Gladwin InternationalConfidential mandate

Chief Technology Officer — Vehicle-Software Programme

Urgent / Unplanned

Confidential Chief Technology Officer seat addressing a regional profitability recovery for a integrated automotive and components manufacturer in India.

The mandate

Customer and operating evidence now point to a technology architecture decision that will determine the next growth phase within a privately held integrated automotive and components manufacturer. The immediate arena is the vehicle-software programme during a regional profitability recovery. For mandate 268, the successful executive inherits decisions that have been deferred, competing stakeholder expectations and a need to establish facts before committing further capital.

The Chief Technology Officer operating perimeter covers approximately ₹9,500 crore in regional revenue and programme portfolio, with activity spanning several vehicle-software programme customer, product and delivery clusters rather than a single asset. The Chief Technology Officer Automotive remit carries direct influence over roughly 1,500 colleagues and third-party capacity.

The group board and the relevant risk and people committees want a Chief Technology Officer who can convert ambiguity into a short list of explicit choices for the vehicle-software programme. The Chief Technology Officer Automotive seat must resolve a regional profitability recovery, while preserving the underlying strengths of the vehicle-software programme. For mandate 268, value will come through sharper allocation, stronger leaders and an operating cadence that exposes variance early.

The Chief Technology Officer’s first year on the vehicle-software programme is expected to end with engineering velocity, reliability and a funded target architecture. In mandate 268, authority covers resources and leadership appointments; material trade-offs go directly to the board sponsor.

Why this seat is open

The Chief Technology Officer — Vehicle-Software Programme requirement was not included in the approved hiring calendar. It became urgent after a regional profitability recovery created an immediate need for one accountable owner of the vehicle-software programme. Interim coverage protects essential decisions, but split ownership cannot continue through the next operating gate. The board intends to move from qualified shortlist to offer within 4–6 weeks while preserving confidential, evidence-led diligence.

What you will own

  • Set the Chief Technology Officer value-creation thesis for the vehicle-software programme, translate it into no more than five enterprise priorities and stop work that does not support them.
  • Carry stewardship of approximately ₹9,500 crore in regional revenue and programme portfolio, including allocation, risk acceptance and board forecasts.
  • Lead the Chief Technology Officer Automotive organisation of about 1,500 employees and partners, appointing a team with clear decision rights and credible succession for every critical seat.
  • Resolve the vehicle-software programme economics and execution constraints created by a regional profitability recovery, with Chief Technology Officer-approved owners, dated milestones and transparent escalation thresholds.
  • Establish one Chief Technology Officer operating review across commercial, customer, financial, people, technology and risk outcomes for the vehicle-software programme; remove reconciliations that obscure accountability.
  • Have made consequential architecture and engineering trade-offs while scaling release throughput and reliability in mandate 268.
  • Build the Chief Technology Officer’s three-year succession and capability plan for the vehicle-software programme, reducing dependence on individual executives and improving mobility across the wider Automotive organisation.

The first 12 months

  • Days 1–90: Validate the vehicle-software programme baseline, meet the 30 stakeholders most consequential to a technology architecture decision that will determine the next growth phase, assess the leadership team, stabilise immediate delivery risks and agree a board-owned scorecard with explicit decision gates.
  • Months 4–9: Make the principal Chief Technology Officer portfolio and organisation choices for the vehicle-software programme, install the new operating cadence, fill critical leadership gaps and deliver the first measurable release of cash, capacity or customer value.
  • Months 10–12: Demonstrate a repeatable vehicle-software programme trend against engineering velocity, reliability and a funded target architecture, lock the following year’s capital and talent plan, evidence control sustainability and present a credible three-year value case with downside actions.

What the board will measure

  • Delivery of the Chief Technology Officer’s agreed first-year vehicle-software programme value case within a 10% tolerance, with variance explained before rather than after the relevant quarter closes.
  • A Chief Technology Officer forecast that remains decision-useful across three consecutive quarters and reconciles the vehicle-software programme’s operating, cash, customer and people assumptions.
  • Closure of the Chief Technology Officer mandate’s highest-priority vehicle-software programme risk and execution issues by their board-approved dates, with independent evidence that fixes are sustained.
  • Retention of at least 90% of critical vehicle-software programme talent and ready-now successors for at least 70% of the Chief Technology Officer’s direct reports.
  • A quantified Chief Technology Officer-owned improvement in the vehicle-software programme operating constraint behind a regional profitability recovery, supported by a clean baseline and named data owner.
  • Clear stakeholder confidence in mandate 268: no unresolved high-severity escalation older than 30 days and no material surprise withheld from its agreed governance forum.

The person

You are currently a CTO, VP Engineering or Chief Architect in a privately held Automotive or adjacent enterprise. In relation to the vehicle-software programme, your Chief Technology Officer track record includes a transition where the original plan was no longer sufficient; you can explain your choices, evidence and numerical impact. Candidates from automotive, industrial manufacturing, mobility, components or engineering services will be considered where the operating model, customer stakes and governance intensity match this Chief Technology Officer brief.

As a Chief Technology Officer candidate, you bring 22–28 years of progressive Automotive or adjacent-sector experience, consistent with the 22-28 experience band. At minimum, you have carried a P&L, book, budget or accountable portfolio of ₹5,500 crore and led an organisation of at least 1,050 people.

For mandate 268, the board wants two transitions: a difficult vehicle-software programme portfolio choice and a leadership-system change during a regional profitability recovery. As the prospective Chief Technology Officer for this vehicle-software programme, you must challenge optimistic cases and still create followership. References for mandate 268 must distinguish your contribution from the institution around you.

The Chief Technology Officer role in Automotive is based in Gurugram; relocation is expected, although a structured weekly commute may be considered during the first quarter.

Non-negotiables

  • Current or recent accountability at the level of CTO, VP Engineering or Chief Architect, with direct exposure to a board, investment committee or equivalent Automotive governance forum.
  • Proven Chief Technology Officer ownership of at least ₹5,500 crore and leadership of no fewer than 1,050 employees in a comparable vehicle-software programme context.
  • One completed Automotive or adjacent-sector example of a technology architecture decision that will determine the next growth phase with outcomes sustained for at least two reporting periods after the initial intervention.
  • Sector credibility from automotive, industrial manufacturing, mobility, components or engineering services; experience that is purely functional and lacks Chief Technology Officer-level vehicle-software programme consequences will not meet the bar.
  • Willingness to meet the Gurugram location expectation, complete conflicts and background diligence, and protect the confidentiality of mandate 268.

Compensation and terms

The anticipated Chief Technology Officer package is ₹3.2–4.6 crore fixed + performance variable and LTI, calibrated to the final vehicle-software programme scope and the candidate’s current mix. Any long-term participation for mandate 268 follows standard vesting and performance conditions. The Chief Technology Officer appointment in Gurugram, centred on the vehicle-software programme, offers regular exposure to the group board and the relevant risk and people committees. A notice period of up to 6 months can be accommodated for the selected executive in mandate 268.

Confidentiality

This search is being conducted without naming the client for mandate 268. Identifying information will follow only when both sides elect to proceed under confidentiality; nothing in the published mandate should be treated as a clue to ownership or brand for mandate 268.

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.