EVP – Risk and Resilience — Developer-Tools Business

The mandate

A deliberate change of pace is required to deal with board concern over resilience and inconsistent first-line ownership within a privately held enterprise technology and digital-products group. The immediate arena is the developer-tools business during a global go-to-market redesign. For mandate 110, the successful executive inherits decisions that have been deferred, competing stakeholder expectations and a need to establish facts before committing further capital.

The EVP – Risk and Resilience operating perimeter covers approximately ₹2,000 crore in annual recurring revenue portfolio, with activity spanning several developer-tools business customer, product and delivery clusters rather than a single asset. The EVP – Risk and Resilience Technology remit carries direct influence over roughly 525 colleagues and third-party capacity.

The board and its investment committee want a EVP – Risk and Resilience who can convert ambiguity into a short list of explicit choices for the developer-tools business. The EVP – Risk and Resilience Technology seat must resolve a global go-to-market redesign, while preserving the underlying strengths of the developer-tools business. For mandate 110, value will come through sharper allocation, stronger leaders and an operating cadence that exposes variance early.

The EVP – Risk and Resilience’s first year on the developer-tools business is expected to end with risk appetite adherence, tested resilience and faster issue closure. In mandate 110, authority covers resources and leadership appointments; material trade-offs go directly to the board sponsor.

Why this seat is open

This is a newly created EVP – Risk and Resilience — Developer-Tools Business seat, established because a global go-to-market redesign now requires one accountable executive rather than distributed ownership. The board has classified the appointment as urgent and intends to move from qualified shortlist to offer within 6–8 weeks. Interim governance protects the developer-tools business, but it is not a substitute for a permanent appointee. The external search remains confidential to avoid unnecessary disruption before the appointment is agreed.

What you will own

• Set the EVP – Risk and Resilience value-creation thesis for the developer-tools business, translate it into no more than five enterprise priorities and stop work that does not support them.
• Carry stewardship of approximately ₹2,000 crore in annual recurring revenue portfolio, including allocation, risk acceptance and board forecasts.
• Lead the EVP – Risk and Resilience Technology organisation of about 525 employees and partners, appointing a team with clear decision rights and credible succession for every critical seat.
• Resolve the developer-tools business economics and execution constraints created by a global go-to-market redesign, with EVP – Risk and Resilience-approved owners, dated milestones and transparent escalation thresholds.
• Establish one EVP – Risk and Resilience operating review across commercial, customer, financial, people, technology and risk outcomes for the developer-tools business; remove reconciliations that obscure accountability.
• Demonstrate enterprise authority across functions and markets, with outcomes visible in cash, customers or controlled risk in mandate 110.
• Build the EVP – Risk and Resilience’s three-year succession and capability plan for the developer-tools business, reducing dependence on individual executives and improving mobility across the wider Technology organisation.

The first 12 months

• Days 1–90: Validate the developer-tools business baseline, meet the 30 stakeholders most consequential to board concern over resilience and inconsistent first-line ownership, assess the leadership team, stabilise immediate delivery risks and agree a board-owned scorecard with explicit decision gates.
• Months 4–9: Make the principal EVP – Risk and Resilience portfolio and organisation choices for the developer-tools business, 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 developer-tools business trend against risk appetite adherence, tested resilience and faster issue closure, 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 EVP – Risk and Resilience’s agreed first-year developer-tools business value case within a 10% tolerance, with variance explained before rather than after the relevant quarter closes.
• A EVP – Risk and Resilience forecast that remains decision-useful across three consecutive quarters and reconciles the developer-tools business’s operating, cash, customer and people assumptions.
• Closure of the EVP – Risk and Resilience mandate’s highest-priority developer-tools business risk and execution issues by their board-approved dates, with independent evidence that fixes are sustained.
• Retention of at least 90% of critical developer-tools business talent and ready-now successors for at least 70% of the EVP – Risk and Resilience’s direct reports.
• A quantified EVP – Risk and Resilience-owned improvement in the developer-tools business operating constraint behind a global go-to-market redesign, supported by a clean baseline and named data owner.
• Clear stakeholder confidence in mandate 110: 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 EVP Risk, Deputy CRO or Operational Resilience Head in a privately held Technology or adjacent enterprise. In relation to the developer-tools business, your EVP – Risk and Resilience track record includes a transition where the original plan was no longer sufficient; you can explain your choices, evidence and numerical impact. Candidates from software, cloud services, digital platforms, IT services or technology-enabled business services will be considered where the operating model, customer stakes and governance intensity match this EVP – Risk and Resilience brief.

As a EVP – Risk and Resilience candidate, you bring 22–28 years of progressive Technology 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 ₹1,150 crore and led an organisation of at least 375 people.

For mandate 110, the board wants two transitions: a difficult developer-tools business portfolio choice and a leadership-system change during a global go-to-market redesign. As the prospective EVP – Risk and Resilience for this developer-tools business, you must challenge optimistic cases and still create followership. References for mandate 110 must distinguish your contribution from the institution around you.

The EVP – Risk and Resilience role in Technology is based in Chennai; 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 EVP Risk, Deputy CRO or Operational Resilience Head, with direct exposure to a board, investment committee or equivalent Technology governance forum.
• Proven EVP – Risk and Resilience ownership of at least ₹1,150 crore and leadership of no fewer than 375 employees in a comparable developer-tools business context.
• One completed Technology or adjacent-sector example of board concern over resilience and inconsistent first-line ownership with outcomes sustained for at least two reporting periods after the initial intervention.
• Sector credibility from software, cloud services, digital platforms, IT services or technology-enabled business services; experience that is purely functional and lacks EVP – Risk and Resilience-level developer-tools business consequences will not meet the bar.
• Willingness to meet the Chennai location expectation, complete conflicts and background diligence, and protect the confidentiality of mandate 110.

Compensation and terms

The anticipated EVP – Risk and Resilience package is ₹2.2–3.0 crore fixed + performance variable, calibrated to the final developer-tools business scope and the candidate’s current mix. Any long-term participation for mandate 110 follows standard vesting and performance conditions. The EVP – Risk and Resilience appointment in Chennai, centred on the developer-tools business, offers regular exposure to the board and its investment committee. A notice period of up to 6 months can be accommodated for the selected executive in mandate 110.

Confidentiality

To protect the board, incumbent team and candidate, the organisation remains unnamed until a confidential conversation confirms mutual relevance for mandate 110. The operating facts have been rounded and blended expressly to remove identifying signals for mandate 110.