Tell me about a time you had to manage out a low performer or have a tough performance conversation.

Lead-level interviewers want to see whether you'll have the conversations that matter or duck them. The interview is partly testing whether your discomfort threshold is calibrated for the role.

STAR walkthrough — sample answer:

Situation: I was managing a small QA team (4 engineers) at a previous company. One member of the team had been hired about 9 months before I took over — solid technical skills, but persistent issues with reliability: missing standups, late on commitments, not flagging blockers in time. The previous manager had given inconsistent feedback. The team had started routing around him — not relying on his commitments — and the dynamic was eroding morale.

Task: Address the performance issue directly. I'd been in role about 6 weeks; I needed to either lead him to improvement or, if that wasn't possible, make a different call.

Action: Five steps over about three months.

1. Honest one-on-one early. In our second one-on-one I named the pattern directly. Not "I want to discuss your performance" — but "I've noticed three things in the last few weeks: standup misses, two missed commitments, no flag when X was blocked. I want to understand what's happening and what would help." He was surprised — said he'd been told things were fine. We talked through what was going on (real personal pressure outside work that I won't detail here).

2. Concrete improvement plan, jointly written. We agreed on three specific behaviours: attend standups or send a written async update; flag blockers within 24 hours of hitting them; renegotiate commitments before the deadline if needed, not after. 30-day check-in.

3. Active support, not just monitoring. I checked in 1:1 weekly rather than fortnightly. When he hit the personal pressure issue worse, we adjusted his work scope temporarily. I made it clear this was support, not lowered expectations — the behaviours still applied, the workload was what was flexing.

4. Honest 30-day check-in. At the agreed point, he'd improved on two of the three behaviours but not the third. I named it directly. Asked what was getting in the way. We extended the plan another 30 days with a sharper focus.

5. Honest call at 60 days. The third behaviour wasn't moving and the personal situation hadn't stabilised. In one-on-one I said: "We've worked on this for 60 days; I've seen progress on two areas but not the third. I think this role isn't the right fit right now. Here are options I can support: a different role at this company, an exit with notice and reference, or one more 30-day attempt with no further extension." He chose the exit option. I honoured the notice period, gave him a fair reference for technical skills, and we ended on respectful terms.

Result: Team morale and reliability improved within a month — the dynamic of routing around him had been more corrosive than I'd realised. He landed at another company a few months later in a role that was a better fit for the personal situation he was managing. He emailed me a year later thanking me for the directness — said it had been hard to hear but better than the indefinite drift his previous manager had allowed.

What I learned: kindness and directness aren't opposites — they're partners. The kindest thing for everyone (him, the team, me) was being honest about what was working and what wasn't. The unkind thing would have been letting it drift for another year while pretending things were fine.

Why this works: shows directness with respect, genuine support before judging, honest call when improvement didn't come, and humane handling of the exit. The interviewer is testing for whether you'll do the hard thing well — this answer demonstrates both willingness and skill.