Describe a time you had to deliver bad news
Asked at:
Meta
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.
“Tell me about a time you had to share difficult information with someone.”
“Describe a situation where you had to tell people something they did not want to hear.”
“What's an example of a time you had to communicate a major setback or missed expectation?”
“Have you ever had to tell a team or partner that a commitment would not be met? What happened?”
“Walk me through a time you had to deliver an uncomfortable update.”
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
A strong junior answer does not end with delivering the news; it shows you helped unblock the situation within your scope.
Good examples
🟢After telling my teammate I would miss the handoff, I proposed a smaller deliverable they could use first and kept them updated until it was ready.
🟢I shared the problem early, asked my lead for help on the hardest part, and owned finishing the remaining work and reporting progress.
Bad examples
🔴I let them know I was behind and then waited for my lead to tell me what to do next.
🔴After I shared the issue, I assumed the other person would replan around it and I just went back to my task.
Weak answers treat communication as the finish line; strong answers treat it as the start of coordinated recovery.
At junior level, interviewers mainly want to see that you did not avoid the conversation, sugarcoat the reality, or wait for someone else to clean it up.
Good examples
🟢Once I confirmed the issue, I told my mentor and then updated the teammate depending on my piece of work the same day that my part would be late.
🟢I was nervous about disappointing the person waiting on me, but I told them clearly that I had found a problem and that the original date was no longer realistic.
Bad examples
🔴I knew the estimate was slipping, but I waited until standup and mentioned it briefly so my lead could decide how to tell everyone.
🔴I tried to keep the conversation positive and told them it was mostly fine, even though I already knew we would miss the handoff date.
Weak answers avoid discomfort and blur the reality; strong answers communicate the truth clearly once the candidate has enough confidence in the facts.
Valuable
You do not need executive-level polish, but you should show basic judgment about telling the right person early enough and not speaking before you understand the issue.
Good examples
🟢I did a quick check to make sure the issue was real, then I told the teammate and my lead before it caused a downstream surprise.
🟢I chose a direct conversation instead of dropping the message into a busy group chat because the impact was specific and time-sensitive.
Bad examples
🔴I warned a broad channel as soon as I suspected there might be a problem, which created noise before I had checked the facts.
🔴I spent too long trying to fix it alone before telling anyone because I wanted to be sure I had solved it first.
Weak answers show either premature alarm or delayed disclosure; strong answers balance fact-checking with timely communication to the right people.
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
Meta
Manager
Early September, 2025
Meta
Manager
Early June, 2025
Meta
Manager
Hello Interview Premium
Your account is free and you can post anonymously if you choose.