GCC Platform Migration Recovery Leader

The mandate

The first transfer wave moved nominal ownership of sixty platform services into a new Hyderabad GCC, but production release, privileged access, incident judgment and environment knowledge remained with individuals in North America and Europe. A major release stalled when those dependencies were unavailable, and emergency support bypassed the new controls. The GCC platform executive left after both sending and receiving teams rejected accountability for the incomplete migration.

The interim must take the Hyderabad seat within three weeks and lead for eighteen months, with a possible three-month extension only if the final regulated product wave is rescheduled. A permanent GCC platform search begins after the centre owns two service families through release and incident, expected in month ten. The successor will overlap for eight weeks and chair the last transfer gate and global reliability council.

Handover requires every migrated service to have Hyderabad-based decision ownership, production access, deployment, observability, runbook, capacity, supplier and escalation capability; three waves to meet release and reliability gates without shadow execution abroad; two cross-region loss exercises to pass; sending teams to exit named duties; and the permanent leader to accept talent, service, dependency and residual-risk registers.

The interim may stop transfers, reject service acceptance, set migration and operating gates, redirect approved roles, change temporary transition support and commit up to ₹75 crore within the authorised GCC programme. Permanent hiring outside approved headcount, product-roadmap changes, legal-entity decisions, site expansion and individual commitments above ₹15 crore require council approval. The seat cannot alter industrial safety or customer-release obligations.

Product feature ownership, corporate functions outside platform engineering, office real estate and wholesale redesign of source business units are explicitly out of scope. The mandate covers platform and SRE service transfer, production authority, cloud and tool access, talent readiness, operating interfaces, migration assurance and permanent GCC leadership handover.

Why this seat is open

The failed wave showed that roles and documents had moved while operational authority and tacit recovery capability had not. Leadership departure left the GCC measured on acceptance and source teams measured on continuity, encouraging both to obscure incomplete transfer. A temporary executive must enforce evidence-based gates, operate the new ownership through real events and leave a permanent leader with global standing.

What you will own

• Reconstruct transferred and retained responsibilities across service decisions, code, release, access, environments, incidents, suppliers and customer escalation.
• Define acceptance gates for architecture knowledge, production permissions, deployment, observability, capacity, recovery, security and accountable talent.
• Decide which services proceed, pause, reverse or split based on readiness and product continuity rather than transfer calendar.
• Remove shadow execution by assigning named decision rights, expiring source access and observing Hyderabad-led production work.
• Build talent and succession plans for platform, SRE and service leadership with evidence from actual operating shifts.
• Command cross-region exercises involving source-team unavailability, provider incident, failed release, access loss and customer escalation.
• Transfer the service ledger, wave evidence, talent map, source exits, exceptions and governance authority through successor-led councils.

Candidate qualifications

• Held executive accountability for a GCC or global engineering-centre transition involving production platform and SRE ownership.
• Recovered a migration where headcount and documents moved but release, access, incident or supplier authority remained offshore.
• Designed evidence gates that distinguished knowledge transfer from independently exercised operating capability.
• Led source-team exit and receiving-team accountability without compromising live product and customer obligations.
• Built senior platform talent and global decision standing inside an Indian centre, not solely delivery capacity.
• Handed a multi-wave migration to permanent GCC leadership after the successor chaired global production decisions.

Non-negotiables

• Can relocate to Hyderabad within three weeks and travel monthly to Bengaluru and transferring international engineering hubs.
• Will accept exclusive executive responsibility and continuous escalation duty for migrated production services.
• Brings executed GCC platform ownership transfer; hiring scale-up or project-transition administration alone is insufficient.
• Must disclose relationships with relevant employers, cloud providers, engineering vendors, recruiters and transition advisers.

1. 49 words maximum. State your earliest Hyderabad start and the largest production-platform transfer you personally led into a GCC.
2. 49 words maximum. Describe one service that appeared transferred until its first serious release or incident.
3. 49 words maximum. Which source-team privilege would you remove last, and what exercised evidence must precede that removal?