0Describe a Situation Where You Pushed Back on a Decision You Believed Was Wrong - Amazon LP Competency
Push back respectfully with data, then commit fully.
Have Backbone Disagree and Commit means confidently challenging decisions when you believe they are wrong, backed by data and logic, and fully committing once the decision is final. The core test is whether you can respectfully push back with conviction and then align with the team to execute.
Amazon wants leaders who are owners, not hired guns - they fix root causes by pushing back when needed, but once a decision is made, they commit fully and drive results.
- Simply agreeing with your manager or team without question
- Being confrontational or disrespectful in disagreement
- Disagreeing without data or rationale
- Refusing to commit after a decision is made
- Completing assigned tasks well - that is execution, not backbone
Shows initiative and courage to challenge the status quo, a core part of backbone.
Demonstrates that disagreement is grounded in logic and not personal opinion.
Shows emotional intelligence and collaboration while having backbone.
Indicates the candidate can disagree but not be disruptive; they support team decisions.
Shows the candidate’s disagreement led to measurable positive outcomes.
Demonstrates ownership beyond assigned scope, a key Amazon expectation.
Spend about 50 seconds on Situation and Task combined, then allocate 70% of your answer time to Action, detailing your specific steps and rationale.
- Describe a situation where you pushed back on a decision you believed was wrong.
- Tell me about a time you disagreed with your manager or team and how you handled it.
- Give an example of when you had to have backbone to challenge a direction.
- Explain a time you committed to a decision you initially disagreed with.
- Tell me about a time you influenced a difficult decision.
- Describe a situation where you had to convince others to change their mind.
- Give an example of when you took a risk by speaking up.
- Explain how you handled a disagreement in a team setting.
Keywords: pushed back, disagreed respectfully, raised concerns, committed after decision, data-driven challenge, outside my team, nobody asked.
I escalated it to the Payments team and they eventually fixed it.
Escalating and waiting = routing not ownership. This CONFIRMS you handed it off. Interviewer now rescores the opening answer as No Hire.
I flagged it to their tech lead for visibility. But I brought a complete fix, not just a problem report. Escalating without a solution adds 2-3 weeks at their sprint velocity.
I just felt the approach was risky.
Feelings alone do not demonstrate backbone; interviewer doubts candidate’s rationale.
I analyzed the error rates and found a 20% increase after the change, which indicated a regression that needed addressing.
I continued to push my viewpoint and didn’t support the final plan.
Refusing to commit signals poor teamwork and inability to align.
Once the decision was final, I aligned with the team and focused on executing the plan to the best of my ability.
I fixed the problem quickly.
Fixing without quantifying impact or influencing decision is weak.
My pushback prevented a potential $15K weekly loss and improved system uptime by 3%.
Amazon looks for long-term thinking - candidates should emphasize fixing root causes, not just symptoms. For example, say: 'I also proposed adding X to prevent this class of problem in future services.'
Candidates who explicitly articulate trade-offs and quantify business impact stand out. For example: 'I delayed a sprint item by 2 days because the cost of inaction was $8K per week, which justified the delay.'
Google values rapid iteration and consensus. Candidates should demonstrate how they used data to challenge decisions and then quickly aligned with the team to move forward.
Strong answers show balancing challenge with speed: 'I gathered data, proposed alternatives, and once the team decided, I committed fully to rapid execution.'
Meta encourages bold disagreement but expects quick commitment to avoid slowing progress. Highlight how you pushed back decisively but did not delay the project.
Emphasize boldness in disagreement and speed in commitment: 'I challenged the design with data but once the team decided, I moved fast to deliver.'
Flipkart expects disagreement framed around customer impact and ownership beyond one’s team. Candidates should highlight customer metrics and cross-team influence.
Frame disagreement around customer obsession and show cross-team ownership: 'I highlighted customer impact, influenced multiple teams, and committed to the final plan.'
At this level, candidates demonstrate backbone by identifying and disagreeing on tasks or bugs outside their assigned scope. They clearly state their individual contribution, and the impact is typically limited to their own team. Cross-team influence is not expected at this stage.
Candidates show backbone by engaging in disagreements involving multiple stakeholders or teams. They provide data-driven rationale, demonstrate respectful challenge, and fully commit to the final decision. Their impact is measurable beyond their own team.
Senior candidates lead cross-team disagreements on complex decisions. They explicitly balance trade-offs, influence senior stakeholders, and quantify business impact including long-term improvements. Their stories show strategic thinking and leadership.
Staff and Principal engineers drive organizational-level disagreements and alignment. They anticipate downstream effects, mentor others on backbone behaviors, integrate multiple leadership principles, and deliver multi-million dollar business impact.
Shows backbone by pushing back on a decision outside own team with data and logic, then committing. Demonstrates ownership and collaboration.
Candidate disagrees with a product feature decision using customer data, influences stakeholders, and commits to execution once decision is final.
Candidate challenges a technical design choice with data and trade-offs, influences team, and commits to implementation.
- Assigned Task Completion - Staying late = effort not proactivity. Deadline was assigned. Effort is execution. Ownership is self-initiated.
- Fixing Own Codebase Bug Quickly - No cross-team impact or disagreement. This is routine execution, not backbone.