Regulated Cloud GCC Launch Leader

The mandate

The Bengaluru centre has premises, approved headcount and initial engineers, but its launch director departed before production authority, regulated controls and source-team exits were established. Cloud operations still depend on overseas privileged staff, SRE recruitment is outpacing leadership, and the board cannot distinguish genuine capability from activity reported through hiring and migration counts.

The interim must take the Bengaluru seat within two weeks and lead for eighteen months, with a possible three-month extension only if a regulator moves the final service-transfer observation. A permanent India cloud executive search begins after the centre commands two regulated services through release and incident, expected in month ten. The successor will overlap for eight weeks.

Handover requires Bengaluru leaders to own cloud reliability, change, incident, capacity and supplier decisions within approved delegations; privileged operations to meet local and global controls; four service families to complete exercised transfer; two source teams to exit shadow duties; the leadership bench to cover critical absences; and the permanent appointee to chair the closing governing-board review.

The interim may stop migrations, reject service acceptance, set operating standards, appoint approved temporary leaders, redirect programme resources and commit up to ₹90 crore within the authorised launch plan. Permanent appointments, site expansion, risk-policy changes, new strategic suppliers and single commitments above ₹18 crore require board consent. The seat cannot waive regulated segregation or payment-continuity obligations.

Payment product roadmaps, consumer operations, corporate real estate beyond the Bengaluru site and transfer of non-cloud functions are explicitly out of scope. The mandate owns the cloud GCC charter in operation, platform and SRE capability, regulated control execution, service transfer, leadership formation, value proof and permanent succession.

Why this seat is open

The director’s exit converted a planned build into an urgent accountability gap before production responsibility had moved. Headquarters continues to absorb risk while hiring creates expectations that the centre already owns outcomes. Temporary executive authority is required to establish real operating control, demonstrate it through regulated events and hand a stable institution to permanent leadership.

What you will own

• Establish the Bengaluru charter through named platform, reliability, control, supplier, talent and financial decision rights.
• Build the leadership spine across cloud engineering, SRE, security, service management, FinOps and workforce development.
• Define service-transfer gates for access, architecture, deployment, observability, capacity, incident, recovery, compliance and source-team exit.
• Command Bengaluru-led releases, incidents and resilience exercises while progressively removing overseas shadow execution.
• Install control evidence for privileged access, segregation, change, vulnerability, recovery, supplier action and operational risk acceptance.
• Demonstrate value through service outcomes, engineering flow, control quality, talent depth and cost without treating headcount as impact.
• Transfer the charter, service ledger, talent map, delegations, exceptions and sponsor relationships through successor-led governance.

Candidate qualifications

• Held executive accountability for launching or scaling an India GCC with regulated cloud and SRE production ownership.
• Built senior platform, reliability, security and service leadership before volume hiring created an unmanageable organisation.
• Migrated privileged operations and incident authority across borders while preserving segregation and regulator evidence.
• Used exercised service-transfer gates to stop premature acceptance and retire source-team shadow work.
• Demonstrated GCC value through reliability, control and product outcomes alongside fully burdened economics rather than simple labour arbitrage.
• Completed succession into a permanent India leader who chaired global service and risk decisions before handover.

Non-negotiables

• Can start on site in Bengaluru within two weeks and travel monthly to named source or regulated service locations.
• Will accept exclusive executive responsibility and continuous escalation availability for transferred production services.
• Brings a regulated India GCC build with real operating authority; campus mobilisation or recruitment scale alone is insufficient.
• Must disclose current relationships with payment firms, cloud providers, GCC vendors, recruiters and location advisers.

1. 49 words maximum. State your earliest Bengaluru start and the largest regulated cloud capability you launched inside an India GCC.
2. 49 words maximum. Describe a service transfer you stopped because access and incident authority had not genuinely moved.
3. 49 words maximum. Which outcome would prove the centre creates value beyond filled seats and lower labour cost?