Director of GCC Setup — Interim, Retail Analytics

The mandate

A lease approval delay forced six analytics teams into separate vendor facilities, and the setup director departed after migration ownership fragmented. Hiring continues, but privacy controls, product alignment and a coherent day-one plan do not.

The interim is needed within three weeks for a fixed twelve-month recovery, after which the programme office closes. A permanent centre operations director is already employed and will inherit the facility once the final migration wave is accepted.

Handover means 520 roles filled within ten per cent of budget, five analytics products operating at agreed service levels, customer-data controls independently approved, and the centre director running the monthly value and risk forum without setup-office intervention.

The setup director may sequence migration waves, allocate programme funds below ₹75 lakh and resolve job architecture within approved bands. Scope additions above forty roles, material vendor termination and customer-data hosting changes need global approval; the interim cannot set merchandising strategy.

Store operations redesign, enterprise cloud renegotiation and consumer research lie outside the assignment. The setup office creates a functioning delivery centre, not the retailer's global analytics roadmap.

Why this seat is open

Facilities delay turned a coordinated launch into six local workarounds. The prior director left before governance could be reassembled. The sponsor wants one time-bound integrator to finish migration and then remove the temporary programme layer cleanly.

What you will own

• Rebaseline the twelve-month launch around facility, hiring, data-access and product-dependency critical paths.
• Decide which teams consolidate first by privacy risk, collaboration need and business-release dates.
• Establish one work-package contract for each migrated analytics product, including inputs, service and acceptance owner.
• Govern role hiring against skill clusters, seniority ratios, compensation envelopes and avoidable duplication.
• Certify customer-data access, masking, retention and model-development environments before each migration wave.
• Reconcile build spending, vendor exit and steady-state run cost monthly with global finance.
• Dissolve the setup office after the centre director accepts assets, controls, suppliers and residual actions.

Candidate qualifications

• Eighteen-plus years delivering GCC launches, capability migrations or analytics operating-model programmes.
• Built or recovered an Indian centre of at least 400 employees involving sensitive consumer or transaction data.
• Strong command of work-package definition, transition waves, role architecture and programme-finance control.
• Experience unifying teams housed across interim vendors without compromising access or intellectual-property safeguards.
• Ability to distinguish centre setup decisions from global product and business-strategy accountability.
• Demonstrated closure of a temporary programme office with residual ownership accepted by line leaders.

Non-negotiables

• Can work onsite in Hyderabad within three weeks for the full setup year.
• No financial interest in facility, staffing or managed-service vendors bidding for the centre.
• Will accept a fixed endpoint when the setup office is dismantled.
• Available for evening governance with global retail stakeholders when migration gates require it.

1. 49 words maximum. Confirm your start date and ability to work onsite throughout the Hyderabad launch.
2. 49 words maximum. Which centre launch did you recover, and what milestone was already late when you arrived?
3. 49 words maximum. What objective evidence did you require before accepting a migrated analytics product?