How to Answer "Tell Me About a Time You Disagreed With Your Manager"
Show you pushed back respectfully with data, gave your manager your honest view, and then committed fully to the final decision — even if it wasn't yours. Interviewers assess backbone plus the maturity to commit. Avoid stories where you were insubordinate or where you were always proven right.
What the Interviewer Is Really Assessing
This is one of the most diagnostic behavioral questions. It tests two opposing traits at once: "Have Backbone" (will you voice a respectful, well-reasoned dissent to authority?) and "Disagree and Commit" (once a call is made, will you execute it wholeheartedly?). Amazon literally names this principle.
Interviewers want engineers who challenge ideas constructively but aren't divas. The ideal arc: you disagreed, you made your case with data through the right channel, the decision went a particular way, and you committed fully. Whether you 'won' matters far less than how you handled the disagreement.
The STAR Structure
The Result must contain a genuine 'commit' phase. Backbone without commitment signals a difficult report; commitment without backbone signals a pushover. You need both.
- Situation: The decision you disagreed with — a technical direction, a deadline, a priority call.
- Task: Your responsibility to surface your concern, given the stakes.
- Action: How you disagreed — privately first, with data, framed around shared goals, not ego. Then how the decision got made.
- Result: The outcome AND your commitment to it. Show you executed the final call well even if it differed from yours.
Sample Answer Outline
This outline deliberately includes a second case where the manager overruled the candidate and they committed anyway — the 'disagree and commit' arc that scores highest.
- S: "My manager wanted to ship a feature without rate limiting to hit a date; I believed it risked an outage at scale."
- T: "I needed to raise the risk clearly without just slowing things down."
- A: "I pulled traffic projections and modeled the failure case, then took it to her 1:1 rather than airing it in standup. I framed it as 'here's the risk and a cheap mitigation,' not 'this is wrong.' I proposed a basic rate limit that added only a day."
- R: "She agreed to the one-day mitigation. But on a separate call where she overruled me on the rollout plan, I committed fully and executed it — and it worked fine. She later told me she valued that I raised concerns directly and still got behind the decision."
Mistakes to Avoid
Being proven right every time reads as ego. Deliberately include a case where the decision went against you and you made it succeed — that's the harder, more valuable signal.
- Stories where you were insubordinate or went over your manager's head first.
- Always being proven right — it reads as ego; include a case where you committed to their call.
- Disagreeing publicly in a way that undermined your manager.
- Emotional or ego-driven pushback instead of data-driven.
- No 'commit' phase — backbone without commitment signals a difficult report.
ResuMax tailors your resume to each role, scores it like a recruiter, and preps you for interviews.
Practice with the interview coachFrequently asked questions
Is it risky to admit I disagreed with a boss?
No — the question demands it. The risk is showing only defiance or only compliance. Demonstrate both backbone and the ability to commit.
Should the story end with me being right?
Ideally include at least one case where the decision went against you and you committed and executed well. That 'disagree and commit' arc scores highest.
What channel should the disagreement happen in?
Show you raised it privately (a 1:1) and constructively first, not publicly in a way that undermines your manager.
How do I show 'commit' convincingly?
Describe doing the work wholeheartedly and the result — not grudgingly. 'I made the decision succeed even though I'd argued the other way.'