Describe a time you had to deliver bad news
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess how you handle uncomfortable communication when the message has real consequences for other people. They want to see whether you are honest, timely, empathetic, and accountable rather than evasive, overly blunt, or passive. For more senior candidates, they are also testing judgment around audience, framing, and what you did after delivering the news.
Key Insights
- You do not get much credit for simply being the messenger; explain how you prepared, chose your approach, and helped people process the impact and next steps.
- Bad news stories are strongest when the consequences were real but your behavior was measured. If your example is trivial, or if you sound proud of being brutally direct, that usually lands poorly.
- You should make clear that you neither hid the problem nor dumped it on others. Strong answers show timely escalation, empathy for the recipient, and concrete follow-through after the conversation.
What interviewers probe atlevel
Top Priority
Even as a junior engineer, you should show that you understood the other person's inconvenience, stress, or disappointment instead of treating the conversation as a checkbox.
Good examples
🟢I knew my delay would block my teammate's testing, so I acknowledged the impact and asked what would help them most while I finished the fix.
🟢I explained the issue directly and also recognized that the designer had already planned around my timeline, so I apologized and talked through the impact.
Bad examples
🔴I just told them my task was late and figured they would adjust since delays happen all the time.
🔴I sent a short message saying I could not deliver and left it at that because the facts were what mattered.
Weak answers deliver information as if other people's plans do not matter; strong answers show awareness that bad news affects real people and responsibilities.
Valuable
Example answers atlevel
Great answers
In my first year, I owned a small backend change that another engineer needed before they could finish testing. After I started implementing it, I realized I had misunderstood one edge case and my original estimate was no longer realistic. Once I confirmed that, I told my teammate and my lead that day that I would miss the handoff and explained exactly what was blocked. I also suggested a smaller version I could finish first so testing could still start on most of the flow. We used that plan, and I sent short updates until the rest was ready. It was uncomfortable, but being direct early made it much easier for everyone to adjust.
On a small mobile team I owned the front-end work for a redesigned onboarding flow that was tied to a marketing launch. Two days before the campaign I discovered a performance regression that made cold-start times noticeably worse on older phones. Rather than quietly pushing a quick fix, I called the PM and marketing lead, explained the user-impact, and recommended we not ship the new flow as-is. I proposed three practical options—delay the launch for 48–72 hours while I optimized the hotspot, roll out the old onboarding behind a feature flag, or restrict the new experience to newer devices—and we agreed to use the feature flag so the campaign could run. I then sent concise status updates and hit the timeline; being upfront and offering alternatives preserved user experience and the team’s trust.
Poor answers
I had to tell my team once that my task was going to be late. I had been working on it for a while and there were more complications than expected, so I mentioned in standup that it probably would not be done that day. My lead picked it up from there and talked to the other people who were waiting on it. I think that worked well because I did not overreact before I had spent enough time trying to solve it myself.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid November, 2025
Early September, 2025
Early June, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.