Courses › Behavioral Interviews › Question Themes

Engineering Manager Questions

Hiring, performance management, team health, delivery and managing up in EM loops.

Engineering manager (EM) loops reuse many standard behavioral questions, but they add a whole category about people management: hiring, performance, team health, delivery and working with your own manager. Engineers moving into management, and tech leads who manage informally, should prepare for these as well.

In many EM loops, the behavioral and "people" rounds count as much as the technical ones, and sometimes more.

What EM interviewers evaluate

Common questions by theme

Hiring and team building

"How do you decide what role to hire for next?"
"Tell me about a hire you're proud of, and one that didn't work out."
"How do you make your interviews fair and consistent?"

Performance

"Tell me about the hardest performance conversation you've had."
"Have you ever had to manage someone out? Walk me through it."
"How do you handle a high performer who is hard to work with?"

Growth

"Tell me about someone whose career you significantly changed."
"How do you run 1:1s?"

Delivery and prioritization

"Your team is going to miss a committed date. What do you do?"
"How do you balance roadmap work with tech debt and reliability?"

Team health and change

"How have you handled a reorg or a layoff on your team?"
"Tell me about a conflict between two of your engineers."
"How do you know your team is healthy?"

Managing up

"Tell me about a time you disagreed with your manager or with leadership."
"How do you represent your team's work to leadership?"

Answering performance questions well

These are the questions EM candidates most often answer poorly. A strong answer covers:

How you noticed: specific, observed gaps such as missed commitments or review feedback, not a vague impression.
Clear expectations: what "good" looked like, written down and agreed.
Support: what you changed to help, such as pairing, smaller scope or clearer goals.
A timeline: regular check-ins, documented progress, involving HR when the process requires it.
The decision: improvement, a move to a better-fitting role, or a respectful exit.
Fairness and dignity throughout, plus how you protected the rest of the team.

[!EXAMPLE] Outline: a performance turnaround A senior engineer on my team had missed three sprint commitments in a row, and their reviews were getting rushed. In our 1:1 I shared the specific examples and asked what was going on; they were overloaded by an on-call rotation that had grown without anyone noticing. We moved them off two rotations, agreed on written goals for the next six weeks, and met weekly. Their delivery recovered within a month. I then rebalanced on-call for the whole team so the problem couldn't build up again, and I now review on-call load in my monthly team health check.

[!WARNING] Common failure modes - Waiting too long. "I gave them six months before saying anything" signals conflict avoidance. - Only "we". Interviewers need to know what *you* did as the manager. - Blaming the person. Describe behavior and impact, and what you changed in the system. - Sharing confidential details about health, compensation or HR cases. Keep them general.

Philosophy questions

Expect "What's your management philosophy?" or "How would your team describe you?" Give two or three principles, each backed by a short real example. A list of ideals without evidence sounds like a template.

Hypothetical questions

Some loops use scenarios: "You inherit a team with low morale and a missed launch. What do you do in your first 90 days?" Structure the answer:

Listen first: 1:1s with everyone, talk to stakeholders, read the incident history.
Diagnose: name likely causes and how you'd check each one.
Act on quick wins that build trust.
Set a longer plan with measures you'd track, such as delivery predictability, attrition and survey results.

Your technical credibility

EM loops usually include a system design round and sometimes coding. Interviewers want to know you can judge technical proposals, ask good questions and spot risk, not that you write the most code. Be ready to talk about a technical decision your team made, your role in it, and what you'd do differently. See Incidents & Technical Judgment.

Preparing

Build a story bank with an EM column: at least one story each for hiring, a performance issue, someone you grew, a missed deadline, a conflict, a reorg or other big change, and disagreeing with leadership.
Have numbers ready: team size, attrition, promotions, delivery measures and hiring numbers.
Be ready to explain why you want to manage. If you're moving from engineering, explain what you've done that shows you're ready.