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 Deliver Bad News Question
Transcript
- Lucas: Today we're talking about what might be the most uncomfortable interview question that's still fair game: 'Tell me about a time you had to deliver bad news.' Luna: That one makes people squirm. Because it's not just about the bad news — it's about how you handled the discomfort. Lucas: Exactly. And hiring managers use it to test three things at once: your communication skills, your emotional intelligence, and your willingness to own a hard situation rather than punt it to someone else. Luna: Before we go deep — we keep this show ad-free because we think career advice should be accessible, not walled off. If that matters to you, you can support us at buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small thing that keeps us independent. And listeners like you are the reason we've been able to do over forty episodes on this stuff without a sponsor breathing down our necks. Luna: Right. So back to bad news — let's talk about why this question gets asked. Lucas: The surface layer is obvious: can you deliver bad news without panicking, without sugarcoating, and without throwing anyone under the bus. But the deeper layer is about judgment. Luna: How do you mean? Lucas: The interviewer wants to know: did you escalate at the right time? Did you own the delivery yourself or delegate it to your boss? Did you propose a fix or just dump the problem? That's what separates a good answer from a great one. Luna: So it's really a test of ownership. Let's anchor this with a concrete example. Lucas: Let's say you're a product manager at a SaaS company. Your team has been building a flagship feature for six months. Two weeks before launch, your lead engineer discovers a critical security vulnerability that requires a complete rework of the authentication layer. Luna: Oof. And you have to tell the VP of Product that the launch is delayed by six weeks. Lucas: Right. How you handle that conversation is exactly what they're asking about. A weak answer would be: 'I told my boss there was a delay.' A strong answer shows you took ownership of the communication, the analysis, and the path forward. Luna: So what's the structure of a strong answer? Lucas: I like a four-part framework. First, set the context briefly. Second, explain your decision-making — did you verify the information, talk to the engineer, explore alternatives? Third, describe how you actually delivered the news. And fourth, the outcome — what happened after. Luna: Let's hear one for the product manager example. Lucas: Context: 'We were two weeks from launching a major feature when our lead engineer found that the authentication system had a vulnerability that could expose user data. The fix would take six weeks.' Decision: 'I spent the afternoon with the engineer understanding the scope. We considered a partial rollout with a temporary patch, but that would have left us exposed. So I decided to delay the full launch.' Luna: That's a good detail — showing you explored alternatives before jumping to the bad news. Lucas: Exactly. Then delivery: 'I scheduled a one-on-one with my VP. I started with the impact: this is a security issue, not a schedule issue. Then I gave the timeline: six weeks. And I brought a plan — the engineering team would work with a security consultant to prevent future issues.' Outcome: 'The VP appreciated the early warning. We launched six weeks late, but with zero security incidents. That experience also led us to add security reviews earlier in our development process.' Luna: I like that the outcome includes a lesson learned. That shows growth. Lucas: It's crucial. The interviewer doesn't just want to hear that you handled one bad situation. They want to know that you'll handle the next one better because of it. Luna: What about when the bad news isn't about a project but about people? Like telling a team member they're being let go, or informing a client you're losing a deal? Lucas: That's an even tougher variant. For people-related bad news, the emotional intelligence piece becomes primary. A former colleague of mine had to tell her retail team that the store was closing. She didn't just send an email — she called a meeting, explained the business reasons, acknowledged the impact on their lives, and spent the next week helping each person update their resume and connect with other stores in the company. Luna: That's a powerful example. It shows empathy without being fake. Lucas: And it shows that she took responsibility for the delivery even though the decision wasn't hers. That's the ownership signal hiring managers are looking for. Luna: I want to push back a little. Some people might be tempted to say, 'I told my boss about the problem and they handled it.' Is that ever okay? Lucas: It depends. If you genuinely lacked the authority to deliver the news — say, it's a company-wide restructuring that only the CEO can announce — then saying 'I escalated it to the right person' can be fine. But you'd better frame it as a judgment call: 'I knew this was above my pay grade, so I prepared the briefing for my boss and stayed on to support the team during the announcement.' Luna: So it's not about never delegating. It's about showing you thought about whether you should. Lucas: Exactly. The worst thing you can do is blame others. If your answer includes 'my engineer didn't tell me sooner' or 'marketing dropped the ball,' you've failed the test. Owning bad news means owning the whole situation, even if it's not your fault. Luna: Let's talk about the client-facing version. If you're in consulting or sales and you have to tell a client a project is delayed or a deal fell through. Lucas: That's a classic scenario. The framework still works, but you add a layer: you're representing your company. So your answer should show that you protected the relationship. For example: 'I called the client immediately. I didn't wait for our weekly check-in. I explained what happened and what we were doing to fix it. Then I offered a discount on the next phase as a goodwill gesture.' Luna: The immediacy part is key. Bad news does not age well. Lucas: It really doesn't. If you wait, the client feels like you were hiding it. And that erodes trust faster than the bad news itself. Luna: One more thing — how do you handle the follow-up? The interviewer might ask, 'And how did the person react?' Lucas: Be honest. If they got angry, say they got angry. If they were disappointed, say that. But then describe how you managed that emotion. 'My VP was frustrated, and I acknowledged that. I said I shared the frustration. Then I redirected to the solution.' Luna: That's a good reminder — you don't have to pretend everything went smoothly. Lucas: In fact, if it went too smoothly, the interviewer might think you're glossing over it. Real bad news almost always has an emotional reaction. Acknowledging that makes your answer more credible. Luna: So the takeaway for this episode: when you get the 'tell me about a time you had to deliver bad news' question, use the four-part structure — context, decision, delivery, outcome. Show ownership, show empathy, and show what you learned. Lucas: And practice it out loud. Because if you're not comfortable saying the words, you won't be comfortable in the interview. Run through it a few times until it sounds natural, not scripted. Luna: Thanks for listening. We'll be back next episode with another tough interview question. Lucas: Take care, and good luck with your interviews.