In short
A CTO owns the technical direction of the company — architecture, technical strategy, and often the external technical voice. A Head of Engineering owns the delivery organisation — people, execution and predictability. Early-stage teams usually need delivery before they need direction, because the direction is still being set by the founders.
Key facts
- CTO answers
- Where is the technology going and why
- Head of Engineering answers
- Will it ship, by whom, and when
- Most common mistake
- Hiring a title to signal seniority to investors
- Cheapest correction
- Deciding the scope before the first conversation
Why the titles blur at this stage
In a company of eight engineers the same person may set architecture, run one-to-ones, negotiate with a customer's security team and write code on a Friday. The titles only separate once the work does.
That makes the title a poor starting point. The useful starting point is the failure you are trying to prevent in the next twelve months, because the two roles prevent different failures.
Two roles, side by side
Read down the column that matches the failure you are most worried about.
| Dimension | CTO | Head of Engineering |
|---|---|---|
| Primary object | The technology strategy | The engineering organisation |
| Time horizon | Twelve to thirty-six months | This quarter and the next |
| Typical first win | A defensible technical direction the team believes | Predictable delivery and clear ownership |
| External role | Customers, partners, due diligence, hiring pull | Mostly internal |
| Failure it prevents | Building the wrong thing well | Building the right thing late or never |
| Works badly when | There is no strategy vacuum to fill | Founders will not delegate delivery |
Signs you need direction, not delivery
These point towards a CTO-shaped hire — or towards a founder taking the title seriously.
- Architecture decisions keep being reopened because nobody owns them.
- Enterprise buyers ask technical questions no one in the company can answer with authority.
- The product roadmap and the technical roadmap contradict each other.
- Two credible technical futures exist and choosing between them is the real bottleneck.
Signs you need delivery, not direction
These point towards a Head of Engineering, or a first engineering manager if the team is smaller.
- The direction is clear and the team still misses dates it set itself.
- The founder-CTO is the bottleneck on reviews, decisions and interviews.
- Engineers do not know who decides what, so escalation goes to a founder every time.
- Hiring, onboarding and performance conversations are being deferred indefinitely.
Decide the scope before you write the advert
Four short exercises that make the search answerable.
Write the twelve-month failure
One paragraph describing the outcome you are hiring to avoid. If it is about direction, you are hiring a CTO. If it is about throughput, you are hiring delivery leadership.
Name what the founders will not give up
If a technical founder intends to keep architecture and technical strategy, the honest title is a delivery one. Advertising CTO in that situation loses good candidates twice — at offer and six months later.
Decide the team they inherit
Size, seniority, whether they can hire, and what the budget is. Leadership candidates ask this early, and a vague answer reads as an unclear mandate.
Agree the decision rights in writing
Three examples: who chooses the cloud provider, who approves an architectural rewrite, who signs off a senior offer. Ambiguity here is the most common reason a strong technical leader leaves inside a year.
Common questions
- Can one person do both?
- Frequently, in a small team — and that is often the right answer at first. It stops working when the delivery organisation is large enough that people management fills the week, leaving no time for the strategic work the title implies.
- Do we need a CTO to raise money?
- We are not in a position to state what any investor requires, and would be inventing it if we did. What we can say is that appointing a title to satisfy an assumed expectation, rather than a real gap, tends to produce a mandate nobody can execute.
- What about a VP Engineering?
- In most usage it is the same job as Head of Engineering with a different market convention — often implying a larger organisation and a layer of managers beneath. Define the scope and decision rights and the label matters much less.
- How does the search differ between the two?
- A CTO search is assessed on judgement, technical strategy and how they defend past decisions. A delivery leadership search is assessed on organisation-building evidence: how they set standards, grew people and made shipping predictable.
Turn this into a brief
Answer six short questions and you have a usable technical hiring brief you can keep improving, print or share internally.
Open the hiring brief builderAny percentages or figures shown in this article are illustrative examples used to explain the model. They are not quoted rates, market benchmarks or salary data.