Use these questions to interview Engineering Manager candidates at {{Company name}}. Management interviews are especially vulnerable to rehearsed philosophy, so every group here pushes for specific people, specific projects, and what the candidate actually said and did. Where a story sounds smooth, ask what happened next — real management stories have residue.

People management and coaching

• Tell me about the lowest performer you have managed. Walk me through what you did, week by week, and how it ended.
• Tell me about your best engineer. What did you do to keep them growing rather than just keep them?
• Describe a time you gave feedback that was hard to deliver. What were your actual words?
• How do you run one-on-ones? What did you discuss in your last three?
• Tell me about someone you managed out. Looking back, what would you have done sooner?
• How do you detect burnout before people tell you?

What good looks like: strong managers give specifics with kindness intact — real timelines for performance cases, actual phrasing from hard conversations, and growth stories where the engineer's scope visibly changed. Vague answers about supporting people, with no names-shaped details and no endings, mean the candidate has not done the hard parts.

Delivery and execution

• Walk me through the most complex project your team delivered. What was your specific role in it shipping?
• Tell me about a project that was clearly slipping. When did you know, and what did you change?
• How do you make commitments to stakeholders when estimates are uncertain?
• What does your team's process look like — and what did you change from the process you inherited?
• How do you balance roadmap work against tech debt and operational load? Show me the actual split.
• Tell me about descoping something painful to hit a date. How did you decide what to cut?

What good looks like: the best answers show the manager creating clarity — surfacing slips early rather than heroically recovering late, changing scope explicitly instead of silently burning the team, and inheriting processes with respect but not reverence. Watch for delivery stories where the manager's only tool was asking people to work more.

Technical judgment

• How technical do you stay, and what did you personally review or build in the last month?
• Tell me about a technical decision you overruled your team on. Were you right?
• How do you evaluate an architecture proposal outside your own depth?
• Describe a technology bet your team made under your watch. How did it age?
• What signals tell you a system needs investment before it fails loudly?

Hiring and team building

• Walk me through the last engineer you hired: sourcing, process, and how they performed after a year.
• Tell me about a hire that did not work out. What did you miss in the process?
• How do you build an interview loop that predicts performance rather than polish?
• What does your onboarding look like — what can a new engineer do after week one and month one?
• How have you built diverse teams in practice, beyond intentions?

Stakeholders and organizational communication

• Tell me about a conflict with product over priorities. How was it resolved?
• How do you communicate bad news upward — a slip, an incident, an attrition risk?
• Describe advocating for something unpopular that your team needed.
• How do you represent your team's work to executives who want it faster and cheaper?
• Tell me about a reorganization or direction change you had to carry to your team without fully agreeing with it.