VP of Engineering: What the Role Owns, and How It Differs From CTO

· Updated · by Marian Kamenistak

A VP of Engineering owns the machine that builds the product: the people, the teams, the process, and the delivery. The one thing not on that list is the technology bets, those stay with the CTO.

That single sentence resolves most of the confusion around the title. The rest of this guide covers what the role owns in practice, how it splits from CTO, and when a company needs one.

I held this seat myself, at Mews I took the engineering org from 8 to 80 people through Series C while the roadmap kept shipping, so what follows comes from the operator side rather than from a framework.

What a VP of Engineering owns

  1. Delivery. The roadmap ships or it doesn’t, and when it doesn’t, the question lands on the VPE’s desk, not on the PM’s and not on the teams’.
  2. The org. Team topology, spans of control, when to split a team, when to add a management layer. Getting this wrong costs quarters.
  3. Hiring and the bar. Headcount plan, interview loops, closing senior candidates. At scale-up pace this is half the calendar.
  4. The management team. Engineering managers and directors report here. Their growth, their performance, their alignment. A VPE who skips 1:1s with their EMs is running blind.
  5. Process and predictability. Planning cadence, incident response, quality gates, enough process to stay predictable without suffocating the teams.
  6. Translation. The exec team speaks revenue and dates, engineering speaks scope and risk, and the VPE converts between the two without losing signal.

VP of Engineering vs CTO

VP of EngineeringCTO
FacesInward: org, deliveryOutward and forward: strategy, board
OwnsTeams, hiring, process, shippingTechnology bets, architecture direction
Measured byRoadmap delivery, org health, retentionRight technology calls, technical moat
Reports toCEO, sometimes CTOCEO
CodeRarelyDepends on stage, often prototypes
Fails whenRoadmap slips, managers churnCompany bets on the wrong stack

The two roles are complementary peers, not a stack. In companies under about 30 engineers one person usually holds both jobs, and the split becomes necessary when that person’s calendar fills up with people problems while the technology direction starts drifting. Watch for the drift, as opposed to any particular headcount number.

Marian Kamenistak on the main stage of the Engineering Leaders Conference, arm raised, co-host in the background.
VPE and CTO are peers with different jobs, not a stacked hierarchy.

For the CTO side of this boundary, I keep a separate practice: CTO mentoring.

When a company adds the role

So when does a company add a VPE? Three common triggers, from the sessions where this decision was on the table:

  1. A founder-CTO is drowning in management and knows it. The VPE hire gives them their technical job back.
  2. Engineering passed 25 to 30 people and delivery got slower with every hire. That’s an org problem, and org problems need an owner.
  3. The board asked “who runs engineering?” during due diligence and the honest answer was “sort of everyone”.

The wrong trigger: hiring a VPE to fix a broken product strategy. A VPE makes the machine run, and if the machine is building the wrong thing, you have a different problem.

Getting into the role, and surviving it

Most VPEs come up through engineering manager and director roles, and the jump is bigger than it looks: a director improves their group, a VPE owns the whole system, including the parts nobody wants, compensation fights, reorgs, the underperforming manager everyone likes. I mapped the exact shape of that jump in How to Become a VP of Engineering: The Three Gaps.

Marian Kamenistak in a 1:1 mentoring session.
The director-to-VPE jump is exactly the kind of transition I work through in session.

52% of the leaders I mentor are in their first leadership role at their level, and across 3,400+ mentoring sessions with 300+ engineering leaders the same pattern keeps repeating with new VPEs: they keep doing their old director job for six months because it feels productive, while the exec-level work, the org design, the translation layer, stays unowned.

If you’re stepping into this role, or fighting for it, that transition is exactly what 1:1 mentoring for engineering leaders is built for. First intro session is free.

Frequently asked

What is a VP of Engineering?+
A VP of Engineering is the executive who owns delivery and the engineering organization: hiring, team structure, processes, and shipping the roadmap. The CTO owns technology strategy and the board conversation, while the VPE runs the org that does the building.
Is VP of Engineering or CTO higher?+
Neither, in a healthy org. They're peers with different jobs. The CTO faces outward and forward: technology bets, architecture direction, board and investors. The VPE faces inward: people, delivery, org health. In smaller companies one person holds both jobs until the org outgrows them.
How much does a VP of Engineering make?+
The band depends on three things: company stage, geography, and whether equity is real. A VPE at a US scale-up earns a multiple of what the same role pays in Central Europe, and equity can dwarf salary at both. Ask for the full range in your market before negotiating, not a global average that applies to nobody.
What does a VP of Engineering do day to day?+
Hiring and org design, unblocking delivery, running the management team, fixing the process where the roadmap slips, and translating between the exec team and engineering. Very little code. If a VPE is still the best engineer in the room, the org has a gap one level down.
What is the difference between a VP of Engineering and a Director of Engineering?+
Scope. A Director runs a group of teams inside the org, usually through engineering managers. The VPE runs the whole engineering org and sits on the exec team. In a 40-person org the two titles often describe the same job.

New posts, straight to your inbox.