Confidential mandate

Vice President, Responsible AI Programme Delivery

Planned Hiring / New

Vice President, Responsible AI Programme Delivery mandate in Bengaluru, India · Financial Technology Delivery Services

Lead permanent delivery of a responsible AI control portfolio for a financial technology services business, translating approved governance requirements into accepted operating capabilities over an initial eighteen-month agenda with clear product, risk and implementation accountability.

The mandate

A financial technology delivery organisation has approved responsible AI requirements but struggles to turn them into consistent product operations. Individual teams interpret the same expectation differently, programme status reports count completed activities and operating owners discover maintenance obligations late. This Vice President owns the delivery architecture that connects approved control decisions to tested capabilities and accountable business-as-usual ownership.

Permanent employment is open-ended, with an eighteen-month initial portfolio agenda. The leader will sequence control implementation according to material exposure, product dependencies and evidence readiness, rather than impose identical deadlines on every team. Delivery work includes operating procedures, assurance interfaces and ownership transfer; it does not treat policy publication or a training attendance count as proof that a control works.

Programme judgement must accommodate uncertain technical behaviour and evolving governance requirements without allowing either to justify indefinite ambiguity. Each workstream needs a defined capability, acceptance owner and observable test. When an expected safeguard cannot be implemented as proposed, the issue must return to the risk decision route with alternatives and consequences, not disappear into a revised milestone labelled amber.

The Vice President controls programme prioritisation and the programme-office team within approved investment limits. Product engineering owns technical implementation, risk sponsors determine policy intent and designated operating executives accept enduring controls. Material scope changes, risk exceptions and additional funding require steering approval. The remit excludes enterprise architecture ownership, customer credit decisions and unilateral interpretation of legal compliance obligations.

At the first-year review, priority workstreams should demonstrate accepted control operation and a credible maintenance owner. At eighteen months, the portfolio should have a stable change mechanism, transparent residual limitations and trained operating leadership able to sustain the implemented capabilities. The continuing position then oversees future responsible AI control delivery as the product estate and approved expectations develop.

What you will own

  • Establish a control capability backlog that translates approved responsible AI expectations into testable operating outcomes, with named acceptance owners and explicit dependencies for each product workstream.
  • Decide the delivery sequence through exposure, feasibility and resource evidence, presenting trade-offs where simultaneous deadlines would create superficial completion rather than reliable implementation of the priority safeguards.
  • Develop acceptance charters with product, risk and operating owners, distinguishing policy intent, technical evidence and maintenance duties so no function assumes another has accepted an unresolved control limitation.
  • Govern portfolio changes when implementation evidence challenges the original design, escalating alternatives and consequences through steering decisions instead of allowing scope drift to hide in revised programme dates.
  • Build an operating transfer standard covering procedures, observation evidence and training demonstrations, ensuring implemented capabilities have usable ownership after the programme workstream is marked complete.
  • Challenge delivery status through sampled control operation and artifact review, separating activity progress from acceptance readiness and requiring workstream leaders to explain material gaps with evidence.
  • Develop senior programme leaders through cross-functional case reviews, strengthening their ability to negotiate practical implementation boundaries while preserving independent risk judgement and engineering accountability.

Candidate qualifications

  • Demonstrate senior programme leadership in financial-services AI innovation, compliance technology or responsible AI implementation, with accountability across several delivery workstreams. Explain a control requirement you translated into a tested operating capability, identify who accepted it and describe the evidence that established completion beyond a policy document or project status declaration.
  • Bring detailed understanding of AI governance and guardrail implementation sufficient to interrogate programme dependencies and acceptance proposals. You need not own every engineering component, but must recognise when an unresolved technical limitation changes the risk decision required. Relevant experience should show clear boundaries between programme leadership, policy ownership and qualified interpretation of external obligations.
  • Show disciplined portfolio prioritisation and change governance under competing executive objectives. Describe a workstream whose apparent progress concealed weak acceptance evidence, how you reopened the issue and what decision followed. The role requires practical judgement about sequencing, maintenance ownership and achievable scope rather than a rigid methodology applied without regard to consequence.
  • Establish strong team leadership, sponsor communication and operating transfer habits. Evidence should include developing workstream leaders, sustaining difficult cross-functional decisions and demonstrating that implemented controls remained usable after project teams withdrew. Recognised programme or agile training may support the record, but personally evidenced delivery and accountability are the essential qualifications.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 11 October 2026. Mandate reference CVU-PER-2026-IND-196.

More seats like this one

Every live mandate, by seat →

This mandate is confidential. The client is named only under a mutual NDA, and your own record is never listed, sold or shown to a company under your name until you release it for this specific mandate.