VP Engineering vs CTO: Which First?

The short version: a CTO decides what to build and on what; a VP Engineering makes sure it gets built. Most scaling businesses need the second before the first, and appoint the first because it sounds more senior.

That inversion is the commonest structural mistake in technology leadership hiring, and it is expensive — a strategist appointed into a delivery problem spends a year producing architecture documents while releases keep slipping. This article sets out where the line falls, which appointment to make first, and when the split becomes necessary.

What each role owns

The CTO owns technology strategy and technical direction. Architecture, build-versus-buy, platform choices, technical risk, and the relationship between what the technology can do and what the business wants to sell. In product businesses the role is externally facing too — investors, partners, occasionally customers. It is a strategic and representational role as much as a technical one.

The VP Engineering owns the engineering organisation and its output. Hiring, team structure, delivery cadence, process, performance management, and the health of a function that may be the largest in the business. Success is measured in shipped work, predictability and retention.

The distinction is not seniority. In many businesses they are peers, and in some the VP Engineering manages more people and more budget. The distinction is what the role is accountable for — direction versus delivery.

Side-by-side comparison

	CTO	VP Engineering
Accountable for	What gets built and on what	That it gets built, predictably
Time horizon	Twelve to thirty-six months	This sprint to this quarter
Spends time on	Architecture, vendors, board, technical risk	People, process, hiring, delivery
External facing	Frequently — investors, partners, customers	Rarely, beyond recruitment
Failure looks like	Wrong platform bets, mounting technical debt	Slipping releases, engineering attrition
Typical background	Architect, founding engineer, principal	Engineering manager, director of engineering

Which to appoint first

Work backwards from the symptom rather than forwards from the org chart.

Appoint a VP Engineering first where the direction is clear but delivery is not. The symptoms are recognisable: releases slipping repeatedly, estimates nobody trusts, engineers leaving, a founder or technical lead spending most of their week unblocking people rather than thinking. This is the more common situation in businesses between fifteen and sixty engineers, and it is where the appointment pays for itself fastest.

Appoint a CTO first where delivery is adequate but direction is not. Platform decisions being deferred, a technical estate nobody has a plan for, an investor or board asking questions the business cannot answer, or a product strategy that depends on technical choices nobody senior is making.

Where the founder is technical — common in early-stage businesses — the CTO function often already exists informally, and a VP Engineering is almost always the right first external appointment. Bringing in a CTO over a technical founder rarely works unless the founder has genuinely decided to step away from technical direction, which they usually have not.

The split point

In smaller businesses one person covers both. The question is when that stops being viable.

Under about fifteen engineers, one role is normal and sensible. A hands-on CTO or a Head of Engineering carries both, and splitting creates overhead the organisation cannot absorb.

Between fifteen and forty, the strain becomes visible. The individual is either neglecting strategy to manage people or neglecting people to think about architecture. Most businesses split somewhere in this band, and most wait longer than they should.

Above forty, running both is genuinely not possible. Businesses attempting it typically have a burnt-out technical leader and an engineering function that has quietly organised itself.

Headcount is a proxy rather than a rule. Multiple products, multiple locations or a regulated environment all bring the split point forward.

How they work together

Where both exist, three things determine whether the relationship functions.

Who the engineers report to. Almost always the VP Engineering. A CTO retaining direct reports across the engineering organisation undermines the appointment immediately and confuses everyone below.

Who owns the roadmap trade-off. When product wants a feature and the platform needs work, someone decides. Usually the CTO, in consultation — but it should be written down, because this is the recurring point of friction.

Whether both report to the CEO. Peer structure works well where the two respect each other’s remit. A VP Engineering reporting into the CTO also works and is more common. What works badly is an ambiguous arrangement where both believe they own the function.

Professional standards for technology leadership in the UK are published by BCS, The Chartered Institute for IT, and where either role is a registered directorship the statutory duties at section 172 of the Companies Act 2006 apply.

Assessment: distinguishing the two at interview

Candidates frequently present for both, so the questions need to separate them.

“Tell me about a delivery problem you fixed. What specifically changed?” — VP Engineering candidates describe process, structure and people decisions with dates attached. CTO candidates often describe a technical solution, which is a different answer to a different question.

“Describe a platform decision you made that turned out badly.” — the CTO question. Look for a specific bet, a specific cost and what they learned.

“How many engineers have you hired and how many have you let go?” — VP Engineering candidates answer both parts readily. Reluctance on the second is worth exploring.

“Explain a technical risk to me as though I were your board.” — relevant for both, decisive for a CTO. If technical exposure cannot be translated into commercial consequence, the board will never fund the fix.

Frequently asked questions

Is a CTO more senior than a VP Engineering?

Usually in title, not always in practice. The CTO holds a C-suite position and owns technical direction; the VP Engineering frequently manages more people and more budget. In many businesses they are peers reporting to the CEO.

Which should a scale-up hire first?

Usually a VP Engineering, because the common problem at that stage is delivery rather than direction — particularly where a technical founder is already providing the CTO function informally. Hire a CTO first where platform decisions are being deferred and delivery is adequate.

At what team size should the roles split?

Most businesses split between fifteen and forty engineers. Below fifteen one person can reasonably carry both; above forty it is not sustainable. Multiple products, multiple locations or a regulated environment brings the split point earlier.

Can a VP Engineering become a CTO?

Sometimes, though the two draw on different strengths. The step requires architectural judgement and board-facing communication that running a delivery organisation does not necessarily develop. Test both before promoting rather than assuming progression.

Do the engineers report to the CTO or the VP Engineering?

To the VP Engineering, in almost all functioning structures. A CTO retaining direct reports across the engineering organisation undermines the VP’s authority and creates confusion about who sets priorities.