Role guide and interview toolkit

Engineering Manager

What the role covers, what each level means and the training that helps, then how interviews run and how to prepare for each step.

Team health·1:1s·Hiring·Delivery·On-call·DORA metrics
The role in practice

What an engineering manager actually does

The manager who leads one or two engineering teams day to day, from hiring and career growth to planning, delivery and on-call.

The work

An engineering manager leads one or two engineering teams. They hire engineers, run one to one meetings, help people grow in their careers and keep the team healthy.

They plan the work with the product manager and the tech lead, follow delivery and quality, handle on-call and incidents with the team, and follow engineering metrics such as the DORA metrics.

Depending on the company, engineering managers stay more or less hands‑on with code and technical decisions.

A typical week
  • One to one meetings with engineers
  • Sprint planning with the product manager
  • Interviews for a new engineer
  • A review of an incident or of delivery metrics
  • A technical discussion with the tech lead
Often confused with
Tech LeadLeads the technical choices of a team, often as an individual contributor.
Director of EngineeringLeads several teams through their managers.
Product ManagerOwns what the team builds and why.
Scrum MasterHelps the team apply Scrum and improve how it works.
Scope and focus areas

The same title, very different scopes

Most engineering manager searches are defined first by the team and the stage of the company, then by the focus areas every manager shares.

StrategyCoversTeam roadmapWorks withProduct
OrganizationCovers1:1s · HiringWorks withHR · Director
ExecutionCoversDelivery · On-callWorks withTech Lead
StakeholdersCoversDirectorWorks withProduct Manager
Team healthMorale, retention
MetricsDORA metrics
HiringOnboarding
CareersGrowth plans
Reports toDirector or VP
Levels

What each level means in practice

Titles vary from one company to the next. What changes from one level to the next is the scope you own and the decisions you take.

01First-time manager
  • Leads a small team, often after a tech lead role
  • Learns one to ones, hiring and feedback
  • Stays hands‑on with the code
02Engineering Manager
  • Leads one team with clear delivery
  • Hires and grows engineers
  • Plans with product and handles incidents
03Senior Engineering Manager
  • Leads two teams or a large team
  • Takes decisions across teams with peers
  • Coaches new managers
04Manager of managers
  • Leads other managers
  • Owns a domain with several teams
  • Moves toward a director role
Education and certifications

The paths into the role, and what really counts

For this role, companies look first at teams you grew and engineers you hired and developed. A strong engineering background is expected in most companies.

Common paths
  • Engineering school or master's in computer scienceThe most common path in France, and often expected by large companies.
  • University degree in computer scienceThe most common path in the US.
  • Senior or staff engineer firstMost engineering managers were senior engineers before.
  • Tech lead firstMany move from tech lead to manager on the same team.
Certifications
Management trainingRarely decisiveUseful to structure your practice, and teams you grew count more.
Agile certificationsRarely decisiveUseful for planning, and your delivery results count more.
Technical certificationsRarely decisiveUseful for hands‑on roles, and leadership counts more.

Our view: for this role, a team you grew and engineers you developed often say more than any certificate.

Your interview with us

A conversation with a senior tech recruiter

Your first interview is with one of our senior tech recruiters, who knows the role, its scope and the levels in this guide. The conversation covers your own leadership through real examples, and the technical and leadership interviews come later, with the company. Before the call, we send you the six themes we will cover so you can prepare your examples.

The six themes we share before the call
  1. What you owned yourselfThe teams, hires or projects you led, and your own part in the decisions.
  2. Your environment and its constraintsTeam size, product needs, technical debt, deadlines or on-call: what shaped your choices.
  3. The decisions you madeHow you organised the team, how you planned and which hires first, the options you compared and the reasons for your choice.
  4. The impact of your workWhat changed thanks to your leadership, with numbers when you have them: delivery, retention, engineers promoted or incidents.
  5. How you work with other teamsYour work with product managers, tech leads, peers and your director, and how you settle a disagreement.
  6. What you want nextThe kind of team, company and scope you are looking for in your next role.
What we look at
  • Teams you grew
  • Engineers hired and developed
  • Predictable delivery

The same ground for every candidate. For a given role, every candidate answers the same final questions, built with the hiring manager around what the role really needs.

Ready for the next steps. After our call, we tell you how the company runs its interviews, who you will meet at each step and what each step is meant to assess.

Interviews with the company

What the company will assess, step by step

Each company runs its own process, and we walk you through its steps before you start. Engineering manager processes often combine the steps below, and the depth expected at each step grows with your level.

The steps you will often meet
  1. A leadership interviewQuestions on one to ones, feedback, conflicts, hiring and how you grow people.
  2. A technical interviewA system design or a technical discussion, to check your depth on the stack of the team.
  3. An execution interviewQuestions on planning, delivery, incidents and how you work with product.
  4. Meeting the director and peersHow you work, how you take decisions with others and what the team expects in your first months.
What changes with your level
  • Engineering ManagerYou show how you lead one team, hire and grow engineers and plan with product.
  • Senior Engineering ManagerYou show how you lead two teams, take decisions across teams and coach new managers.
  • Manager of managersYou show how you lead other managers and own a domain with several teams.
Your interview toolkit

How to prepare as an engineering manager

Practical advice for each step of an engineering manager process, from the way you introduce yourself to the questions you ask at the end of each interview.

01Introduce yourself in two minutes

Start with the teams you led, their size and their results. Mention your technical background in one sentence, then close with what you want next.

02Prepare two people stories

Prepare one engineer you helped grow and one hard conversation you led, with the context, your actions and the result.

03Know your team numbers

Prepare the size of your teams, your hiring, your retention and your delivery metrics.

04Keep your technical depth

Most companies check your technical level. Review system design and the stack of the team.

05Show how you work with product

Prepare one example of planning or a trade‑off you made with a product manager.

06Ask about AI tools

Rules on AI coding tools differ from one company to the next. Prepare how your team uses them and how you keep quality high.

Questions you will often hear
  • Tell us about an engineer you helped grow.
  • How do you handle an engineer whose work falls below expectations?
  • How do you balance delivery and technical debt?
  • Walk us through an incident your team handled.
Questions worth asking them
  • How big is the team, and how senior is it?
  • How hands‑on is the role expected to be?
  • How do managers and tech leads share the work?
  • How are engineers promoted?
  • Which delivery or team problems need fixing first?
  • How does the team use AI coding tools day to day?
Where the role leads

Where engineering managers come from, and where they go

The roles people most often hold before this one, and the ones they most often move to.