Chief Information Officer — Interim, Financial Services GCC

The mandate

A regulatory-control migration failed during cutover, producing unauthorised access and incomplete reconciliations. The GCC CIO was removed after an independent review found that delivery metrics routinely overrode risk acceptance.

The interim must take the seat within two weeks for eighteen months, covering stabilisation, remigration and regulatory closure. A global search begins after the first clean control quarter, with eight weeks reserved for successor induction.

Handover is achieved when the affected platforms complete controlled cutover, all critical technology findings are closed, service availability stays above 99.95 per cent for six months, and the incoming CIO signs the application-ownership and residual-risk inventory.

The CIO may stop migrations, assign engineering capacity, approve remediation below ₹2 crore and reject risk acceptances lacking named owners. Architecture changes above ₹8 crore, material outsourcing and risk acceptance beyond tolerance require global committees; business product policy is excluded from CIO authority.

Core banking strategy, customer pricing and global data-centre consolidation are outside the seat. The assignment repairs India-delivered technology services and their accountable risk framework.

Why this seat is open

The failed cutover exposed a pattern of weak control challenge rather than an isolated engineering error. Removal of the incumbent created an immediate regulated-officer gap. A tested interim CIO must reset decision quality before the organisation commits to a permanent technology leader.

What you will own

• Reconstruct cutover failures across entitlement, reconciliation, rollback and approval evidence, assigning causal ownership.
• Decide the remigration sequence using customer impact, control readiness and recovery-test results.
• Reinstate technology-risk acceptance with quantified exposure, expiry dates and accountable business owners.
• Establish application ownership covering service, data, cyber, resilience and regulatory obligations.
• Direct closure of critical findings through independent evidence testing rather than programme self-reporting.
• Certify service availability, change failure and control health monthly to the India risk committee.
• Transfer the platform inventory, risk decisions and operating cadence through two chaired successor cycles.

Candidate qualifications

• More than twenty-two years in regulated financial-services technology, including CIO or equivalent large-centre accountability.
• Led recovery from a failed migration involving access, reconciliation, resilience or regulatory control breakdown.
• Strong grasp of application ownership, operational resilience, cyber risk, change governance and outsourced technology control.
• Experience managing Indian engineering scale above 1,000 while remaining accountable to global regulated entities.
• Evidence of stopping high-profile delivery when risk evidence or recovery readiness did not meet tolerance.
• Board and regulator communication experience translating technical failure into explicit customer and control exposure.

Non-negotiables

• Available onsite in Hyderabad within two weeks and for global incident escalation.
• Satisfies enhanced financial-services background and fit-and-proper screening.
• No concurrent commitment to a regulated competitor or key technology supplier.
• Prepared to hold executive risk-signatory duties through the eighteen-month recovery.

1. 49 words maximum. Confirm your start date and capacity for global incident duty from Hyderabad.
2. 49 words maximum. Which regulated cutover did you stop or repeat, and what control failed first?
3. 49 words maximum. What technology risk did you refuse to accept despite a committed launch date?