Engineering Manager interview questions
Grouped by interview stage, with what a strong answer actually sounds like — the part most question lists leave out.
When interviewing a engineering manager, structure questions by stage and assess against the role's actual requirements. Engineering managers are accountable for a team's delivery, quality and people. The questions below cover screening through final round, each with what a strong answer sounds like and the warning signs of a weak one.
How to use these
Pick four to six for a 45-minute interview — not all 7. A well-followed-up question takes six to eight minutes, and the information is almost always in the follow-up rather than the first answer. Ask the same core questions of every candidate so you can actually compare them; vary the follow-ups.
Screening questions
Tell me about someone on your team who was underperforming. What did you do?
Why ask it: The clearest signal of whether someone actually manages or avoids managing.
A strong answer: Named the problem early and directly, was specific about the gap, gave support and a timeline, and saw it through either way.
A weak answer: Waited and hoped, or moved straight to exit with no attempt to fix it.
How do you know whether your team is doing well?
Why ask it: Reveals whether they manage by evidence or by vibes.
A strong answer: Combination of delivery signals, quality signals and direct conversation. Sceptical of single metrics.
A weak answer: Velocity alone, or "I just know".
Core questions
Describe a time you disagreed with a decision from above and had to implement it.
Why ask it: Managers spend real time here, and how they handle it shapes the team's trust.
A strong answer: Argued privately, committed publicly, was honest with the team without undermining the decision.
A weak answer: Told the team it was a stupid decision from management.
How much do you code now, and how much do you want to?
Why ask it: A common failure mode is a manager who is really a reluctant senior engineer.
A strong answer: Honest, realistic, clear that the team's output matters more than their own commits.
A weak answer: Wants to be the top contributor, or has lost all technical engagement.
Walk me through how you would run your first 90 days here.
Why ask it: Tests whether they have a method or will improvise.
A strong answer: Listens first, meets everyone, identifies the real constraint before changing things.
A weak answer: Arrives with a reorganisation plan.
Final questions
Tell me about a hire you made that did not work out.
Why ask it: Everyone who has hired enough has one. Denial signals inexperience or lack of reflection.
A strong answer: Specific about what the process missed and what they changed as a result.
A weak answer: Never made a bad hire.
How do you protect your team from organisational noise without isolating them?
Why ask it: A defining part of the job that is easy to do badly in either direction.
A strong answer: Filters rather than blocks; keeps the team informed about what genuinely affects them.
A weak answer: Passes everything through, or keeps the team in the dark.
Red flags for this role
- Cannot describe a difficult people conversation
- Measures the team by their own output
- No examples of anyone growing under them
What a engineering manager actually does
Engineering managers are accountable for a team's delivery, quality and people. The job is mostly judgement, communication and unblocking — the technical depth exists to make those decisions well, not to write most of the code.
See the full engineering manager job description, including how to assess each requirement.
Generate questions specific to your role — and that account for what previous interviewers already asked — with the free interview question generator.