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
Transcript
- Lucas: So Luna, let me ask you something that's probably hit most of us at some point in our careers. You know the project is going to be late. You've got to tell the client. How do you do it in a way that doesn't make you look like you're making excuses, but also isn't just dropping a bombshell and running? Luna: Oh, that's a great one. And honestly, that's the exact scenario that interviewers love to probe with the question, 'Tell me about a time you had to deliver bad news.' It's a classic behavioral question but it's often overlooked. Lucas: Right, and it's a tricky one because it tests so many things at once. Can you communicate clearly? Can you handle pressure? Do you show empathy? And crucially, can you take responsibility without throwing anyone under the bus? Luna: Exactly. It's like a stress test for your maturity and professionalism. So today, let's dig into how to craft a killer answer to this question. What's the first thing someone should do when they get this in an interview? Lucas: First, understand what the interviewer is really asking. They want to see if you can handle a situation where there's no good outcome. They're looking for your ability to be transparent, to manage expectations, and to offer solutions. It's not about whether you delivered bad news, but how you did it. Luna: So it's more about the process than the negative outcome itself? Lucas: Absolutely. And that's why the STAR method works well here, but with a twist. The action part is where you really shine. You need to show that you didn't just inform someone of bad news; you also took steps to mitigate the damage. Luna: Can you give us an example? I find that a concrete story helps listeners visualize it. Lucas: Sure. Let's say you're a project manager at a software company. Your team is building a feature for a client, and you realize you're going to miss the deadline by two weeks. A bad answer would be, 'I told the client the project was delayed.' That's it. No context, no plan, no empathy. Luna: And a good answer? Lucas: A good answer would be something like this. Situation: the client is expecting a launch in six weeks. Task: I needed to communicate that we'd need an extra two weeks. Action: I scheduled a meeting with the client, prepared a detailed explanation of the technical roadblocks, and presented a revised timeline with milestones. I also proactively offered to bring in a contract developer at our cost to speed things up. Result: the client appreciated the transparency and the solution. We extended the timeline, but maintained the relationship. Luna: Wow, that's a great example because it shows you didn't just deliver the news, you offered a solution and took ownership. The offer to bring in a contractor at your cost is a powerful touch. Lucas: Exactly. That's the key. You're not just saying, 'Sorry, we're late.' You're saying, 'Here's why, here's what we're doing about it, and here's how I'm going to make it right.' That's what interviewers want to hear. Luna: What about a situation where the bad news is something you can't fix? Like a layoff or a budget cut? Lucas: Good point. In that case, the action part is about empathy and clarity. You might say, 'I had to tell a team member they weren't getting a promotion they expected. I focused on listening to their reaction, acknowledging their disappointment, and then discussing specific steps they could take to get there in the future.' Luna: So it's about being human. Not just a messenger. Lucas: Right. And that's a skill that translates to any role. Whether you're in customer service, management, or even just collaborating with colleagues, delivering bad news is inevitable. Interviewers know that, and they want to see that you have a thoughtful approach. Luna: Now, what are some common mistakes people make when answering this question? I bet a lot of people either sound too defensive or they try to sugarcoat the whole thing. Lucas: You're spot on. One mistake is blaming others. 'The engineering team didn't deliver on time.' That immediately raises red flags. You're not taking responsibility. Another is being vague. 'I told the customer there was a delay.' That gives no insight into how you handled it. Luna: And I'd guess some people also downplay the severity of the bad news, like saying, 'It wasn't a big deal.' That comes across as not caring. Lucas: Exactly. And the opposite extreme is being overly dramatic, which makes you seem like you can't handle pressure. The sweet spot is calm, factual, and empathetic. Luna: So how can someone prepare a good answer for this question before they even walk into the interview? Lucas: First, think of a specific instance where you had to deliver bad news. It doesn't have to be a huge catastrophe. It could be a missed deadline, a rejected proposal, or even telling a friend something they didn't want to hear. The key is that you had to communicate something negative. Luna: Okay, and then what? Lucas: Then, structure it using the STAR method, but focus heavily on the action. Write out the steps you took, especially the ones that show empathy and problem-solving. Did you listen? Did you offer alternatives? Did you follow up? Those are the details that make your story compelling. Luna: And I think it's also important to practice saying it out loud. It's one thing to write it, but another to deliver it naturally in an interview. Lucas: Absolutely. And one more tip: try to frame the bad news in a way that shows the bigger picture. For example, 'I had to tell my team that we were cutting a project I'd championed, but I explained how it allowed us to focus on higher-priority initiatives.' Luna: That reframes a negative into a strategic decision. It shows you're a team player and you see the larger goals. Lucas: Right. And that's the kind of answer that makes an interviewer think, 'This person can handle tough conversations.' And that's a huge asset in any role. Luna: Now, let's talk about the listener for a second. If you've been in an interview and struggled with a question like this, or if you're preparing for one, the fact that you're listening to us means you're already taking your career seriously. And if today's episode has been useful to you, the way we keep these episodes ad-free is through listener support. You can buy us a coffee at buy me a coffee dot com slash fexingo. It's a small gesture that goes a long way in helping us continue to bring you practical advice like this. Lucas: Yeah, we really appreciate that. It keeps the lights on and the mics on. But back to the question — I want to talk about a nuance that often gets missed. How do you handle delivering bad news to a boss versus a client or a direct report? Does the approach change? Luna: That's a great nuance. I'd say with a boss, you want to be more concise and solution-oriented, whereas with a client, you need to be more diplomatic and empathetic. With a direct report, it's about support and development. Lucas: Exactly. And interviewers love to hear that you can adapt your communication style to the audience. So if you can show that you're aware of these differences, that's a big plus. Luna: Any final thoughts on how to nail this question? Lucas: I'd say practice, but also be genuine. Don't try to memorize a script. Just remember the key points: take responsibility, show empathy, offer a solution, and communicate clearly. If you can do that, you'll turn a negative story into a positive impression. Luna: And that's what we're here for. Thanks for joining us, and we'll see you in the next episode. Lucas: Take care, everyone.