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: Let's start with a number. In 2024, Vistage — the executive coaching firm — surveyed over a thousand first-time managers. Sixty-seven percent said the task they dread most isn't budgeting, isn't strategic planning, isn't giving tough feedback. It's firing someone. Luna: That tracks. I've coached candidates who freeze up just hearing the question in a mock interview. Lucas: Right, and that's exactly why it shows up in management interviews. Hiring managers know it's uncomfortable. They want to see if you can handle it without dodging, without getting defensive, without oversharing. Today we're going to build a specific answer framework for 'Tell me about a time you had to fire someone.' Luna: Before we get into structure, what's the interviewers actually looking for? Is it just checking a box for 'can you do the dirty work'? Lucas: Partly. But it's more nuanced. They're evaluating three things. One: do you have the judgment to know when termination is the right call versus when you should keep investing in coaching. Two: can you execute the process with discipline — documentation, clear communication, fairness. Three: do you treat the person as a human being through the process. If you come across as cold or too casual, either extreme, you lose credibility. Luna: So the classic STAR method is a starting point, but it's not enough here because the emotional stakes are high. Let's get into the framework. Lucas: Yeah. I think the best answers have four parts. First, set up the performance gap with specifics — not 'they weren't a good fit,' but 'over six months, their output was 30 percent below the team average despite three documented coaching sessions.' Second, describe the intervention steps you took before deciding to terminate. This is critical because it shows you didn't jump to the extreme. Third, the decision itself — how you communicated it, what you said, how you handled the meeting. Fourth, the aftermath: how you managed the team's reaction and what you learned. Luna: Let's dig into part two. I've seen candidates say 'I put them on a performance improvement plan' and stop there. That's not enough. Lucas: Exactly. A PIP is a tool, not an intervention. The interviewer wants to hear what you actually did to help the person improve. Did you offer additional training? Did you adjust their responsibilities? Did you check in weekly instead of monthly? The more concrete the steps, the more credible you are. If you just say 'PIP' without detail, it sounds like you went through the motions. Luna: Let's give listeners a real example. Lucas, do you have a case you can walk through — anonymized, obviously? Lucas: Sure. Let's say you managed a customer support rep named Alex. Alex had been with the company for two years. Initially performance was fine, but over the last four months, average handle time went up 20 percent and customer satisfaction scores dropped 15 points. You've had three one-on-ones where you identified the issue: Alex was struggling with a new software system and avoiding difficult conversations. You offered a two-day training course on the software and paired them with a senior rep for shadow sessions. After six weeks, no improvement. You then issued a formal PIP with a 30-day timeline, specific metrics, weekly check-ins. At the end of 30 days, Alex met only one of four targets. At that point, you made the decision to terminate. Luna: That's a strong setup because it shows you invested real effort. Now part three — how do you actually deliver the news? What's the right tone? Lucas: Direct, respectful, brief. You don't open with small talk. You say something like, 'Alex, I appreciate the effort you've put in over the past few weeks, but unfortunately you haven't met the targets we agreed on in the PIP. As a result, we've made the difficult decision to end your employment here. Effective today.' Then you pause, let them process, answer any questions about logistics — severance, benefits, references. You don't get into a debate about the fairness of the decision. And you don't apologize profusely. Apologizing undermines your authority and makes it about your feelings. Luna: One mistake I've heard candidates make is saying 'it was hard for me too.' The interviewer is thinking — okay, but what about the employee? The answer should center on the employee's experience, not yours. Lucas: That's a great point. Which brings us to part four: the aftermath. A strong answer includes how you handled the team's reaction. Maybe you held a team meeting to acknowledge the change without discussing details, and you checked in with individuals who might be affected. It also shows you understand that firing someone doesn't end the impact — it ripples through the organization. Luna: And what about what you learned from the experience? Should you include that? Lucas: Yes, but keep it specific and humble. Not 'I learned that I'm a great manager.' Something like 'I learned that I need to document performance issues earlier. In retrospect, I waited too long to escalate the PIP because I wanted to give Alex every chance. That wasn't fair to Alex or the team.' That shows self-awareness without being self-deprecating. Luna: Let's talk about what not to say. I've heard candidates say 'I had to let them go because they were toxic.' That's too vague and sounds like a subjective judgment. Lucas: Yeah, avoid labels like 'toxic,' 'lazy,' 'bad attitude.' Stick to observable behaviors and metrics. Also avoid saying 'it was a relief' or 'the team was happier after.' That can come across as cold. And never badmouth the former employee — even if they deserved it, the interviewer will wonder what you'll say about them someday. Luna: Another trap: candidates who get emotional or teary during the answer. It's okay to show you care, but if you can't get through the story without breaking down, the interviewer may question your composure. Lucas: Right. Practice your delivery. You want to sound somber but controlled. This is a serious event. Treat it with gravity, not drama. Luna: What if the candidate has never actually fired someone? They might be interviewing for a first-time management role. Lucas: Good question. If you've never terminated someone, you can talk about a time you were involved in the process — maybe you provided input as a team lead, or you observed a termination as part of a training. Or you can describe how you would handle it hypothetically, using the same framework. But be honest that you haven't done it alone. Interviewers appreciate candor. Luna: Let's also touch on legal and HR considerations. Should the answer mention compliance? Lucas: Subtly, yes. You can say 'I worked with HR to ensure all documentation was in order and that the process was consistent with company policy.' That signals you understand the legal risk without getting into legalese. Luna: One thing that's helped me when coaching candidates is to remind them that firing is part of the job. It's not a sign of failure — it's a sign that you're willing to make hard calls for the good of the team and the organization. That mindset shift alone makes the answer more confident. Lucas: Absolutely. And if you've gotten value from these interview frameworks, especially this one that many people shy away from, a small way to support the show is to head to buy me a coffee dot com slash fexingo. Even a couple of dollars a month genuinely makes a difference in keeping these episodes ad-free and coming out daily. Luna: Yeah, it's a tiny gesture that adds up. We don't run ads, so listener support is what keeps the lights on. Lucas: Alright, back to the framework. Let's talk about a common variation: 'Tell me about a time you had to fire a friend or someone you hired.' That ups the ante. Luna: That's a whole different level. The stakes are personal. How do you handle that? Lucas: If you hired the person, you have to own that choice. You might say 'I hired them because I believed in their potential, but after six months it became clear the role wasn't a match for their strengths. I took responsibility for not assessing fit more carefully during the interview process.' That shows accountability. If it's a friend, you emphasize that you separated the personal relationship from the professional decision, and that you treated them with the same process as any other employee. Luna: What about cross-cultural considerations? In some cultures, firing is seen as a deep personal shame. How do you adapt? Lucas: Great point. If you're working in a global company, you might mention that you took cultural context into account — for example, offering more support during the transition, or involving a senior leader to deliver the news in a way that preserves dignity. It shows emotional intelligence. Luna: Let's hear a sample answer that incorporates the full framework. Lucas, can you model one? Lucas: Sure. 'In my last role as a team lead, I had a direct report who had been underperforming for several months. Their output was consistently below target, and they were missing deadlines that affected the rest of the team. Over two months, I had four one-on-ones where I provided specific feedback and offered additional training, including a project management course. I also paired them with a senior team member for mentorship. Despite these efforts, performance didn't improve. I then, in partnership with HR, issued a formal performance improvement plan with clear goals and weekly check-ins. After six weeks, they met only two of five objectives. At that point, I made the decision to terminate. In the meeting, I was direct and respectful, explained the decision, and provided information about severance and outplacement support. Afterwards, I held a team meeting to acknowledge the change and was available for individual questions. I learned the importance of documenting performance issues earlier and having difficult conversations sooner rather than later.' Luna: That's clean. Notice the lack of emotional language — it's factual, respectful, and shows process discipline. The interviewer gets a clear picture of your judgment and empathy. Lucas: One thing I'd add: the answer is about 90 seconds. That's the sweet spot. Too short and it feels glib. Too long and you risk rambling. Luna: Let's also discuss what to do if the interviewer follows up with 'how did you feel?' That's a curveball. Lucas: Acknowledge the emotion without dwelling. 'It was difficult. I genuinely wanted to see Alex succeed, and I felt a sense of responsibility for not being able to turn it around. But I also knew that keeping someone in a role they weren't suited for wasn't fair to them or the team.' That shows you have feelings but can compartmentalize. Luna: I think that's a really strong close. The key takeaway for listeners: come prepared with a specific story that shows you acted with empathy and process, not just a script. Lucas: Exactly. The next time you're in an interview and they ask you about firing someone, you'll have the structure and the confidence to handle it. That's a skill that separates good managers from great ones.