Tell Me About a Time You Delivered Bad News That Wasn’t Your Fault

Asked “tell me about a time you delivered bad news” when the cause wasn’t yours? Own everything after the cause. Engineers often carry news they didn’t create. A platform rule changes, a vendor drops an API or another team’s date slips. The weak answer stops at “it wasn’t my call, so I told them.” That makes you a courier. The strong answer shows four things you did control. First, you turned the outside fact into a clear consequence for this team. Second, you chose who heard it first and when. Third, you brought a recommendation with its cost stated. Fourth, you stayed with the problem after the meeting ended. Below, an invented Android engineer named Dara walks through one case. A Google Play policy took away a feature her product manager had already promised upward. The last section covers the case where your honest story is missing one of those four parts.

Bad news you didn’t cause still needs an owner in your answer

The question checks how you handle a message with real consequences for other people. Hello Interview’s page for this question lists recent reports from Meta and Gong. The site sells interview prep, so read it as one coach’s view. It warns that being only the messenger earns little credit. Its sample answers share one trait, though. In each, the candidate caused the delay they reported.

Those samples leave out a case engineers do run into. Sometimes nobody on the team caused the news. Then the answer can’t rest on “I admitted my mistake.” The credit has to come from what you did with a fact you didn’t choose. Was the bad news your own slip? Our post on missing a deadline you saw coming covers that case.

Amazon’s Leadership Principles page carries no date. Under “Earn Trust,” it asks leaders to “speak candidly” and to treat others with respect. That applies when the rule came from someone else. The interviewer wants to hear you deliver it plainly. Pointing at the source and stepping back doesn’t count.

Dara turned a policy page into one sentence about one feature

Dara worked on a secondhand marketplace app. Her product manager, Noor, had promised a “recent photos” strip in the listing flow. It showed a seller’s latest gallery photos so they could pick them with one tap. The strip needed broad photo access through the READ_MEDIA_IMAGES permission.

Google Play’s restricted permissions page shows no last-updated date. For apps targeting Android 13 or later, it limits that permission to cases where system pickers aren’t enough. Apps whose “core functionality revolves around broad access to Photos and Videos” may keep it. A gallery app fits that. A marketplace that needs a few photos per listing almost certainly doesn’t.

Dara’s first job was translation. Noor didn’t need the policy text. She needed one sentence: “The photo strip as designed won’t pass Play review.” Dara wrote that sentence only after reading the page herself. She also checked a second question before saying anything. Could a declaration in Play Console save the feature? The page requires one when an app argues the picker isn’t sufficient. Dara judged that argument would fail for a listing flow. She said that was her judgment, not Google’s ruling.

Interviewers hear the difference. An answer that says “Google banned our feature” sounds like the courier again. An answer that says “I read the rule and concluded it covered us” shows your reasoning. It also leaves room for the interviewer to probe that reasoning.

Who hears it first decides whether it lands as news or as an ambush

Noor had shown the strip in a quarterly planning deck. A director had seen it. Dara found the policy two weeks before the next roadmap review. She could have raised it in that meeting. She told Noor privately the same afternoon instead.

Name that order in your answer, because it was a choice. Noor owned the promise, so Noor heard first. That gave her time to decide how to tell the director. Dara also didn’t wait for a complete plan before telling her. She told Noor the problem that day and promised options within two days.

In your own answer, give the dates or the gap in days. “I told her right away” is hard to score. “Same afternoon, two weeks before the review” can be written down.

A recommendation with its cost is the part they score

Dara came back with three options. Option one was the Android photo picker. Android’s photo picker guide shows no last-updated date. It says the picker runs on Android 11 and later. Older versions get a backport through Google Play services. That kept photo selection working everywhere. The one-tap strip would go, though. Sellers would need one extra screen to choose photos. Option two was to file a declaration and ship the strip. She expected a refusal. The policy page says apps that don’t comply are subject to removal from Google Play. Option three was to delay the feature and redesign it.

She recommended option one and said what it cost. Noor would lose the feature she had demoed. Dara also offered to join Noor at the director review and explain the policy part. With that offer, Dara stops reporting the problem and starts sharing the hard conversation. Interviewers can write that down as a behavior.

Dara’s full answer to tell me about a time you delivered bad news

Early last year I was the Android engineer on our marketplace app’s listing flow. My product manager had promised a recent photos strip in the planning deck. A director had seen it. The strip needed broad photo access. I found that a Google Play policy limited that access to apps built around photos, like galleries.

I read the policy myself first. I concluded that our listing flow wouldn’t qualify. A declaration would likely be refused. I was clear that this was my reading, not a ruling from Google. I raised it with my product manager privately that afternoon. That was two weeks before the roadmap review. I promised options in two days.

I brought three. We could switch to the system photo picker, file a declaration and hope, or delay the feature. I recommended the picker. I was direct that it cost her the one-tap strip she’d demoed. Sellers would also get one extra screen. I offered to join her at the director review to explain the policy part. She accepted.

We shipped the picker version on the original date. The extra screen did cost something. Our listing funnel showed more drop-off at the photo step for about a month. Then design shortened the screen around it. My product manager later asked me to review policy changes during planning. Now I check Play’s policy deadlines page at the start of each quarter.

Dara, the app and the funnel result are invented for this post. Use the shape, then fill it from your own tickets, messages and dates. Each paragraph covers one thing Dara controlled. The first paragraph sets the stakes for someone else. The second gives her own reading and her timing. The third gives a recommendation with its cost. The fourth stays past the meeting, including a result that wasn’t clean.

When your honest story is missing one of the four parts

Your real story may have a gap. One likely gap is timing. You sat on the news for a week because you hoped it would resolve. Don’t hide that week. Say it. Then say what it cost the person who heard it late. Then say what you do differently now. For Dara, that might sound like this. “I waited four days to confirm the policy. That cost Noor four days of prep. Now I flag a likely problem the day I see it and confirm in parallel.”

In another gap, your manager delivered the news. You only drafted it. That story can still work if the draft was yours. Say what you wrote, why you framed it that way and what you recommended. Then name one part of the conversation you’d want to lead yourself next time. If you didn’t draft it, reached no conclusion and offered no option, choose a different story. Pick one where you made at least one call about the message.

Leave a Comment