Engineering Manager Behavioral Questions: 50 Patterns and a Framework

By /
⏱ 3 min read

Engineering manager behavioral interviews live or die on specifics. The interviewer wants to verify that you have actually done the things on your resume — and that you can describe them with the texture of someone who lived them. Vague answers (“I made sure the team was aligned”) signal to hiring committees that you may have been a bystander rather than a driver.

The STAR/CAR framework

Two common acronyms, same idea:

  • Situation: context, scope, stakes
  • Task: what you were asked to do
  • Action: what you specifically did (not “we”)
  • Result: outcome with numbers

The simpler CAR version drops the redundant Task/Situation split: Context, Action, Result.

The 50 most common EM behavioral questions, organized

Hiring (5)

  1. Tell me about a time you hired someone who turned out to be a great fit
  2. Tell me about a hire that did not work out
  3. How do you assess for technical depth in an interview?
  4. How do you assess for cultural fit without unconscious bias?
  5. Tell me about a time you broke a tie between two strong candidates

Performance management (8)

  1. Tell me about a time you had to give difficult feedback
  2. Tell me about a time you put someone on a PIP
  3. Tell me about a low performer you helped turn around
  4. Tell me about a time you let someone go
  5. How do you write a meaningful performance review?
  6. How do you handle a high performer who is also a difficult teammate?
  7. How do you reward someone you cannot promote yet?
  8. Tell me about a calibration discussion that did not go your way

Conflict (6)

  1. Tell me about a time you disagreed with your boss
  2. Tell me about a time two of your reports were in conflict
  3. Tell me about a time you escalated something to your manager
  4. Tell me about a time a peer EM and you had different priorities
  5. Tell me about a time you had to defend an unpopular decision
  6. Tell me about a time you changed your mind

Cross-functional (5)

  1. Tell me about a difficult relationship with a PM
  2. Tell me about a time you pushed back on a deadline
  3. Tell me about working with a difficult senior stakeholder
  4. Tell me about a time design and engineering disagreed
  5. How do you align a team with conflicting OKRs?

Tech leadership (8)

  1. Tell me about a major technical decision you led
  2. Tell me about a technical decision you regret
  3. How do you balance new feature work and tech debt?
  4. How do you assess code review quality across your team?
  5. Tell me about an outage you handled
  6. Tell me about a migration you led
  7. How do you stay technical as a manager?
  8. Tell me about a time you overruled a senior engineer

Strategy and ambiguity (6)

  1. Tell me about a time the goal changed mid-project
  2. Tell me about an ambiguous problem you scoped
  3. Tell me about a time you killed a project
  4. How do you decide what your team should work on?
  5. Tell me about a multi-quarter bet
  6. What is a hill you would die on?

Team and culture (6)

  1. How do you build trust with a new team?
  2. Tell me about scaling a team from N to 2N
  3. How do you handle on-call burnout?
  4. How do you handle remote vs in-office tensions?
  5. Tell me about a culture change you led
  6. How do you give recognition?

Self-reflection (6)

  1. What is your biggest weakness as a manager?
  2. What management mistake do you keep making?
  3. What kind of work do you find draining?
  4. What kind of report is hardest for you to manage?
  5. How do you measure your own success?
  6. Why are you leaving your current role?

Signal traps to avoid

  • “We” syndrome. If your story is all “we,” interviewers cannot tell what you did. Use “I” liberally.
  • Vague results. “It went well” is not a result. “We hit the deadline by 2 weeks, and engagement was up 12% in Q3” is.
  • The hero narrative. Do not credit yourself for everything good. Acknowledge the team. Name names.
  • Politically loaded stories. Do not bash former bosses or companies. Stay constructive.

Frequently Asked Questions

How many stories should I prepare?

15–20 distinct stories cover ~80% of likely questions. Each story should map to multiple themes so you can repurpose it.

What if I do not have a story for a question?

Be honest. “I have not personally led X, but I have observed and supported it. Here is what I would do if it came up tomorrow.”

Is it OK to refer back to the same story twice?

Once is fine; twice in the same loop is a flag. Have enough variety to avoid repetition.

Scroll to Top