Path 10 of 10, by 2026 demand
Engineering Manager / Head of Engineering
Lead people and delivery: hiring, growth, execution and technical strategy for one or several teams.
Demand Both labs list many engineering-manager roles (Anthropic about 110 titles with "manager", including non-engineering; OpenAI Applied AI engineering managers among them) (our count, §2.3). AI-era EMs are expected to lead AI adoption in their teams.
What the role is
An Engineering Manager is accountable for a team's people, delivery and technical health. A Head of Engineering does this across several teams, adds organisation design, budgeting and hiring plans, and partners with product and business leaders on strategy.
Moving from Staff/Principal IC to management is a career change, not a promotion. Interviews test whether you have done the people work, not just the technical leadership.
Level signals
- Hiring: built a team and raised the bar.
- Growth: people you developed and promoted; hard performance conversations handled well.
- Execution: predictable delivery with healthy on-call and quality.
- Strategy: technical direction tied to business goals.
- Org design: team boundaries that match the architecture.
The typical loop
No single public source. Common shape for EM and Head of Engineering roles.
| Stage | What it tests | Basis |
|---|---|---|
| Recruiter and hiring manager | Management experience, scope, style | Common industry pattern; no single source |
| People management | Hiring, performance, growth, conflict | Common industry pattern; no single source |
| Execution and delivery | Planning, prioritisation, incidents | Common industry pattern; no single source |
| System design | Credibility; sometimes lighter than for ICs | Common industry pattern; no single source |
| Cross-functional / executive | Partnership with product and leadership | Common industry pattern; no single source |
Track order
Work top to bottom. Ticks come from the lessons you mark complete.
- 01Behavioural rounds at Staff levelLeadership and behavioral track. The core of the loop.
- 02Working with customersCustomer discovery and technical consulting track. Stakeholder mapping applies to internal partners.
- 03The design methodSystem design track. Keep design credibility.
- 04Worked promptsSystem design track. The migration prompt doubles as an org-design case.
- 05Production AI systemsLLM and agent engineering track. Leading AI adoption in your teams.
- 06Mock roundsMock rounds track. Behavioural and deep-dive mocks.
Role practice set
Prompts written for this site. They are not reported interview questions.
- Tell the story of the hardest performance conversation you have had, including what you would do differently.
- Walk through how you would plan a quarter for a team of eight with three competing priorities.
- Design an interview loop for a Staff engineer and explain each round's purpose.
- Explain how you would roll out AI coding tools to a team, measure the effect, and handle skeptics.
Your résumé and story angle
- Be explicit about management experience. [People you managed directly, for how long, hires made, promotions supported.] If most of your leadership is as an IC, say so and pitch the transition honestly.
- Technical credibility is a strength: Principal-level architecture lets you hold your own with Staff engineers.
- AI adoption leadership: [any team-level AI rollout, with measurement].
Six-week plan
Tick weeks off as you go
Sources
- Reference Full research notes: docs/RESEARCH.md