Interview Questions for an Engineering Manager

Walk me through how you run sprint planning and capacity planning for a team of six to eight engineers. How do you handle a sprint that's clearly over-committed?

What to look for: A repeatable process: breaking work down, accounting for on-call/PTO/meetings in capacity, negotiating scope with product mid-sprint, and protecting the team from thrash rather than just adding hours.

You're reviewing a design doc and disagree with the proposed architecture. How do you engage without overriding the engineer or rubber-stamping it?

What to look for: Asking questions to surface tradeoffs, naming concrete risks (scalability, coupling, operational load), letting the engineer own the call where reasonable, and knowing when to escalate to a hard 'no'.

How do you design an on-call and incident-management process for a team that didn't have one? What do you measure?

What to look for: Rotation fairness, runbooks, severity definitions, blameless postmortems, and tracking signals like MTTR, alert noise, and pages-per-shift to drive down toil.

What does your code-review and quality bar look like, and how do you keep it from becoming a bottleneck?

What to look for: Clear standards for testing/documentation, SLAs on review turnaround, automation (CI, linters), and balancing rigor against delivery speed without abandoning operational readiness.

Describe how you run a hiring loop: defining the role, calibrating interviewers, and making a close.

What to look for: A structured rubric, interviewer calibration to reduce bias, debrief discipline, and a deliberate selling/closing motion rather than passive offer-and-wait.

How do you decide whether to build, buy, or defer a piece of infrastructure under delivery pressure?

What to look for: Weighing total cost of ownership, team expertise, time-to-value, and roadmap impact rather than defaulting to either build-everything or buy-everything.

Tell me about an engineer you helped grow into a significantly more senior role. What did you actually do?

What to look for: Specific coaching: stretch assignments, feedback cadence, visibility, and a real before/after arc rather than taking credit for someone's natural trajectory.

Describe a time you had to address an underperformer. How early did you act and what was the outcome?

What to look for: Early, direct, documented feedback, a concrete improvement plan, and an honest result, including cases that ended in a managed exit handled with dignity.

Tell me about a delivery milestone you committed to with product that was at risk. How did you handle it?

What to look for: Early surfacing of the risk, options offered (scope, timeline, resourcing), and protecting trust with stakeholders instead of silently slipping.

Give an example of a process change you championed that improved engineering quality or delivery.

What to look for: A measured problem, a change driven with the team's buy-in, and evidence of impact such as fewer escaped defects, faster cycle time, or reduced incidents.

Describe a time you had to advocate for your team's needs against pushback from leadership.

What to look for: Framing the ask in business terms, bringing data, and navigating organizational complexity to win resourcing without burning relationships.

Two senior engineers on your team are in a recurring conflict over technical direction that's slowing the team. What do you do?

What to look for: Getting to the underlying disagreement, facilitating a decision (possibly a time-boxed spike or a clear decision owner), and addressing the interpersonal pattern, not just the technical question.

Your team's velocity has dropped for three sprints and morale is visibly low. How do you diagnose and respond?

What to look for: Looking past the metric to causes (unclear priorities, tech debt, burnout, dependencies), talking to people directly, and acting on root cause rather than pushing harder.

Product wants to commit to a date you believe is unrealistic. How do you handle the conversation?

What to look for: Quantifying the gap, offering scoped alternatives, and being firm but collaborative so you protect both the team and the relationship.

A production incident is ongoing and a junior engineer caused it. How do you manage the moment and the aftermath?

What to look for: Stabilizing first, shielding the individual from blame, running a blameless postmortem, and turning the failure into a systemic fix and a learning moment.

What does psychological safety mean to you in practice, and how do you build it on a new team?

What to look for: Concrete behaviors: inviting dissent, normalizing mistakes, following through on feedback, rather than a generic definition.

How do you partner with product and design when priorities conflict with engineering health or tech debt?

What to look for: A shared-ownership stance, making tradeoffs visible, and negotiating sustainable balance rather than treating it as us-versus-them.

How do you give difficult feedback to someone who reports to you?

What to look for: Direct, timely, specific, and kind feedback with examples, focused on behavior and growth, not a vague or avoidant approach.