Tell me about a time you had to say no to a stakeholder

Why interviewers ask this

Engineers who can't say no end up with unsustainable workloads and scope creep that hurts everyone. This checks whether you can protect the team's capacity while still being seen as helpful, not obstructive.

What a strong answer covers

• What was being asked, and why saying yes wasn't actually feasible or advisable
• How you delivered the "no" — did you just refuse, or did you explain the tradeoff and offer an alternative?
• The stakeholder's reaction, and how the relationship held up afterward
• Whether there was a partial yes available (a smaller version, a later timeline) that you offered instead of a flat refusal

Common pitfalls

• A story where you actually just quietly did the extra work instead of saying no — that's not answering the question asked
• No alternative offered, making the "no" sound unhelpful rather than a reasoned tradeoff