Delivering Bad News to a Team or Stakeholders Without Losing Trust
Company: Gong
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Other
Describe a time you had to deliver bad news, such as a missed deadline, a serious defect, a cancelled project, or a decision people would dislike. Explain who needed to hear it, how you prepared, how and when you delivered it, and what happened afterward.
```hint Timing is part of the story
Be ready to say when you first knew and how long it took you to tell the people affected.
```
```hint Bring a path forward
Think about what the listener needs besides the news itself in order to make a decision or move on.
```
### Clarifying Questions
- Should the news be bad for my own team, for a stakeholder or for a customer, or does any of those work?
- Do you want a case where I was responsible for the problem, or one where I only had to communicate it?
### What a Strong Answer Covers
- Raising the issue early, before certainty, with an honest confidence level
- Choosing the right audience and order, so that key people were not surprised
- A delivery that leads with the facts and impact, followed by options and a recommendation
- Ownership without blame-shifting or excessive apology
- Follow-through after the conversation and a lasting improvement
### Follow-up Questions
- How did the recipient react, and how did you handle that reaction?
- What would have happened if you had waited another week to say it?
- How would you deliver the same news to an executive versus to your own team?
- Tell me about a time you delivered bad news badly.
Overview: A behavioral interview question about a time you had to deliver bad news such as a missed deadline, a serious defect or an unpopular decision. It tests timing, choosing the right audience, delivering facts with options and a recommendation, owning the problem without blame, and following through afterward.