Engineering manager interview questions: the complete guide

In this article

1. Start here: the learning path
2. What is the role of an engineering manager?
3. What the loop looks like
4. What the research says great managers do
5. How to talk about team health and delivery
6. The core topics, with the short answer for each
7. Questions interviewers ask on engineering management
8. All 32 guides in Engineering management
9. Follow-up questions
10. Sources

Start here: the learning path

Prepare in the order below. The first step tells you what you are being hired to do, and the last turns your stories into answers. Five terms are used throughout, so they are defined first.

Change fail rate

Change fail rate is the share of production deployments that need immediate intervention, such as a rollback or hotfix, and is one of the five software delivery metrics defined by DevOps Research and Assessment (DORA).

Project Oxygen

Project Oxygen is an internal research programme, run at Google, that analysed survey data and comments to find the behaviours of its highest-rated managers.

Attrition

Attrition is the share of a team that leaves in a period, counted as leavers divided by team size.

1. The role. What an engineering manager is accountable for.
2. The loop. Which rounds to expect and how they differ from an engineer's loop.
3. People questions. Performance, conflict, hiring, growth.
4. Delivery and metrics. How you know a team is healthy and shipping.
5. Technical judgement. System design and code review at manager depth.
6. Your stories. A small bank of real examples, rehearsed out loud.

Text description of the diagram

• Google names three manager responsibilities: deliver results, develop people and build community.
• Nine common interview topics are grouped under those three responsibilities.

The map places nine common topics, from team health and low performers to hiring and inheriting a team, under the three responsibilities. Each topic is summarised below.

1. What is the people management round in an engineering manager interview?
2. How do you handle a low performer?
3. How do you measure the health of a team as an engineering manager?
4. Two of your engineers can barely stand each other: what do you do?
5. Growing engineers: interview questions on coaching and promotion, answered
6. Hiring as an EM: how to run a hiring process and decide
7. Have you ever fired someone? Show the feedback, the process and what you changed
8. One-on-ones and hard feedback interview questions, answered
9. What's your management philosophy? Two principles, each tied to a behaviour
10. Keeping and stretching high performers: an EM's guide
11. Inheriting a team: what do you do in the first 90 days?
12. What do you do when the project gets delayed?
13. What is your approach to managing technical debt within a team?
14. How did you manage performance of your team?
15. What is your approach to managing poor performers on your team?
16. How do you manage underperforming employees?
17. How to get teams or people to communicate better with one another?
18. How would you address a skills gap or personality conflict?
19. How do you mentor top talent?
20. How do you coach and develop your engineering team?
21. Director of engineering interview questions on managing managers and org design
22. Have you ever had to terminate an employee's employment?
23. How do you think about hiring standards and maintaining talent density?
24. How do you ensure biases don't impact hiring decisions?
25. What was the best thing you built? How to answer it
26. How do you handle scope creep mid-project?
27. What was the most challenging performance management that you had to handle?
28. How to answer a conflict interview question
29. Engineering team metrics interview answer
30. Tell me about tough feedback you received: how you checked it and what changed

What is the role of an engineering manager?

An engineering manager owns outcomes through other people. The U.S. Bureau of Labor Statistics (BLS) describes the closest government category, computer and information systems managers, as people who plan and direct the work of information technology (IT) staff, determine personnel needs, assess the costs and benefits of projects, and negotiate with vendors (BLS Occupational Outlook Handbook, modified August 2026). The category is wider than engineering management, so read it as context, not as a job description.

Google's own wording is simpler. Its re:Work page names three manager responsibilities: deliver results, develop people and build community (Google re:Work, August 2025). Almost every interview question belongs to one of the three, which makes them a useful way to organise your stories.

Text description of the diagram

• Google's three manager responsibilities are deliver results, develop people and build community.
• Questions on delivery and priorities map to deliver results.
• Questions on feedback, performance and growth map to develop people.

What the loop looks like

An EM loop replaces most coding with rounds on people, execution and judgement. Reports of EM loops in the 43 candidate reports we collected (computed 2026-10-24) ¹ mention a system design or architecture round more often than a coding or code-review round, and a few say a loop had no coding or no technical questions. The reports describe screens with a recruiter and a hiring manager, then rounds on design, people management, cross-functional leadership, project execution and behaviour or culture. These are candidate reports, not any employer's policy, and the mix varies widely by company and by level.

Text description of the diagram

• Candidate-reported loops include screens with a recruiter and a hiring manager.
• Reported rounds include system design, people management, project execution, cross-functional leadership and behaviour or culture.
• Loop reports mention a system design or architecture round more often than a coding or code-review round.

For how the whole loop fits together, see interview loops. The behavioural round uses the same answer structure as the behavioural interview hub, and manager-of-managers questions are in the leadership interviews hub. To see how one employer describes its own loop in public, read the OpenAI interview process page.

What the research says great managers do

Google's research gives interviewers a vocabulary, and using it shows you have read the evidence. Garvin's account of Project Oxygen reports that high-scoring managers had lower team turnover and that manager quality was more strongly tied to retention than seniority, performance, tenure or promotions (Harvard Business Review, December 2013).

Google later expanded its list of behaviours from eight to ten. The ten are: coaches effectively; gives the team autonomy instead of micromanaging; creates an inclusive environment; is productive and results-focused; communicates well by listening and sharing; supports career development; has a clear vision and strategy; has the technical skills to advise the team; collaborates across the company; and makes strong decisions (Nextgov, February 2018). The August 2025 re:Work page still describes ten key behaviours. The list is an employer's research, not a universal standard, so use it as one framework and say so.

How to talk about team health and delivery

Interviewers ask how you know a team is healthy and shipping, and the strongest answers use a small set of measures plus judgement. DORA names five delivery metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate (dora.dev, updated January 2026). Pair them with people measures such as attrition.

With an illustrative team of 8 engineers where 2 leave in a year, attrition is 25.0%, and with 40 deployments of which 6 fail, the change fail rate is 15.0% ². The inputs are made up; the interview point is to define each measure, say what you would do when it moves, and never present one number as proof of health.

The core topics, with the short answer for each

Each summary below is the short answer you can give today.

The people management round

Expect questions on hiring, feedback, performance and conflict, and expect the interviewer to push past your first example. Prepare two real stories per area. Give each one the same shape: the situation in a sentence, what you personally did, the result in plain terms, and what you changed afterwards. Interviewers listen for specifics and for ownership of the outcome, including the parts that went badly. Avoid answers that describe what "a good manager" does in general, because they sound rehearsed. Keep each story short and be ready for the follow-up "what would you do differently?".

How do you handle a low performer?

Start with clarity: was the expectation clear, written and understood? Then check for causes you can fix, such as unclear scope, a poor fit of tasks to strengths, personal circumstances or missing support. Agree a time-bound plan with specific, observable goals and regular check-ins, and be explicit about what happens if it is not met. Interviewers listen for early and honest feedback, for fairness to the person and the team, and for a willingness to make the final decision rather than drift. A strong answer also names how you protect the rest of the team's workload while the plan runs.

Team health as an EM question

Name two or three signals, the measure behind each, and the action when one worsens. Delivery can be read through the DORA metrics, retention through attrition, and psychological safety through how readily people raise problems, disagree in meetings and admit mistakes. Say how you would collect the softer signals, for example through one-to-one conversations and anonymous surveys, and how often you would look. Add one example of a number that looked healthy while the team was not, so the interviewer hears that you treat measures as prompts for a conversation, not as the verdict.

Two of your engineers can barely stand each other

Separate the work conflict (design disagreements, unclear ownership) from the personal one (tone, trust, history). Speak to each person separately first, listen for the facts they agree on, then bring them together to agree working norms, such as how to review each other's changes and how to escalate. Say what you would escalate and when: harassment or discrimination goes to your human resources team at once, and a conflict that keeps harming delivery needs a firmer decision from you. Interviewers listen for whether you act early and stay neutral on the person but decisive on the outcome.

Growing engineers

Describe how you find out what each person wants, which is rarely a promotion alone. Then cover how you match growth to work: stretch assignments, ownership of a larger area, pairing with a stronger peer, and honest feedback on the gap to the next level. Name how you check progress, for example a written growth plan reviewed every quarter. Strong answers include a specific engineer you grew, what the plan was and what happened, including any part that did not work. Also be ready for the opposite case: someone who is content at their level and whom you still treat as valuable, with work that suits them and honest expectations.

Hiring as an EM

Cover the whole pipeline: defining the role and the bar before you open it, sourcing a varied candidate pool, a structured loop with consistent questions and scoring, and a decision made on evidence rather than first impressions. Explain how you calibrate with other interviewers, how you handle a split vote, and how you sell the role to a candidate you want. Interviewers also ask how you build a team, so describe the mix of skills and experience you aim for and why. Name one hire you are proud of and one you would not repeat, and say what each taught you about your bar.

Have you ever fired someone?

If you have, tell the story plainly: the expectations, the support and feedback you gave, the plan, the decision, and how you handled the conversation and the team afterwards. If you have not, say so honestly and describe how you would approach it, including involving your human resources team, documenting, and treating the person with dignity. Interviewers also test a related idea, sometimes called the keeper test: whether you would act when someone is not failing but is no longer a strong fit. A thoughtful answer shows you take the decision seriously and do not enjoy it.

1:1s and hard feedback

A one-to-one (1:1) is a recurring private meeting between a manager and one report. Say that it belongs to the report: they set much of the agenda, and you use it for support, career and blockers, not only status. For hard feedback, describe being specific, timely and about behaviour and its effect, then agreeing the next step together and following up. Pair it with a coaching or performance plan when the problem is larger. Give a real example of a difficult conversation and how the person responded, and say what you would do differently next time.

What's your management philosophy?

Give a short statement you could defend with stories: for example, set clear outcomes, give autonomy, and step in early when something drifts. Then back each part with an example so it does not sound like a slogan. Interviewers often follow with "what is your biggest mistake as a manager?", so prepare one real mistake, its effect on a person, what you changed and how you know the change held. Avoid a philosophy that you cannot connect to a decision you actually made, and keep the whole statement to a few sentences so the stories carry it.

Keeping and stretching high performers

High performers often leave quietly, so a good answer starts with noticing: regular career conversations, fair pay and recognition raised with your own manager, and meaningful work. Describe how you stretch them without burning them out, for example a larger scope, leading a project, mentoring or representing the team, and how you spread the load so they are not the single point of failure. Interviewers also ask about a time you nearly lost a top performer and what you did. Be honest about what worked, what did not, and what you learned, and say how you would spot the warning signs sooner next time.

Inheriting a team

Describe your first weeks as listening first: one-to-one conversations with each person, learning the work and the history, and asking what to keep and what to fix. Then pick a few early, visible improvements and share your plan. Cover what you do if morale is low after a previous manager left, if you have too few engineers, or if the team disagrees with you: be open about your reasoning, ask for objections, and decide. Interviewers listen for humility about what you do not yet know and for a plan with checkpoints, such as what you will have learned by the end of the first month.

Questions interviewers ask on engineering management

These are the question families candidates report, written in our own words, with what each one tests. Pair them with your own prompts from the questions to ask the interviewer page, and prepare your opener with tell me about yourself.

People and performance

• How would you handle an engineer who is underperforming? Tests fairness, clarity and follow-through.
• Tell me about a time you had a hard conversation with a report. Tests directness and care.
• Have you ever let someone go? Tests judgement and how you treat people at the worst moment.
• Two engineers will not work together; what do you do? Tests conflict handling without taking sides.
• How would you handle a strong performer who creates conflict? Tests whether results excuse behaviour.

Growth and hiring

• How do you coach people, and how do you assess talent? Tests whether you have a method.
• Tell me about someone you mentored and how they progressed. Tests specifics and outcomes.
• How do you keep top performers motivated and stretched? Tests retention thinking.
• How do you make a hiring decision, and how do you build a varied candidate pool? Tests structure and fairness.

Delivery and priorities

• What do you do when a project is delayed? Tests early signals and honest communication.
• How do you balance technical debt against new features? Tests prioritisation with trade-offs.
• How do you measure a project's success? Tests defining measures before the work.

Judgement and technical depth

• What is your approach to managing technical debt within a team? Tests whether you can reason about code health.
• How do you handle a failed production deployment? Tests calm, ownership and learning.
• What is your management philosophy, and what is your biggest mistake? Tests self-awareness.
• How would you lead a team through a significant change, or inherit a team with low morale? Tests listening and a plan.

Follow-up questions

How do I prepare for an engineering manager interview?

Learn the loop, build a bank of six or seven real stories mapped to deliver, develop and build community, and rehearse them aloud. Prepare one system design and one team-health answer at manager depth.

What is the role of an engineering manager?

An engineering manager is accountable for a team's delivery, growth and hiring, and works through the team. The BLS and Google descriptions above give two views of it.

Do engineering managers have to do LeetCode?

It depends on the employer and level. In the 43 candidate reports we collected, some loop reports mention a coding or code-review round and a few say there was none ¹, so ask the recruiter which rounds apply. The coding interviews hub covers the format if one is included.

Should I grind coding problems for an EM loop?

Only after confirming a coding round exists. System design came up more often than coding in those reports ¹, so split preparation between design depth and people stories.

What does "not technical enough" feedback mean?

It usually means the interviewer could not hear technical judgement in your answers, such as why you chose a design or how you reviewed a risky change. Two of the reports give a reason a candidate was not progressed: one cited technical depth and one cited missed management signals ¹. Practise explaining trade-offs in the system design hub style.

Sources

1. How Google Sold Its Engineers on Management — Harvard Business Review (David A. Garvin), 1 Dec 2013
2. Google Is Expanding Its List of What It Takes to Be a Great Manager — Nextgov, 28 Feb 2018
3. Following the data: the research behind great managers — Google re:Work, 1 Aug 2025
4. DORA software delivery performance metrics — DORA (Google Cloud), 5 Jan 2026
5. Computer and Information Systems Managers, Occupational Outlook Handbook — U.S. Bureau of Labor Statistics, 27 Aug 2026