Interview Loops & Rounds

How do you handle performance issues or challenges with team members?

By Interview Clozo · Published 27 October 2026 · Last verified 26 October 2026 · 10 min read

How do you handle performance issues or challenges with team members? You talk to the person early and privately, name the specific behavior and its impact, agree a fix with a date, and follow up. You escalate to a formal process only if that fails. The sentence that separates a mid-level answer from a Staff one is the last one: the measure you agreed and its date.

In this article

Before you start
Why interviewers ask this
Handling a team member's performance issue from first principles
The Staff-level answer
The rubric
Three variants of this question
Common mistakes
Follow-up questions
Sources

Before you start

This page answers one behavioral question. It sits inside the wider interview process and rounds path.

Why interviewers ask this

A wrong answer here is costly, because it shows how you treat people when something has already gone wrong. A candidate who avoids the topic, blames the person or jumps to formal action shows a gap that technical rounds do not test. If you are preparing for a management loop, the Meta engineering manager interview page describes how one such loop is structured.

A weak answer says "I told them to improve" or "I escalated to human resources (HR)". A strong answer gives a real example, says what you observed, shows you listened to the cause, and ends with a result. A Staff-level answer also names the measure you agreed on, what you did when the first plan did not work, and what you changed in your own habits. You do not need to be a manager to answer: a tech lead, a mentor or a peer who owned a shared deliverable can use the same structure.

Handling a team member's performance issue from first principles

SBI feedback: SBI feedback is a way of giving feedback that describes one Situation, the specific Behavior you saw there, and the Impact it had, so the other person hears an observation instead of a judgment about their character.

In plain words

Think of a doctor with a patient. She does not say "you are unhealthy". She names a measurement and explains what it affects. She asks about daily life and agrees a plan with a check-up date. Handling a performance issue follows the same order: facts first, cause second, plan third, review fourth. The analogy breaks in one place. A doctor can prescribe, while you may be a peer, so your plan has to be agreed rather than ordered.

In one precise sentence, handling a performance issue means closing the gap between the work you need and the work you see. You do it through a private talk about specific behavior, a measurable agreement and a scheduled follow-up.

Step 1: Check the facts and your role

Check the facts and your role before you speak. Write down two or three specific examples with dates, so that you talk about work, not a general feeling. Then ask whose issue it is. A direct report is a person who reports to you in the organization, so you own the conversation. A peer is not yours to manage, so you raise the issue directly with them first and involve a lead only if the shared work is at risk.

Also test your own assumptions. The cause may be unclear goals, missing skills, too much work, a personal difficulty or a lack of motivation, and each needs a different response. Input: your observations. Output: a short, factual list and a guess about the cause that you are ready to be wrong about. You now know what you will say and what you will ask.

Step 2: Talk privately using situation, behavior, impact

Describe the situation, the behavior and the impact in private, soon after the event. Situation-Behavior-Impact (SBI) feedback was developed by the Center for Creative Leadership, and its value is that each part is checkable. A sentence might read: "In last week's design review (situation), the document arrived the morning of the meeting (behavior), so nobody could read it and we postponed the decision (impact)."

After that, stop talking and ask: "How did that look from your side?" The answer often reveals the real cause, such as a blocked dependency or an unclear priority. Input: your specific example. Output: a shared description of the problem and a first view of its cause. Avoid words about personality, such as "careless" or "lazy"; they invite defense, and they cannot be checked. You now have agreement on what happened, which the next step turns into a plan.

Step 3: Agree a measurable fix with a date

Agree a measurable fix with a date, because without one both sides will remember the improvement differently. Pick one or two changes, say what "better" looks like, add a date, and note what support you will give: a pairing session, a clearer priority, a lighter load. Write the plan down afterwards.

Here is an illustrative example. A team member returns code reviews slowly, and you agree a target: the share of reviews returned within two days. In illustrative weekly data the share is 30% at baseline, 40% at day 30, 70% at day 60 and 90% at day 90.¹ These numbers are made up to show the method and are not industry norms. The point is that a measure lets you say "this is working" or "this is not" with evidence, and it lets the person see their own progress.

A measure agreed up front lets both sides see the improvement, here an illustrative rise from 30 to 90 percent.CC BY 4.0 — source: How do you handle performance issues or challenges with team members?

Text description of the diagram

In the illustrative data the share of reviews returned within two days rises from 30 percent at baseline to 90 percent at day 90.
A measure agreed up front lets both sides see the improvement.

In the illustrative data the share of reviews returned within two days rises from 30 percent at baseline to 90 percent at day 90. A measure agreed up front lets both sides see the improvement.

Step 4: Follow up, support and escalate only if needed

Follow up on the date and escalate only if the plan fails. Hold a short check-in on the agreed date and compare the measure with the target. If it improved, say so clearly and keep a lighter rhythm. If it did not, ask what is blocking progress and adjust the plan or the support once before going further.

If the issue continues after a fair attempt, tell the person what comes next, then involve your manager and HR, with your written record of examples, the plan and the check-ins. A formal performance improvement plan is the last step, not the first. Input: the measure and the dates. Output: either a recovered team member or a documented case, and in both outcomes the person was never surprised.

The conversation moves from facts to a private talk, a measurable dated fix, and a follow-up before any escalation.CC BY 4.0 — source: How do you handle performance issues or challenges with team members?

Step-by-step description

Gather examples and check your role.
Describe situation, behavior, impact.
One measure and a date.
Review, then escalate only if needed.

Check the facts and your role before you speak.
Describe the situation, the behavior and the impact in private.
Agree a measurable fix with a date.
Follow up on the date and escalate only if the plan fails.

The same story told two ways

A weak and a strong answer to this question differ in five places, and this illustrative pair shows them. Weak: "A teammate kept missing deadlines, so I told them to work harder, and when nothing changed I went to HR." Strong: "A teammate's deliverables slipped three sprints in a row. I met them privately, described two specific misses and what they delayed, and asked what was in the way.

It was an unclear priority between two projects. We agreed one owner for the priority, a weekly check on the slipped item, and a review date. It recovered, and I now confirm priorities in writing at the start of a sprint." The strong version has facts, a listening step, a measure, an outcome and a lesson.

Knowing it is half the job. Saying it is the other half.

Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.