Loading…
A 4-phase interactive guide to this behavioral interview question — asked at Amazon, Google, Meta, Microsoft: decode what the interviewer assesses, build a STAR answer structure, and drill the follow-up questions it typically draws.
“Tell me about a time you disagreed with your manager.”
2–3 minute core answer, then 5–8 minutes of follow-ups
Have Backbone; Disagree and Commit · Earn Trust
Before reading anything else: how would you answer this out loud, right now? Pick the story you'd use, then move to Decode to check whether it shows what the interviewer is actually listening for.
This question tests whether you can push back on authority professionally — and whether you commit once a decision is made. Interviewers have seen two failure modes: engineers who never disagree (no backbone) and engineers who can't let go after losing the argument (no commit). They want evidence you can do both.
Backbone
You raised the disagreement directly with the person, not around them — and you did it when it still mattered, not in the retrospective.
Name the exact moment you raised it and to whom. "I booked 30 minutes with my manager the same week" is evidence; "I had concerns" is not.
Data over opinion
Your disagreement was grounded in evidence — benchmarks, incident history, customer impact — not preference or ego.
State the specific data you brought: "I pulled the last quarter's on-call pages and showed 40% traced to the component we were about to extend."
Disagree and commit
If the decision went against you, you executed it wholeheartedly instead of slow-rolling or saying "I told you so" later.
Describe what committing looked like in practice — you built the thing you argued against, and you didn't relitigate when it hit friction.
Relationship intact
The disagreement improved or preserved trust with your manager rather than damaging it.
End with the relationship outcome: your manager brought you into the next decision earlier, or explicitly thanked you for the pushback.
🚩 Choosing a story where you were obviously right and the manager obviously wrong
It reads as ego, avoids the hard part (committing to a decision you dislike), and interviewers discount stories where the candidate is the flawless hero.
🚩 Escalating over the manager's head as the first move
Skipping the direct conversation signals you damage trust under disagreement. Escalation should appear, if at all, as a transparent later step.
🚩 "We compromised and met in the middle" with no specifics
A vague compromise ending suggests the story is invented or that you avoided the actual decision. Real disagreements end with a decision someone owns.
Reveal all 4 signals to unlock the red flags and the answer structure.
One or two sentences of context: the project, the stakes, and the decision on the table. The interviewer needs just enough to understand why the disagreement mattered.
Spending a minute on org charts and project history. If the situation takes longer than 20 seconds, the interviewer is already redirecting you.
State the disagreement crisply as a decision conflict: what they wanted, what you believed, and what was at stake if either side was wrong.
Framing the manager's position as unreasonable. Acknowledging their constraint was legitimate is what makes the story senior.
This is 50% of the answer. Walk through how you raised it, what evidence you brought, how the conversation went, and what was decided. Be concrete about your exact moves.
Narrating opinions instead of actions. "I felt strongly and made my case" contains zero verifiable behavior — name the meeting, the artifact, the words.
Close with the concrete outcome, what the disagreement cost or saved, and what it did to the relationship. A quantified result plus a trust outcome is the strong ending.
Ending at the technical outcome and skipping the relationship. This question is about trust under disagreement — say what happened to it.
Your core answer is only the opening move. Interviewers spend most of the round drilling into it — these are the follow-ups this question typically draws. Try answering each out loud before revealing anything.
What would you have done if your manager had said no to the compromise too?
HardThe interviewer is testing whether you know the difference between disagreement and insubordination — and where escalation legitimately fits.
Strong candidates say they would commit and execute, while putting the risk in writing so the decision was informed — and they distinguish reversible from irreversible decisions. For a truly irreversible, high-stakes call, transparently telling the manager "I'd like us to get a second opinion together" is legitimate; going around them quietly never is.
Have you ever disagreed, committed — and then been proven right? How did you handle that?
HardThis probes for hidden resentment. The worst answer is enjoying the vindication.
The strong answer focuses on making the failure cheap to recover from rather than being right: they helped fix the fallout without "I told you so," and used the retro to improve how the team makes that class of decision — not to score the point.
How do you decide which disagreements are worth raising at all?
MediumThey're checking you have a filter — engineers who fight every decision are as ineffective as those who fight none.
Strong candidates describe a threshold: one-way-door decisions, customer or reliability impact, or ethical concerns always get raised; reversible preferences get one mention and then commitment. Naming the two-way-door versus one-way-door framing lands especially well at Amazon.
Work through the other behavioral questions, or switch tracks to system design and coding.