Tell me about a time you had to deliver bad news to stakeholders about a release.

Stakeholders judge you by how you behave when things go wrong. Honesty plus structure builds the trust you'll draw on for years.

STAR walkthrough — sample answer:

Situation: A previous team had committed to a release date for a customer-facing feature, with marketing already lined up. About 5 days before the planned date, I'd been running E2E and performance testing and concluded the release wasn't ready: not because of one big bug, but because of an accumulation of small issues — a flaky integration that we couldn't reproduce locally, a performance regression of about 30% on a critical page, and incomplete handling of a third-party error case.

Task: Tell the PM and engineering manager — and ultimately the marketing stakeholder — that the release wouldn't make the date, soon enough that the marketing window could be adjusted.

Action: I didn't message it half-formed. Took 30 minutes to structure what I was going to say:

1. Headline first. "I'm recommending we slip the release by 1 week. Here's why."
2. Three specific reasons with evidence — flaky integration test (3 of 10 runs failing, can't reproduce locally), performance regression (data attached, pre/post comparison), and the unhandled error case (description + worst-case impact).
3. Two options, each costed: (a) push the release 1 week, fix all three; (b) slip 3 days, ship with the performance regression flagged as known-issue, fix in the next release. Recommended (a).
4. What I'd already done — to make sure the message wasn't "we should slip" but "we should slip and here's what's in flight to recover."

Took it to the eng manager and PM together, in a brief meeting rather than written-only. They decided on option (a), with PM taking it to the marketing stakeholder. I offered to be in that conversation if useful — they declined but kept me available for clarifying questions.

The marketing conversation went better than expected. The stakeholder appreciated the lead time (5 days vs. day-of); they re-cut the launch communication for the new date and avoided a more painful retraction.

Result: Release went out clean a week later. The marketing stakeholder mentioned in a later all-hands that the team had handled the slip professionally — that explicit credit changed how senior leadership framed similar situations afterwards. I was looped in earlier on subsequent launches.

What I learned: bad news delivered well strengthens trust. Sugarcoating or hoping things will work out leaves you worse off when reality lands.

Why this works: structured delivery (headline → reasons → options), respected the right people's authority (PM owns the marketing conversation), early enough timing, and the long-term outcome was increased trust rather than damaged credibility.