Tell Me About a Time You Had to Say No to a Stakeholder and How You Did It - Behavioral Competency
Assertively say no while owning outcomes and relationships
This competency tests your ability to engage in difficult conversations, especially saying no to stakeholders, while maintaining professionalism and driving the best outcome. The core test is balancing assertiveness with empathy to resolve conflicts constructively.
Amazon wants leaders who are vocally self-critical and willing to challenge stakeholders respectfully; saying no is not about refusal but about owning the decision and its impact on customers and business.
- Avoiding conflict by agreeing with everyone
- Being confrontational or aggressive to win arguments
- Simply following orders without question
- Completing assigned tasks well - that is execution, not conflict management
- Ignoring stakeholder concerns or shutting down communication
Shows the candidate can assert boundaries with reasoning, not just refusal.
Demonstrates empathy and respect, critical for maintaining relationships during conflict.
Shows accountability beyond just saying no; they drive resolution.
Indicates strategic thinking and ability to manage trade-offs.
Emotional intelligence is key to productive conflict resolution.
Maintains long-term relationships and trust.
Spend about 50 seconds on Situation and Task combined, then devote 70% of your answer time to detailed Actions you took, followed by a concise Result with metrics and impact.
- Tell me about a time you had to say no to a stakeholder and how you did it.
- Describe a difficult conversation you had with a colleague or stakeholder.
- Give an example of when you disagreed with a stakeholder and how you handled it.
- Have you ever had to push back on a request that was unrealistic? What happened?
- Describe a time you managed conflicting priorities.
- Tell me about a situation where you had to influence without authority.
- Give an example of how you handled a disagreement on your team.
- Describe a time you had to deliver bad news to a stakeholder.
Keywords: said no, push back, disagreement, difficult conversation, conflict, negotiate, influence, manage expectations, handle objections.
"I just told them no when they asked."
Shows lack of preparation and thoughtfulness; suggests reactive rather than proactive behavior.
I gathered data on impact and constraints, anticipated their concerns, and prepared clear reasons and alternatives to present.
"They were upset but I didn’t engage further."
Avoids managing the relationship and conflict aftermath; no ownership of resolution.
They were initially frustrated, so I listened actively, acknowledged their concerns, and reiterated the reasons calmly to rebuild trust.
"No, I just said no and that was it."
Shows inflexibility and lack of ownership to find solutions.
Yes, I proposed a phased approach that met critical needs first while deferring lower priority items.
"The project was delayed but eventually completed."
Vague and lacks ownership of consequences or benefits.
By saying no, we avoided scope creep that would have delayed the release by 3 weeks and increased costs by 15%. This kept the team focused and stakeholders aligned.
Amazon looks for long-term thinking - fix root cause not just symptom. Saying no must be accompanied by ownership of the decision’s impact and proposing preventive measures.
Candidates who explicitly name the trade-offs involved, such as pushing back a sprint item by 2 days because the cost of inaction was $8K per week, demonstrate Amazon's emphasis on data-driven ownership. They also show ownership by describing how they proposed solutions to prevent similar issues in the future, reflecting long-term thinking.
Google values data-driven and empathetic communication. Saying no should be framed with clear facts and active listening to align stakeholders.
Strong answers combine quantitative evidence with a clear understanding of stakeholder needs. Candidates who describe how they used data to support their position and actively listened to concerns to maintain collaboration exemplify Google's emphasis on respectful, fact-based communication.
Meta values speed and decisiveness. Saying no quickly when necessary, while maintaining trust, is critical to avoid delays.
Candidates who highlight balancing speed with clear communication and maintaining stakeholder trust despite difficult conversations align with Meta's culture. They show how decisiveness prevented delays and how they proposed alternatives to keep projects on track.
Handled a conflict or said no within own team or immediate scope; demonstrated individual contribution and clear communication; no cross-team complexity required.
Managed conflict involving multiple stakeholders or teams; showed negotiation skills and ownership of the outcome; balanced trade-offs with data or rationale.
Led difficult conversations across teams or departments; influenced stakeholders without authority; demonstrated strategic thinking and long-term impact ownership.
Owned complex, high-impact conflicts involving multiple organizations; drove alignment on contentious issues; balanced competing priorities with clear communication and visionary solutions.
Shows ability to manage difficult conversations across teams, balancing competing priorities and maintaining relationships.
Demonstrates prioritization and assertiveness when resources are limited and demands exceed capacity.
Shows technical judgment and conflict management when asked to deprioritize critical fixes or quality improvements.
- Assigned Task Completion - No conflict or difficult conversation; just execution of assigned work. Does not demonstrate saying no or managing disagreement.
- Effort Without Conflict - Working late or hard without a difficult conversation does not show conflict management or communication skills.
