To answer “tell me about a time you dealt with an underperforming team member,” show that you noticed the gap early, talked to the person privately, found the cause before choosing a fix, agreed clear expectations and support, followed up on a schedule, and reached an outcome: improvement, or a fair and documented next step. Interviewers are testing whether you can hold people to a standard and treat them with respect at the same time. Keep the person anonymous and the focus on what you did.
What the interviewer is testing
The question appears in almost every manager, supervisor and team-lead interview, and in a peer version for experienced individual contributors. Panels listen for:
- Timing. Did you act within weeks, or let it drift for a year?
- Fairness. Did you look for causes such as unclear expectations, missing training or tools before blaming the person?
- Directness. Did you have the conversation yourself, privately and specifically?
- Follow-through. Was there a plan with dates, and did you check it?
- Judgment at the end. If it didn't improve, did you escalate properly, with HR and documentation?
The NSW Public Sector Capability Framework (Version 3, 2026) files this under “Manage and develop people,” defined as engaging with and motivating staff and developing their capability and potential, and Amazon's “Hire and Develop the Best” principle says leaders take seriously their role in coaching others (both checked November 2026). Neither treats tolerating poor performance as kindness.
| Your role | What the question means | What a good answer shows |
|---|---|---|
| Manager or supervisor | How you manage performance | A private conversation, a plan with measures, check-ins and an outcome, with HR if needed |
| Team lead without authority | How you influence a peer's work | Direct, kind feedback first; involving the manager only after that, and telling the person you are doing so |
| Peer or student | How you handle a teammate who isn't pulling their weight | Asking before assuming, re-dividing work fairly and protecting the shared deadline |
Find the cause before you choose the fix
Most underperformance has a cause you can name. Saying which one you found, and how, is the most persuasive part of the answer.
| Likely cause | Typical signs | What usually helps |
|---|---|---|
| Unclear expectations | Good effort, wrong output; surprise when told | Write down what good looks like, with an example |
| Skill or knowledge gap | Errors in one kind of task; slow on new tools or rules | Training, pairing, a checklist |
| Missing tools or information | Delays waiting on others; workarounds | Fix the access, data or handoff |
| Workload or role fit | Quality drops as volume rises; strong in other areas | Rebalance the work; discuss a better-suited role |
| Personal circumstances | A sudden change in someone who was strong | Listen, point to support, agree temporary adjustments |
If the cause was mainly personal, the struggling-team-member answer covers that conversation in depth. If your story is mostly about delivering the message, see tell me about a time you gave difficult feedback.
Choosing the story, and protecting the person
- Pick a case where your action changed the course, not one where the problem fixed itself.
- Never name the person or share health, family or disciplinary details. “A team member” and “for personal reasons” are enough.
- Avoid stories where the real problem was your own unclear direction, unless you say so and show what you changed.
- Avoid stories that end with you quietly doing their work for months; that is avoidance, not management.
- If the person left, say how the exit was handled respectfully and what you learned about hiring or onboarding.
A six-step structure, with timings
| Step | What to say | Time |
|---|---|---|
| Notice | The gap, with evidence: numbers, missed dates, customer impact | 15 seconds |
| Talk | The private conversation and the question you asked first | 15 seconds |
| Diagnose | The cause you found | 15 seconds |
| Agree | Clear expectations, support and a timeline | 20 seconds |
| Review | Check-ins and what you saw | 15 seconds |
| Outcome | Improvement or the fair next step, plus your lesson | 20 seconds |
It is the STAR method with the Action split into talk, diagnose, agree and review, because those are the parts interviewers probe. About 100 seconds in total.
Sample answers: peer, team leader, foreman, senior accountant, sales manager
We wrote these to show the shape in different jobs; they are not real candidates' stories. Use your own situation, your own numbers and your own words.
Entry-level peer: closing duties at a restaurant
“I was a server at a busy brunch restaurant, and closing side work, restocking stations and rolling cutlery, was shared between the last three servers. One colleague, who had transferred from our sister restaurant, kept leaving his share, and the opening shift complained to our manager. Instead of going to the manager, I asked him at the end of a shift whether he'd seen our closing checklist. He hadn't: his old restaurant had a porter for that work, and nobody had walked him through ours. I showed him the list, we split it by station, and I suggested to our manager that the checklist be posted by the service area. The complaints stopped within a week, and the manager added the checklist to training for transfers. I learned to ask what someone knows before deciding they don't care.”
Customer-facing: a contact-centre agent rushing calls
“As a team leader in an insurance contact centre, I had an agent whose quality scores fell from among the best on the team to the bottom quarter in two months, and two customers complained he'd rushed them. I listened to five of his calls and then met him privately. I played one strong call and one weak one and asked what he noticed. He said he was chasing the six-minute average handle time on our wall board, which he thought was a personal target. It was a team guide, and nobody had told him. We agreed that quality came first, set two goals for six weeks, quality back above team average and no rushed-call complaints, and met for fifteen minutes every Friday to review two calls together. By week five he was back in the top half, and I changed how we explained the wall board to new agents.”
Trades: failed inspections on an electrical crew
“I was a foreman for a commercial electrical contractor, and one of our journeymen had three jobs fail inspection in a month, which meant return visits and an unhappy general contractor. He had been reliable for years, so I didn't start with a warning. I went through the three inspection reports with him in the site office. All three failures involved requirements that had changed in the latest code update, and he had missed the company's update training. We agreed he would take the code-update course the following week on paid time, and for a month I did a short walk-through of his jobs before inspection, with him explaining what he had done. He passed every inspection after that, and we started tracking who had completed update training instead of assuming everyone had.”
Office: late reconciliations in an accounting team
“As a senior accountant, I reviewed the work of two staff accountants. One was consistently three or four days late with bank reconciliations, which held up the whole month-end close, yet her accuracy was excellent, so effort wasn't the problem. I asked her to walk me through one reconciliation on screen. She was rebuilding each one by hand from statements, because a system export had once given her wrong totals and she no longer trusted it. I showed her how to run the export with the right date filter, and we agreed she would run both methods side by side for a month to see that they matched. I also put a due date for each reconciliation on our close calendar and checked progress with her mid-week. By the second close she was on time, and she later wrote the export instructions the whole team now uses.”
Manager: a formal plan that ended in an exit
“As a regional sales manager, I had a rep who missed his target for three straight quarters while the rest of the team was close to plan. Informal feedback hadn't changed much, so I told him plainly that we needed a formal plan, and I involved HR so the process would be fair and documented. Together we went through his pipeline and found he was spending most of his time on large accounts that rarely closed. The plan set three measurable goals for 60 days, focused on mid-sized accounts, with weekly one-to-ones and a joint customer visit every other week. His activity improved but his closed sales didn't, and at the end of the plan, with HR, we ended his employment respectfully and with the notice and support our policy provided. My lesson was to set clear goals in a new rep's first 90 days, so a problem surfaces in one quarter, not three.”
What the panel will ask next
- “What did you try before a formal process?” The informal conversation, the support you offered and the timeline you agreed.
- “How did the rest of the team react?” Say you kept the details private and rebalanced work openly where needed.
- “What if they disagreed with your assessment?” Show the evidence, listen, adjust if they had a point, and ask your manager or HR for a second view.
- “How do you tell a skill problem from a motivation problem?” Ask, observe, then add support: if training fixes it, it was skill.
- “Would you act sooner next time?” Almost everyone should say yes, and say when.
These come up across the manager interview question bank. If you coached someone who was doing fine but wanted to grow, keep that story for the mentoring question instead.
Mistakes to avoid, and how to practice
- Speaking badly about the person. The panel imagines you describing them one day.
- Sharing private details: health, family or what was said in HR meetings.
- Skipping the diagnosis and jumping straight to a warning.
- A happy ending with no evidence. Say what the numbers or behavior looked like afterwards.
- Doing their work yourself for months and calling it support.
Write the six steps in one line each and say the answer aloud; it should take under two minutes. Prepare the follow-ups above too, because that is where this answer usually turns vague. An AI mock interview reads questions aloud and scores each spoken answer out of 10, and the free practice demo adds a follow-up question to a typed answer.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant, and for people-management questions it is most useful before the interview. The free AI mock interview takes your résumé and the job description, builds questions from both, reads them aloud and scores each spoken answer out of 10. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month, and it runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta.
If you use live help in a real interview, follow your employer's rules first. AI can help you structure and tighten a story, but it must not invent one: every event, number and name in your answer has to be true and yours. That matters even more when the story is about another person.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
How do you answer “tell me about a time you dealt with an underperforming employee”?
Notice the gap with evidence, talk privately, find the cause, agree expectations and support with a timeline, review on schedule, and describe the outcome and your lesson.
What if I've never managed anyone?
Use the peer version: a teammate on a project or shift who wasn't pulling their weight. Ask before assuming, re-divide work fairly, and involve the lead only if needed, telling the person you're doing so.
Can I use a story where the person was let go?
Yes, if you show you tried to help first, followed a fair and documented process with HR, and treated the person with respect. Leave out private details.
Should I mention a performance improvement plan?
If you used one, yes, briefly: what it measured, how long it ran and how you supported the person. Panels want to see that the plan was a real chance, not paperwork.
How long should the answer be?
About 90 seconds to two minutes when spoken.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview