Disagreement with Manager
Last Updated: June 4, 2026
Practice this question in a realistic, spoken behavioral interview.
Tell me about a time you had a disagreement with your manager.
A good answer here covers two things in one story: raising a real concern with your manager, then committing to the decision once it was made. Pick a disagreement about substantive work, walk through the decision you challenged, the risk you saw, the evidence you brought, how your manager responded, and what you did after the final call.
What the Disagreement Needs to Prove
The best version has both challenge and commitment in the same story:
- You raised the concern professionally: The conversation should be calm, private, and anchored in the work rather than ego.
- Your case had evidence: Bring data, user impact, technical risk, prior incidents, or a clearly stated principle. "I felt strongly" is not enough.
- You were willing to challenge upward: The versions that work show judgment and courage instead of automatic agreement.
- You committed after the decision: If your manager chose a different path, show how you supported the final call and helped it succeed.
Where This Answer Usually Goes Wrong
This question scores against Has Backbone / Disagree and Commit (Amazon), Influence (Google, Meta), and overall managerial collaboration. A few patterns reliably pull the writeup down.
The most damaging at L5+ is "I've never disagreed with my manager." It leaves no Backbone signal and suggests someone who may not push back when needed, which is often terminal for a senior role where challenging leadership is part of the job. A close cousin is the trivial disagreement: vacation time, scheduling, or work-from-home preferences do not probe the same competency as a technical or strategic call, and the trivial version comes across as a dodge.
Two framing problems show up next. The "I was right, they were wrong" narrative, where the manager exists in the story only to be wrong, downgrades Earn Trust and invites an uncomfortable follow-up about what happened to the relationship afterward. Worse is insubordination as the ending: continued resentment, going around the manager to their boss, or refusing to execute reads as a flight risk even when you were technically right.
The most commonly missed piece is the commit beat. A story that ends at "we disagreed and they made the call" is incomplete, because it never shows what you did to make the chosen path succeed despite preferring a different direction. Without it, the writeup notes that you disagreed but did not demonstrate commit.
Two smaller traps round this out. Outcome-laundering, where a manager's correct decision gets retold to make you look prescient, usually shows through; a clean "the call went against me and turned out to be the better one" scores higher than retroactive vindication. And conviction without evidence, "I felt strongly that we should use technology X" with no data, prior incidents, customer signal, or stated principle, sounds like opinion. The versions that work show what evidence you brought to the conversation.
How This Answer Changes by Level
The substance of what you push back on grows with seniority:
At staff+, "I disagreed with my manager about a code review" is the wrong scale. The expected story is closer to "I disagreed with my director about the multi-quarter direction for our area, brought a written counter-proposal, and we eventually agreed on a hybrid path."
Inside the Action Step
Three beats matter here: how you prepared, how the conversation actually went, and how you handled the decision afterward.
- Prepare with data: Walk in with more than conviction. Bring the evidence, risk, user impact, or technical principle that made the disagreement worth raising.
- Engage in dialogue: Explain how you approached the conversation. It was a private, respectful dialogue, not a public confrontation. You presented your case, but you also listened to their perspective.
- Respect the decision (disagree and commit): Clearly state what the final decision was and how you fully committed to making it work, regardless of whether you initially agreed with it.