Conflict & disagreement
How to answer: “Tell me about a time you disagreed with your manager”
A judgment and disagree-and-commit test. Show you can push back respectfully with evidence, then fully support the final call.
Why it is asked
What this question is really testing
This question tests two things that sit in tension: do you have the backbone to push back on a decision you think is wrong, and do you have the maturity to commit fully once the decision is made anyway. Interviewers worry about both extremes, the pushover who never raises concerns and the person who relitigates losses, so your answer should show the healthy middle.
Pick a real disagreement where you pushed back with evidence and respect, privately and on substance. Then, crucially, show what happened after the decision. The strongest answers include a disagree-and-commit moment: your manager went the other way, you backed the call completely, and you describe that without resentment. If your concern turned out valid, show grace; if it turned out wrong, show you learned.
Never tell this as a story about an incompetent manager. The hero of the story is your judgment and your professionalism, not your manager's flaws.
The signal
What interviewers listen for
- Willingness to disagree, raised respectfully and on substance.
- Evidence and reasoning, not just a gut objection.
- Disagree-and-commit: full support for the final decision.
- No bitterness or relitigating, whichever way it turned out.
Worked example
A STAR answer you can adapt
Scenario: Engineer who pushed back on a rewrite. Read it for the shape, then swap in your own story.
Situation
My manager wanted to rewrite a service from scratch; I thought an incremental refactor was lower risk.
Task
It was a big bet and I felt strongly it was the wrong one.
Action
I asked for fifteen minutes one-on-one and laid out the risks with a rough timeline comparison and the migration history of a similar rewrite that had gone badly. I made the case once, clearly, and asked questions about what I might be missing.
Result
He still chose the rewrite, partly for reasons I had not had full context on. I committed to it completely and ended up leading a chunk of it. It took longer than I would have liked but landed well, and he later told me he valued that I raised the concern and then got fully behind the call. I learned to weight context I cannot see.
Answer skeleton
Fill-in-the-blank template
I disagreed with [decision]. I raised it privately with [evidence]. They chose [their call] for [context I lacked]. I committed fully and [outcome]. I learned [lesson], with no hard feelings either way.
Avoid these
Common mistakes
- Portraying your manager as foolish and yourself as obviously right.
- Pushing back in public or on emotion rather than evidence.
- Failing to commit, or quietly undermining the decision afterward.
- Picking a trivial disagreement with no real stakes.
By role
How the answer shifts by role
Engineering
A technical-direction disagreement backed by data is ideal. End with genuine disagree-and-commit.
Product management
A roadmap or prioritisation disagreement works if you show you advocated for the user and then aligned.
Engineering management
Disagreeing with your own skip-level or a peer manager shows you can push up while modelling commitment for your team.
Be ready for
Likely follow-up questions
- How did you feel once the decision went against you?
- What would you have done if you still strongly disagreed?
- Has there been a time your manager changed their mind because of you?
Last reviewed by the site editor: June 2026
More practice
Other questions worth a rehearsal
If this question is on your list, these usually belong there too.
Turn prep into an offer
Behavioral rounds are only half the loop. See the technical and behavioral questions for your exact role, and when an offer lands, check it is competitive with the salary comparison tool.