behavioral Hard Software Engineer

Tell me about a time you had to address a teammate's persistent underperformance.

Break down this behavioral question with a model STAR answer, the pitfalls that cost candidates points, and the follow-up questions worth rehearsing next.

A strong STAR example answer

On my previous team, one engineer's work had become a liability. His pull requests were bouncing through round after round of review, he had broken the staging build repeatedly, and the rest of the team was quietly absorbing the spillover — our sprint completion had fallen by roughly a quarter. As the tech lead, addressing it was my job, and I had been avoiding it because he was well liked.

Before saying anything to him, I checked my own contribution. Reviewing his tickets, I found he was consistently assigned the most ambiguous work, which partly explained the failures. That was a resourcing mistake I had made.

Then came the direct, private conversation. I laid out what I was seeing, asked for his view, and listened. He admitted he was struggling with our new infrastructure stack and too embarrassed to ask for help.

We built a two-track plan. I rebalanced assignments so he owned a well-defined service area, paired him with our strongest infrastructure engineer for regular working sessions, and set a thirty-day check-in with clear quality bars. I also told the team I was handling it — no details — to stop the quiet resentment from spreading.

He recovered within about a month and a half. Review cycles shortened, sprint completion climbed back to where it had been, and he later became our on-call specialist. What told me more than any metric: his one-on-ones went from the most guarded on the team to the most candid.

How to structure your own answer

  • Situation: Quantify the underperformance and its cost to the team.
  • Task: Explain why addressing it was your responsibility.
  • Action: Show how you checked your own contribution first, then had the direct conversation.
  • Result: Give the measurable recovery and what it taught you about performance issues.

Common mistakes to avoid

  • Candidates often go straight to a manager or HR without ever speaking to the teammate directly.
  • Vague complaints crumble under questioning — bring concrete, observable evidence of the problem.
  • Check whether your own processes contributed before laying the failure at one person's feet.
  • A story that ends at the conversation has no follow-through; show the plan and the measurable recovery.

Follow-up questions to prepare for

Expect the interviewer to dig past your first answer. Common follow-ups for this question include:

  • What was your plan if the thirty-day check-in showed no improvement?
  • How do you protect team morale while keeping the individual conversation confidential?
  • Have you ever been the underperformer in a story like this?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator