Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Had to Fire Someone
Transcript
- Lucas: If you're interviewing for a management role, there's one question that can make even seasoned candidates freeze: 'Tell me about a time you had to fire someone.' Luna: And it's not because people haven't done it — it's because they don't know how to frame it in a way that sounds both humane and decisive. Lucas: Exactly. So today we're going to walk through a real example from a client I worked with earlier this year. Let's call her Priya. She was a VP of Sales at a mid-market SaaS company, about 150 employees. She was interviewing for a Chief Revenue Officer role at a competitor. Luna: And the interviewer asked her this exact question, right? Lucas: Yes. And Priya's instinct was to give a very clinical answer — she started talking about performance metrics, PIPs, severance calculations. But the interviewer stopped her and said, 'I don't care about the process. I want to hear how you felt.' Luna: That's the key. Hiring managers aren't checking if you know the termination protocol. They're assessing your emotional intelligence and your ability to make hard calls without being cold. Lucas: Right. So let's break down what makes a great answer. First, the context. Priya had to fire a top-performing sales rep — we'll call him Raj. Raj was hitting 150% of quota every quarter. But he was toxic. He undermined junior colleagues, took credit for team deals, and two people had quit because of him. Luna: That's the hardest kind of termination — when the person is generating revenue but damaging culture. A lot of managers hesitate because they don't want to lose the numbers. Lucas: Exactly. And Priya hesitated for about four months. She documented everything, put him on a performance improvement plan — but the PIP was about behavior, not sales. She framed it as 'leadership expectations.' The behavior didn't change. So she made the call. Luna: What did she say in the termination meeting? Lucas: She told me she started with acknowledgment. She said, 'Raj, I want to start by recognizing your contributions. You've delivered exceptional results for this company. But the way you work with others is damaging the team, and we've talked about this multiple times. I've decided to terminate your employment effective today.' She didn't waver, didn't apologize, but she was human. Luna: I like that she didn't say 'it's not personal' or 'it's just business.' Those phrases minimize the impact and can sound dismissive. Lucas: Exactly. The interviewer wants to see that you can hold two things at once: respect for the person and accountability to the organization. In Priya's interview, she said something like, 'It was the hardest conversation I've had professionally. I lost sleep over it. But I knew that letting one person's behavior erode the culture would cost us more in the long run.' Luna: And that's the story the interviewer remembers. It's not about the PIP steps — it's about the judgment call. What's the biggest mistake people make when answering this question? Lucas: Two things. First, being too vague. Some candidates say, 'I had to let someone go because they weren't a good fit' — that's not specific enough. You need to show you understand the real reasons. Second, being too defensive. They'll say, 'It was a company decision, not mine,' which makes you look like you can't own hard choices. Luna: So the STAR method works here, but you have to emphasize the 'R' — the result. What happened after? In Priya's case, the team's morale improved, and within a quarter, they actually exceeded their previous revenue run rate because collaboration improved. Lucas: Exactly. She could say, 'After Raj left, the team started sharing leads more openly. Our close rate went up by 12 percent because people trusted each other again.' That's the positive outcome that justifies the hard decision. Luna: And that's a concrete number. Interviewers love specific results. So let's talk about what not to say. Can you name the one phrase that instantly disqualifies a candidate? Lucas: I'd say the worst is any variation of 'I enjoyed it' or 'I didn't lose any sleep.' If you come across as someone who relishes firing people, you're showing a dangerous lack of empathy. Luna: Right. Another one is blaming the employee entirely. Like, 'He was lazy and incompetent.' That may be true, but you sound petty. Instead, focus on the misalignment between the role and the person's strengths or behavior. Lucas: Exactly. Frame it as a responsibility to the team, not a judgment of the individual. And if you've never actually fired someone — if you're early in your career — don't lie. But you can talk about a time you were part of a layoff decision, or you had to deliver difficult feedback that led to someone leaving voluntarily. Luna: That's a good point. Hiring managers can usually tell if you're fabricating. Better to say, 'I haven't had to terminate someone directly, but I've been involved in performance improvement discussions that resulted in a resignation.' That's still a relevant experience. Lucas: Absolutely. And let's be honest, these conversations are never easy. Which is exactly why they show up in interviews for leadership roles. Luna: Speaking of things that are never easy but worth doing — a quick aside. You know, we keep this show ad-free, and that's only possible because listeners like you occasionally chip in. Lucas: Yeah, it's a small thing that makes a big difference. If you've ever gotten a job or a promotion and thought, 'Hey, that interview prep episode helped,' a few dollars at buy me a coffee dot com slash fexingo keeps the lights on. Luna: No pressure, just genuine gratitude. And we're back to termination stories. Lucas: So let's talk about how to practice this answer. Priya rehearsed her story out loud about six times before the interview. She timed it — it was about two minutes. That's the sweet spot. Too short and it sounds like you're hiding something; too long and you lose the interviewer. Luna: And she used the STAR format? Situation, Task, Action, Result? Lucas: Yes, but loosely. She described the situation: 'I inherited a team where a top performer was causing cultural damage.' The task: 'I needed to either change his behavior or remove him to protect the team.' The action: 'I documented issues, set clear expectations, gave him a chance to improve, and when he didn't, I terminated.' The result: 'Sales actually increased because the team started collaborating.' Luna: Clean and compelling. One thing I'd add is to be ready for follow-up questions. Interviewers might ask, 'How did the team react?' or 'Did you have any regrets?' Lucas: Great point. Priya was asked, 'Did you consider reassigning him to an individual contributor role?' And she said, 'Yes, I did. But the behavior issues would have followed him, and it would have been unfair to a new team.' That showed she had thought through alternatives. Luna: That's a strong answer. It shows you didn't jump to termination as a first option. So the takeaway: be specific, be human, and own the decision. Lucas: And one final tip: don't use the word 'fired' if you can avoid it. Say 'terminated' or 'let go' — it's more professional. But in the context of the question, you're allowed to say 'fire' because that's what they asked. Luna: Right. And remember, the interviewer is also evaluating whether you'd be able to handle that conversation at their company. So your answer is a preview of your leadership style. Lucas: Exactly. If you sound like you'd avoid the hard conversation or handle it brutally, they'll pass. But if you show you can be both empathetic and decisive, you're likely to move forward. Luna: Great advice. Next time, we'll tackle a question that's even trickier: 'Tell me about a time you had to fire a friend.' Lucas: Oh, that's a good one. And it happens more often than you'd think. Till then, practice your story — and if you want to support the show, you know where to find us.