Head of engineering is the most senior engineering leader in a company that has not yet split the job into VP of Engineering and CTO. One person, the whole function: teams, delivery, hiring, and usually the technology direction too.
That is why the title confuses people. It does not name a rung on a ladder. It names a stage of the company.
I see the title constantly in my practice: 3,400+ sessions with 300+ leaders across 17+ countries since 2019, a large share of them in Central Europe, where “head of engineering” and “head of development” are the default labels for the top engineering job in orgs of 10 to 80 engineers.
What the role owns
Everything, is the short answer, and that is the problem.
- Delivery. The roadmap, the deadlines, the trade-offs. There is nobody above to escalate to except the CEO.
- The teams and the managers. Org shape, first EM promotions, spans of control. Often while still being the most senior technical reviewer in the building.
- Hiring. The pipeline, the bar, the closing calls. At 10 to 50 engineers this is the single biggest lever the company has.
- Technology direction. Stack decisions, architecture bets, build vs buy. The CTO half of the job, done in the gaps between the VPE half.
- The exec conversation. Budgets, board slides, the “when will it ship” question. Translation between business and engineering, both directions.
How the title maps
| Title | Typical company | Scope |
|---|---|---|
| Head of Engineering | Startup or scale-up, ~10 to 80 engineers, common in Europe | Whole engineering function, org + tech |
| Head of Development | Agencies, enterprises, older orgs | Same job, older label |
| VP of Engineering | Scale-up with a formal exec layer | The org half: teams, delivery, hiring |
| CTO | Any stage | The technology half: strategy, board, bets |
The pattern under the table: as the company grows, the head-of-engineering job splits. Strategy and the board conversation go one way, the org and delivery go the other. The person holding the combined title ends up on one side of that split, and choosing which side is one of the hardest career calls in engineering leadership.
I wrote about both halves separately: VP of Engineering vs CTO covers the split itself, and the engineering director guide covers the layer that appears underneath once the org grows.
The trap built into the role
A head of engineering carries two jobs on one calendar. The org job is loud: hiring, delivery, people problems. The technology job is quiet: architecture direction, technical debt strategy, the bet that pays off in two years. Loud beats quiet on every busy week.
The result, seen across dozens of sessions: heads of engineering who have not made a real technology decision in a year, or the mirror image, deeply technical heads whose management layer is silently on fire. Both look fine from the outside until they don’t.
The fix starts with naming which job is currently losing, then protecting explicit time for it. Easier said than done under a CEO who wants both halves at full speed. That negotiation, and surviving the role until the split, is bread-and-butter work in 1:1 mentoring. The intro session is free.