Engineering manager interview questions test whether you can grow people, deliver through a team, and make sound technical and organizational calls without writing the code yourself. The three questions you are most likely to get are "How do you handle an underperforming engineer?", "Tell me about a project that slipped and what you did" and "How do you balance technical debt against new features?"
This guide lists 32 questions grouped by area, with what a strong answer shows for each, five sample answers we wrote, a table of what interviewers listen for, and how to practice. It is a question bank; for a round-by-round prep plan, see our engineering manager interview prep guide.
How an engineering manager interview usually runs
Loops differ a lot by company size and by whether the role is a first-line manager or a manager of managers. A common shape:
- Recruiter screen. Team size you have managed, why management, scope you want.
- Hiring manager interview. Usually a director. Your management philosophy and a deep dive on one team you ran.
- People management round(s). Performance, hiring, feedback, conflict, career growth. Often the most heavily weighted part.
- Execution or delivery round. Planning, prioritization, a project that went wrong, working with product.
- Technical round. Many companies include a system design or architecture discussion pitched at manager level; some still include coding, some don't. Ask.
- Cross-functional interviews. A product manager, a peer manager or a senior engineer who would report to you.
Ask the recruiter which of these apply and whether the technical round is system design, coding or an architecture review of your past work. If it's system design, our system design interview overview and the free system design cheat sheet are a good refresher.
32 engineering manager interview questions, grouped by area
People management and performance
- How do you handle an underperforming engineer? Shows you diagnose first (skill, will, clarity, personal circumstances), set clear written expectations with a timeline, support, and act if nothing changes.
- Tell me about someone you managed out. Shows you can make the hard call fairly, with documentation and dignity, and reflect on what you'd do earlier next time.
- How do you run one-on-ones? Shows they're the report's meeting: their agenda first, career and feedback regularly, not status updates.
- How do you give difficult feedback? Shows specific, timely, behavior-focused feedback and a follow-up.
- How do you help a senior engineer grow to staff level? Shows you find scope and sponsorship, not just advice.
- How do you handle a high performer who is difficult to work with? Shows you hold everyone to how they work, not just what they ship.
- How do you prevent burnout on your team? Shows you watch load and on-call patterns and protect focus time.
- How do you handle promotions and calibration? Shows you build evidence over time and advocate with data, not adjectives.
Hiring and team building
- How do you hire well? Shows a defined bar, structured interviews, trained interviewers and a fast, respectful process.
- Tell me about a hire that didn't work out. Shows you found what the process missed and changed it.
- How do you build a diverse team? Shows concrete practices: wider sourcing, structured scoring, consistent questions.
- How do you onboard a new engineer? Shows a plan with a first commit early, a buddy, and clear 30/60/90-day expectations.
- Your team doubles in a year. What changes? Shows you think about splitting teams, leads, rituals and communication before it breaks.
Delivery and execution
- Tell me about a project that slipped. Shows early detection, honest communication, scope trade-offs and what you changed in planning.
- How do you estimate and plan? Shows ranges and confidence levels, not single dates, and replanning as you learn.
- How do you balance technical debt against features? Shows you tie debt to business risk or speed, agree a budget with product, and track it.
- How do you measure your team's performance? Shows team-level delivery and outcome signals, used for improvement rather than ranking individuals.
- Walk me through how you handled a major incident. Shows calm coordination, clear roles, a blameless review and follow-through on fixes.
- How do you handle conflicting priorities from two stakeholders? Shows you make the trade-off visible and get a decision from the right owner.
- When do you say no to product? Shows you say "not now, and here's the cost" with options, not a flat refusal.
Technical judgment
- How technical are you today? Shows an honest answer: what you still do hands-on and how you stay credible in design reviews.
- Tell me about a technical decision you disagreed with on your team. Shows you let the team own decisions within guardrails, and step in only when risk is high.
- How do you decide between rewriting and refactoring a system? Shows incremental options first and a clear business case for a rewrite.
- Design a system your team might own. Shows you can reason about requirements, scale and trade-offs at a whiteboard, even if you're rusty on details.
- How do you run code review and design review on your team? Shows clear norms and turnaround expectations, and that reviews teach rather than gatekeep.
Behavioral and leadership
- Why do you want to be an engineering manager? Shows motivation centered on multiplying others, not status.
- What is your management style? Shows a style you can describe with examples and that you adapt by person. See our guide to "What is your leadership style?".
- Tell me about a time you disagreed with your manager. Shows you push back with data, then commit. Our disagreeing with your manager guide has the structure.
- Describe a change you led across teams. Shows influence without authority.
- What was your biggest mistake as a manager? Shows real ownership and a changed habit.
- How do you communicate bad news upward? Shows early, specific and with a plan.
- How do you build trust with a team you inherit? Shows listening first: one-on-ones with everyone before changing anything.
What interviewers are listening for
| Area | Sample question | What they are listening for |
|---|---|---|
| Performance management | Handle an underperformer | Diagnosis before action, clear written expectations, follow-through |
| Hiring | How do you hire well? | A defined bar and a structured process |
| Delivery | A project that slipped | Early signal, honest communication, scope trade-offs |
| Prioritization | Tech debt versus features | Debt framed as business risk, an agreed budget |
| Metrics | How do you measure your team? | Team-level signals used for improvement, not ranking |
| Technical judgment | Rewrite or refactor? | Incremental options first, a business case |
| Self-awareness | Your biggest mistake as a manager | Real ownership and a changed habit |
Metrics: what to say when asked how you measure a team
Interviewers often probe whether you know industry-standard delivery metrics and whether you would misuse them. As of October 2026, DORA (the DevOps Research and Assessment program) lists five software delivery performance metrics in two groups:
- Throughput: change lead time, deployment frequency and failed deployment recovery time.
- Instability: change fail rate and deployment rework rate.
A strong answer names a few of these, adds an outcome measure from product (adoption, a customer metric) and a health signal (on-call load, attrition, engagement), and says that you look at trends at team level and never use them to rank individual engineers.
Five sample answers (examples we wrote)
"How do you handle an underperforming engineer?"
Example (first-line manager): "First I figure out why. With one engineer on my last team, code reviews were slow and his PRs bounced repeatedly. In our one-on-one I learned he'd moved from backend to frontend and was quietly struggling with our React stack. That was a skill gap, not motivation. We agreed on written expectations for six weeks: smaller PRs, pairing twice a week with a senior frontend engineer, and a check-in every Friday. By week five his PRs were landing on the first or second review. If it had been a motivation or conduct issue, I'd have moved to a formal plan with HR sooner."
"Tell me about a project that slipped."
Example (Situation, Task, Action, Result): "We committed to migrating billing to a new provider in one quarter. Four weeks in, we found the old system had undocumented proration rules. My task was to reset expectations without losing trust. I told my director and the PM that week, with two options: cut annual plans from phase one and keep the date, or move the date six weeks. We cut scope, shipped monthly plans on time, and annual plans five weeks later. I changed our planning to include a two-week discovery spike before committing to dates on any migration."
"How do you balance technical debt against new features?"
Example: "I treat debt as a business problem, not an engineering wish list. I ask the team to rank debt by the cost it creates: incidents, slow delivery, or on-call pain. Then I agree a standing budget with the PM, typically a share of each sprint, and spend it on the top items. For big items I write a one-page case: 'This queue rewrite cuts our weekly pages from about six to one and unblocks the reporting project.' That makes the trade-off the PM's decision as much as mine."
"Why do you want to be an engineering manager?"
Example (senior engineer moving into management): "Over the last two years I noticed the work I was proudest of wasn't my code. It was getting two junior engineers to the point where they led features, and running our incident reviews so they actually changed things. I enjoy making a team better more than making a module better. I also know what I'm giving up. I'll keep doing design reviews and some small fixes, but not critical-path work, because that would make me a bottleneck."
"How do you build trust with a team you inherit?"
Example: "I listen before I change anything. In my first two weeks I hold one-on-ones with everyone and ask the same questions: what's working, what's frustrating, what would you change if you were me. Then I play back the themes to the team and pick one quick fix they asked for. On my last team, that was moving standup off the time zone that didn't suit half the team. Small, but it showed I'd act on what they said. Bigger changes came after a month."
Questions to ask the interviewer
- "How many direct reports would I have, and what's the mix of seniority?"
- "How much hands-on technical work do you expect from managers here?"
- "What is the biggest problem this team has right now?"
- "How are engineering managers evaluated, and by whom?"
For questions to ask when you are the candidate meeting your future manager, see our questions to ask an engineering manager. For more general options, see questions to ask the interviewer.
How to practice for an engineering manager interview
- Write your six stories and practice telling each in under two minutes, with a clear result.
- Prepare your management philosophy in three sentences you can back with examples.
- Refresh system design if the loop includes it: practice one design out loud with a 45-minute timer.
- Do a scored mock. CoPilot Interview's Mock Interview builds questions from your résumé and the job description; you choose the level, 3, 5 or 8 questions, and a mix of behavioral and system design. It reads each question aloud, scores your spoken answer out of 10 with what to fix and a model answer, and ends with a report card. The browser mock at /ai-mock-interview has behavioral and system design tracks with no install.
Moving from engineering into your first manager role? Our general manager interview questions guide covers the people-management questions every field asks.
Rehearse your management stories out loud
Mock Interview builds questions from your résumé and the job description, scores each spoken answer out of 10 and shows a model answer. Free for 15 minutes a day.
Try a free AI mock interviewFAQ
What are the most common engineering manager interview questions?
Expect "How do you handle an underperforming engineer?", "Tell me about a project that slipped", "How do you balance technical debt and features?", "How do you hire well?" and "Why do you want to be a manager?".
Do engineering manager interviews include coding?
It depends on the company. Many include a system design or architecture round at manager level; some include coding and some do not. Ask the recruiter what the technical round covers.
What metrics should an engineering manager mention in an interview?
As of October 2026, DORA lists five delivery metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate. Pair a few of them with a product outcome and a team health signal, and say you use them at team level, not to rank individuals.
How do I answer "How do you handle an underperformer?"
Diagnose the cause first, set clear written expectations with a timeline, offer specific support, check in regularly, and say what you would do if nothing improves. Use a real example with a measurable outcome.
How many stories should I prepare for an engineering manager interview?
Six reusable stories cover most loops: an underperformer, a great hire, a bad hire, a slipped project, a conflict, and a decision you got wrong.
How is a manager-of-managers interview different?
Expect more on org design, developing managers, setting strategy across teams and handling problems through other managers rather than directly with engineers.