Engineering Manager interview questions and how to answer them
Engineering manager loops are mostly about people, but they'll still check that you can hold your own in a design review. Expect stories about hard feedback, missed deadlines, and hiring calls, and expect follow-up questions that dig past the polished version. Bring real examples with names changed and details intact.
What happens in each round
- 1
Recruiter screen
What happens
Team size you've managed, whether you've done hiring and performance reviews, and why you want this role and not a staff engineer job.
- 2
Hiring manager conversation
What happens
Your management style, how you run one-on-ones, and whether your instincts match how their director wants teams run.
- 3
People and leadership round
What happens
Specific stories about underperformance, conflict, coaching, and retention. They'll push for what you actually said and what happened after.
- 4
Execution and delivery round
What happens
How you plan, estimate, handle scope creep, and keep a roadmap honest with product and design partners.
- 5
System design or technical round
What happens
Enough depth to guide architecture tradeoffs, ask sharp questions in design reviews, and spot when a team is heading for trouble.
- 6
Cross-functional or skip-level chat
What happens
Whether a product manager or senior engineer would want to work with you, and whether you listen more than you pitch.
Questions you're likely to get
1.Tell me about a time you managed someone who was underperforming.
Why they ask
This is the conversation new managers dodge. They want to see you acted early, stayed fair, and documented it.
How to answer
- Describe the gap in concrete terms: missed reviews, slipped tickets, not personality
- Explain how you raised it directly in a one-on-one and agreed on clear expectations
- Show the support you offered, like pairing, smaller scoped work, or clearer specs
- Give the outcome honestly, including if the person left, and what you'd do sooner next time
2.How do you run your one-on-ones?
Why they ask
One-on-ones are the core tool of the job. A vague answer usually means they're status updates in disguise.
How to answer
- Say the engineer owns the agenda, often in a shared doc
- Keep project status out of it since standups and Jira cover that
- Cover career growth, blockers, and feedback in both directions on a regular rhythm
- Mention how you adjust for a new hire versus a senior engineer
3.Walk me through a project that slipped. What did you do?
Why they ask
Every team misses dates. They want to know if you spot it early and tell people before they find out on their own.
How to answer
- Name the signal you noticed first, such as a burndown flattening or a dependency stalling
- Explain how you reset scope or the date with your product partner
- Show how you told stakeholders, and how early
- Share what you changed in planning afterward
4.How do you decide between paying down technical debt and shipping features?
Why they ask
This is the tension between engineers and product that you'll referee every quarter.
How to answer
- Tie debt to a cost product cares about, like slower releases, on-call pages, or incidents
- Describe a standing budget for maintenance work in each sprint or quarter
- Give a real example where you made the case and what you traded
- Admit when you let debt pile up and what it cost
5.Tell me about a hire you got wrong.
Why they ask
Everyone who has hired has made a bad call. Pretending otherwise suggests you haven't hired much.
How to answer
- Say what the interview loop missed or what signal you overweighted
- Explain how you noticed after they started and what you did
- Show the change you made to your interview process or rubric
6.How do you grow a senior engineer toward staff level?
Why they ask
Keeping strong senior engineers is hard. They want to see you create scope, not just write nice feedback.
How to answer
- Explain how you learn what staff means at your company and share that bar openly
- Describe finding cross-team problems they can own, like a migration or a shared library
- Show how you give them visibility with other leaders
- Mention building the promotion case together over time
7.Design a notification service for a mobile app, then tell me how you'd staff it.
Why they ask
Manager design rounds check that you can reason about architecture and turn it into a team plan.
How to answer
- Clarify requirements first: delivery guarantees, volume, user preferences
- Sketch the main parts like a queue, workers, and push provider integrations
- Call out the risky pieces and where you'd want a senior engineer
- Break it into milestones a small team could ship in stages
8.Two senior engineers disagree strongly on an architecture choice. What do you do?
Why they ask
They want to know if you can settle a fight without picking favourites or letting it drag on.
How to answer
- Get both views written down, often as a short design doc with options
- Agree on the criteria before comparing, like cost, risk, and team familiarity
- Set a decision date and name who decides if there's no consensus
- Follow up so the person who lost the argument still owns part of the work
9.How do you handle a product manager who keeps adding scope mid-sprint?
Why they ask
Your relationship with product decides whether your team has any calm weeks.
How to answer
- Start by understanding why the requests keep coming, such as sales pressure or unclear priorities
- Make the tradeoff visible: this goes in, that comes out
- Agree on a process together, like a change request threshold
- Keep the relationship warm, since you'll work with them for a long time
10.What does your team's on-call and incident process look like?
Why they ask
On-call is where burnout starts. They want to see you protect people and still keep systems reliable.
How to answer
- Describe the rotation and how you keep it fair
- Explain blameless postmortems and how action items actually get done
- Show how you track paging load and push back when it's too high
11.Why do you want to manage rather than stay an engineer?
Why they ask
People who manage for the title or the pay tend to struggle and leave.
How to answer
- Point to moments you enjoyed, like a mentee's promotion or fixing a broken process
- Be honest about what you miss from coding
- Show you've thought about the staff track and chose this on purpose
12.Tell me about a time you disagreed with your own manager.
Why they ask
They want a manager who pushes back up the chain but commits once a call is made.
How to answer
- Describe the disagreement and why it mattered to your team
- Show how you raised it privately with evidence
- Explain what happened and how you represented the decision to your team
Mistakes that sink good candidates
Telling stories where you wrote the key code yourself to save the project
Talking about your reports as resources or headcount instead of people
Having no example of hard feedback you delivered
Badmouthing your last company or your current team
Need more Engineering Manager interviews to prep for?
HeroApply applies to Engineering Manager jobs that match you, every day. 4,376 jobs are open today.