general

The Engineering Manager Interview: A Complete Guide

Engineering manager loops confuse strong candidates because they're really four interviews wearing one badge: people leadership, execution, technical judgment, and (at senior levels) organisational design. Engineers moving up over-prepare the technical and under-prepare the people rounds; career managers do the reverse. This guide maps all four so nothing surprises you. (If you're still deciding whether to make the jump at all, start with IC to manager.)

The typical loop

A recruiter screen and hiring-manager conversation, then a loop of four to six rounds: people management, execution/delivery, technical (system design and/or architecture discussion — real coding is rare but not extinct), cross-functional collaboration, and at many companies a values/leadership round. You are being assessed simultaneously as a leader of people, a shipper of projects, and an engineer who hasn't lost the plot technically.

The people round

The heart of the loop. Expect:

Tell me about the lowest performer you've managed. What did you do, and how did it end?
How have you retained someone who was about to leave — or decided not to?
Walk me through a hard piece of feedback you delivered. What changed?
Tell me about growing someone into a promotion. What was your contribution?
Two of your reports are in conflict. What do you actually do — mechanics, not philosophy?

What graders listen for: specificity and follow-through. Real names redacted, real timelines, real outcomes — including the ones where the outcome was a managed exit. The red flag is the candidate whose every story ends "and they turned it around" with no visible mechanism. Structure with STAR, but let the interpersonal reasoning breathe.

The execution round

Can you ship through a team rather than around it?

Tell me about a project that was going to miss its date. When did you know, and what did you do?
How do you decide what your team works on? Walk me through a real prioritisation.
Describe a time you cut scope. Who pushed back and how did you handle it?
What do you measure? What have you stopped measuring, and why?

Strong answers show early detection (you knew in week 3, not week 11), honest communication upward, and mechanisms — planning cadences, risk registers, definitions of done — that outlive any single project.

The technical round

The bar is technical credibility, not virtuosity: can you interrogate a design, smell a risky migration, and represent your team's work to senior engineers without a translator? Expect a system design conversation graded on judgment and trade-offs, or a deep-dive on a system you owned. The failure mode isn't rustiness — it's bluffing. "Here's how I'd evaluate that, and here's where I'd lean on my staff engineer" is a good EM answer.

The org-design round (senior EM / EM2+)

Larger-scope roles add organisational reasoning: how would you split this 25-person team? What's your approach to on-call health? How have you handled a reorg you disagreed with? Platform team or embedded infra engineers — how do you decide? There are no right answers, only trade-offs argued from real experience; Conway's law citations impress nobody without a story attached.

Preparing

Inventory your management artifacts. Your last two years contain every story you need: performance cases, promotions, conflicts, misses, reorgs. Write them up as a story bank before rehearsing anything.
Rehearse the numbers. Team size, attrition, delivery stats, promo rate. Managers who don't know their own numbers read as passengers.
Refresh system design if you've been away from the keyboard — the prerequisites and one or two case studies like WhatsApp are usually enough to be fluent again.
Do a mock loop. People-round answers especially benefit from an observer — the difference between empathy and evasion is delivery, and you can't hear your own.

Interviewing for EM roles? Get matched with a coach who has hired and been hired as an engineering leader — and can run the people round against you for real.