0Tell Me About a Time You Disagreed With Your Manager and How You Handled It - Amazon LP Competency
Respectfully challenge decisions, then fully commit.
Have Backbone Disagree and Commit means respectfully challenging decisions when you believe they are wrong, backed by data or strong reasoning, and once a decision is made, fully committing to it. The core test is whether you can push back constructively and then align without hesitation.
Amazon expects leaders to act like owners who dive deep and challenge decisions when necessary, but once a direction is set, they commit fully to deliver results.
- Blindly agreeing with your manager to avoid conflict
- Simply executing assigned tasks without question
- Disagreeing without data or rationale
- Being confrontational or disrespectful
- Delaying progress by refusing to commit after disagreement
Shows backbone and willingness to challenge decisions thoughtfully, a core Amazon leadership trait.
Demonstrates maturity to disagree but also commit, avoiding disruption after decision.
Shows Dive Deep combined with backbone, strengthening the challenge with facts.
Connects disagreement to business impact, showing ownership and results orientation.
Shows humility and ability to commit, critical for team cohesion and Amazon culture.
Spend about 70% of your answer on the Action section, detailing your specific steps to challenge and then commit. Keep Situation and Task combined under 50 seconds to maximize time for impact and reasoning.
- Tell me about a time you disagreed with your manager and how you handled it
- Describe a situation where you had to challenge a decision at work
- Give an example of when you pushed back on a direction you thought was wrong
- Have you ever disagreed with leadership? What did you do?
- Tell me about a time you had to influence a decision
- Describe a situation where you had to convince others to change their mind
- Give an example of when you had to stand your ground
- Tell me about a time you had to balance differing opinions
Keywords: disagreed, challenged, pushed back, alternative approach, committed after decision, respectfully, data-driven challenge.
I just told my manager my opinion and left it at that.
Shows poor communication and lack of follow-through; no influence demonstrated.
I prepared data-backed points, scheduled a one-on-one to discuss privately, and asked clarifying questions to understand their view while clearly presenting mine.
I kept pushing my idea because I thought it was better.
Shows inability to commit and undermines team alignment.
Once the decision was made, I aligned fully and focused on executing the plan to the best of my ability, supporting the team’s success.
No, my manager didn’t change anything.
Candidate appears ineffective or passive; no impact shown.
My challenge led to revising the design, which reduced latency by 15% and improved customer experience, avoiding costly rework.
I just said what I thought without worrying about consequences.
Shows lack of tact and poor judgment; may damage relationships.
I framed my disagreement respectfully, backed by data, and acknowledged their perspective to maintain trust while advocating for the best outcome.
Amazon looks for long-term thinking - fix root cause not just symptom. Candidates should show they challenged decisions to prevent future issues, not just immediate fixes.
To elevate your answer at Amazon, explicitly name the trade-offs you considered. For example, explain how you pushed back on a sprint item delay because the cost of inaction was higher than the delay cost. This shows ownership beyond immediate scope and long-term thinking.
Google values data-driven debate but also rapid alignment to maintain velocity. Candidates should show they challenged with data but committed quickly to avoid slowing the team.
Highlight how you balanced thorough challenge with rapid commitment to avoid blocking progress, demonstrating bias for action and respect for team velocity.
Meta encourages bold challenges but expects candidates to move fast and not get stuck in debate. Show you disagreed but quickly committed to keep pace.
Emphasize your willingness to commit quickly even if not fully convinced, with a clear plan to iterate later, showing agility and focus on speed.
Flipkart expects backbone to be customer-centric; disagreements must be framed around customer impact and ownership of outcomes.
Tie your disagreement directly to customer metrics and ownership of the customer journey, demonstrating deep customer obsession and accountability for outcomes.
At this level, candidates should demonstrate individual contributions where they identified a task or bug outside their assigned scope, clearly disagreed with a decision, and committed fully. Cross-team impact is not required but ownership of the disagreement is.
Candidates at SDE 2 level handle disagreements involving multiple stakeholders or teams. They drive discussions using data, influence decisions beyond their immediate scope, and show clear commitment after alignment.
Senior SDEs challenge complex and ambiguous decisions affecting multiple teams or products. They demonstrate leadership by influencing and aligning diverse opinions, quantifying impact and trade-offs, and driving consensus.
Staff and Principal engineers lead high-stakes disagreements involving senior leadership. They balance long-term vision and trade-offs, mobilize large teams across organizational boundaries, and commit to and drive execution of the final decision.
Shows backbone by challenging a design decision made by leadership or another team, with data and respectful communication. Demonstrates impact beyond own team.
Candidate pushed back on a new process or tool rollout that would reduce team velocity or quality, backing their position with data and proposing a better approach.
Candidate challenged prioritization decisions that would impact customer experience or technical debt, showing backbone and ownership of outcomes.
- Routine Bug Fix in Own Team - Does not show backbone or disagreement; just execution of assigned work.
- Effort-Based Stories (Working Late) - Staying late = effort not proactivity. Deadline was assigned. Effort is execution. Ownership is self-initiated.