How Do I Answer "Tell Me About a Time You Managed an Underperformer" as an Engineering Manager Candidate?
TL;DR: Use STAR, but weight it toward process: how you identified the gap early, the specific conversation you had, the written improvement plan you set, and the actual outcome — including if it didn't work out. Interviewers are listening for a structured, humane process, not a happy ending every time.
By Pinal Dave · Last updated: 2026-07-31
The short answer
This is one of the most commonly asked engineering-manager behavioral questions because it reveals more than almost any other single prompt: how early you catch problems, whether you document and communicate directly instead of avoiding conflict, and whether you can describe a real outcome without either throwing the person under the bus or claiming everything worked out perfectly. Interviewers explicitly distrust answers where every story ends in "and they turned it around and everyone was happy" — real management includes performance plans that don't work and people who eventually leave.
What the evidence says
Hiring practitioners who run EM loops describe the best answers as ones that show a "structured process": early identification of the issue (often within weeks, not months), a direct one-on-one conversation naming the specific gap, a written improvement plan with concrete, measurable targets and a timeline, and a clear final outcome — whether that's improvement, a role change, or an exit. The common failure mode is vague answers ("I sat down with them and things got better") that give the interviewer nothing to actually evaluate.
Weak vs. strong answer structure
| Element | Weak answer | Strong answer |
|---|---|---|
| Identification | "I noticed things weren't going well" | "Missed two sprint commitments in a row and code review turnaround tripled" |
| Conversation | "We talked about it" | "I named the specific gap directly in a 1:1, not over Slack, within the same week" |
| Plan | "I gave them more support" | "We wrote a 30-day plan with two measurable targets and a check-in cadence" |
| Outcome | "It worked out" | States the real outcome, including if it required a role change or the person left |
| Reflection | None | "Looking back, I'd have started the written plan two weeks earlier" |
Step-by-step: building your answer
- Pick a real, specific person and situation — not a composite or hypothetical. Interviewers ask follow-up questions and vague stories fall apart under probing.
- State the signal that told you something was off, with a number or concrete detail if possible (missed deadlines, review feedback, peer complaints).
- Describe the direct conversation. Name that you had it privately, in person or on video, and named the specific behavior — not a personality trait.
- Describe the written plan. Interviewers want to hear "we wrote down" — informal verbal check-ins read as less rigorous.
- State the real outcome, even if imperfect. A story that ends "they ultimately weren't a fit and we parted ways professionally" told with self-awareness scores well.
- Add one honest reflection. What you'd do differently signals growth, which matters as much as the outcome itself.
InterviewBoost.ai's AI mock interviews include a dedicated engineering-leadership track that scores your STAR structure, specificity, and whether you named a real measurable outcome — the exact gaps interviewers say separate strong EM candidates from weak ones.
FAQ
What if I've never had to manage someone out of a role? Use the closest real situation — a skill gap you helped close, or a case where you flagged an issue to your own manager because you didn't yet have the authority to act alone. Be honest about your level of involvement.
Should I name the person or use initials? Never use a real name. Describe the role and situation specifically enough to sound real without identifying anyone.
Is it okay if the story doesn't have a happy ending? Yes — often preferred. A well-handled exit is a stronger answer than a vague "it worked out" story interviewers can't verify.
How long should this answer take? 90 seconds to 2 minutes for the initial answer, leaving room for 1-2 follow-up questions, which almost always come.
Do I need different versions of this story for different companies? The core story stays the same; adjust only which details you emphasize based on whether the company culture leans more process-driven or more autonomy-driven.