← Learning Pathways Learning Pathway

Head of Engineering to VP of Engineering

🕑 24-48 months Shared Leadership

The transition to VP is as much about organisational influence and executive presence as it is about engineering excellence. You move from owning the engineering function to co-owning the company's technology strategy at board level.

🎯 Focus Areas

Executive Presence and Influence

At VP level you are a member of the executive team, not just a representative of engineering. You need to shape company strategy, build credibility with investors and the board, and influence decisions that span the whole organisation - product, commercial, finance, and people.

Technology Strategy at Company Scale

You are accountable for multi-year technology bets - platform investments, build vs buy decisions, architecture evolution, and the engineering capability needed to support business growth. These decisions are made with incomplete information and have long-lasting consequences.

Organisational Design at Scale

VP-level org design means structuring multiple departments, managing managers of managers, and ensuring the engineering organisation can scale its output without proportional growth in headcount. Team Topologies, cognitive load, and delivery flow become strategic tools.

Commercial and Financial Literacy

You need to own engineering's budget, make investment cases to the CFO and CEO, and understand how engineering spend connects to revenue, margin, and competitive position. FinOps, vendor strategy, and capacity planning are now your accountability.

External Representation

VPs represent engineering externally - to candidates, to customers, to the press, and to the technical community. Building employer brand, speaking at industry events, and cultivating external technical credibility are part of the role.

⚡ Skills & Behaviours to Develop

Skills to Develop

  • Build and present multi-year engineering investment cases that connect technology decisions to commercial outcomes.
  • Design org structures across multiple departments, applying Team Topologies principles to minimise cognitive load and maximise flow.
  • Operate credibly in board and investor conversations - translating engineering strategy into business value with confidence.
  • Develop succession plans for every senior engineering leadership role, identifying and investing in the next generation of leaders.
  • Manage engineering budget at scale - headcount planning, vendor contracts, infrastructure spend, and return on investment analysis.
  • Build and articulate a compelling engineering brand externally to attract senior technical talent.
  • Navigate cross-functional executive conflict - aligning engineering priorities with product, commercial, and finance leadership.

Behaviours to Demonstrate

  • Presents engineering strategy to the board or investors with clarity and confidence, without deferring to a CTO or CEO to translate.
  • Identifies organisational bottlenecks at department level and restructures teams to restore flow without creating political fallout.
  • Makes major build vs buy or platform investment decisions with explicit documentation of assumptions, risks, and success criteria.
  • Develops engineering managers into heads of department, actively investing in their leadership capability over 12-24 month horizons.
  • Operates as a genuine peer to CPO, CFO, and CMO - contributing to company strategy beyond the engineering domain.
  • Maintains deep enough technical credibility to spot when the organisation is taking on dangerous technical debt or making poor architectural bets.
🛠 Hands-On Projects
1 Build a three-year engineering capability roadmap tied to the company's commercial growth plan and present it to the executive team for ratification.
2 Lead a full org design exercise across two or more engineering departments, applying Team Topologies principles and documenting the expected impact on delivery flow.
3 Run a build vs buy evaluation for a major platform capability - document the commercial, technical, and organisational trade-offs and secure executive alignment.
4 Develop a succession plan for every Head of Engineering and senior leadership role in your organisation, with named candidates and 12-month development plans.
5 Represent engineering externally - speak at a conference, publish a technical blog post, or participate in a panel - and measure the impact on talent pipeline.
⚡ AI Literacy for This Transition
AI as a strategic and organisational capability
1

Develop a coherent organisational AI strategy - covering how engineering teams adopt AI tools, what guardrails are needed, and how AI capability connects to the company's competitive position.

2

Use AI to accelerate strategic analysis - market research, competitor technical positioning, and technology trend synthesis - while maintaining critical judgement about what AI gets wrong at this level of abstraction.

3

Build AI literacy as an organisational capability, not just a personal one - setting expectations for how engineers at every level engage with AI tools safely and productively.

4

Engage with the governance and ethics dimensions of AI at board level - understanding regulatory exposure, model risk, and reputational considerations as part of technology strategy.

5

Evaluate AI investment decisions with the same rigour applied to any major build vs buy decision - distinguishing genuine competitive advantage from hype-driven spend.

📚 Recommended Reading

The Hard Thing About Hard Things

Ben Horowitz

Unvarnished account of executive leadership in technology - the decisions that don't have clean frameworks.

Become an Effective Software Engineering Manager

James Stanier

A grounded guide to engineering leadership that scales from manager to VP-level thinking.

Team Topologies

Matthew Skelton and Manuel Pais

The foundational framework for org design - essential for a VP designing engineering at scale.

Good Strategy Bad Strategy

Richard Rumelt

How to distinguish genuine strategy from goal-setting dressed up as strategy - essential for VP-level planning.

Measure What Matters

John Doerr

OKRs in practice - how to align engineering goals with company strategy and create accountability without micromanagement.

🎓 Courses & Resources

Executive Leadership Programme

London Business School / INSEAD

Broadens commercial and strategic thinking beyond the engineering domain.

Financial Acumen for Non-Financial Leaders

Coursera / various business schools

Builds the financial literacy needed to own engineering budget and make investment cases at board level.

CTO Craft Community and Events

CTO Craft

Peer learning from VPs and CTOs navigating the same challenges - the network is as valuable as the content.

📋 Role Archetypes

Review the full expectations for both roles to understand exactly what good looks like at each level.

→ Head of Engineering Archetype → VP of Engineering Archetype