"Tell me about a time you disagreed with a decision but committed to it anyway."
This one trips people up. You're being asked to prove two things that feel like opposites: that you have real opinions, and that you can let them go. Lean too hard on the disagreement and you sound like the person nobody wants in a planning meeting. Lean too hard on the commit and you sound like you have no spine. The whole skill is holding both at once.
I'll walk through what the question is actually testing, then a structure that lands, then a worked example you can adapt.
What the interviewer is checking
They want to know how you behave when you're outvoted. That's it. Every team makes decisions you won't agree with, and the expensive employees are the ones who keep relitigating those decisions for weeks, slow-walking the work, or telling the rest of the team "I told you so" when something breaks.
So the interviewer is listening for a few specific things:
- You raised your disagreement clearly, to the right person, at the right time.
- You did it before the decision was final, not after.
- Once the call was made, you actually committed. You didn't sandbag.
- You can tell the difference between a hill worth dying on and a normal tradeoff.
Notice what's not on that list: being right. You do not need to have been right. Some of the best versions of this story end with the team's decision working out fine and you admitting you'd have made the wrong call.
A structure that works
Use the bones of STAR (situation, task, action, result), but spend your time deliberately. The mistake most people make is burning the whole answer on the disagreement and rushing the commit. Flip that.
- Set the stakes in two sentences. What was the decision, and why did it matter? Keep it tight.
- State your disagreement and how you raised it. This is where you show judgment. Name your actual concern, who you took it to, and that you brought a reason, not just a vibe.
- Mark the moment the decision was made. One clean sentence: "Leadership decided to go the other way." This is the pivot.
- Spend real time on the commit. What did you do to support the decision you'd argued against? This is the part that separates candidates.
- Close with the result and what you learned. Honest beats heroic.
The center of gravity should be steps 4 and 5. The disagreement earns you credibility; the commit is what they're hiring for.
A worked example
Here's a version, kept generic so you can swap in your own details.
"We were picking a database for a new service. I pushed for Postgres because the team already knew it and the data was relational. The tech lead wanted to use a managed NoSQL store the platform team was standardizing on. I laid out my case in the design review: the relational shape, the migration cost, the on-call burden of a tool nobody on our team had run before. I wrote it up so the tradeoff was on the table, not just in my head.
The lead heard it and still chose NoSQL, mostly for long-term consistency across the org. Once that was decided, I stopped arguing. I volunteered to write the data-access layer so we'd have a clean abstraction, and I spent a Friday going through the platform team's runbook so I could be the person who knew it, not the person complaining about it. I also wrote down my original concerns in the design doc as risks to watch, framed neutrally, so if they showed up later we'd catch them early.
It shipped fine. One of my migration worries turned out to be real and we hit it in month two, but because it was already logged as a risk, we'd budgeted time for it and it was a half-day fix instead of a fire. I'd still probably reach for Postgres by default, but I learned that org-wide consistency was worth more than I'd weighted it."
That ending does a lot of quiet work. You were partly right, you say so without gloating, and you name a thing you genuinely updated on.
Common ways this answer goes wrong
- The fake disagreement. "I disagreed but I was totally on board." That's not a disagreement, it's a humblebrag, and interviewers clock it instantly.
- The grudge. Any hint that you committed on the surface while rooting for the decision to fail. Watch your tone on the result.
- The doormat. No real disagreement at all, just "I do what I'm told." They asked for judgment. Show some.
- Picking a trivial stakes story. If the disagreement was about tabs versus spaces, the commit doesn't prove anything. Pick something that cost you to let go of.
Before the interview
Have one of these ready, written out and said out loud at least twice. Pick a story where you cared about the outcome and the team went the other way. Practicing it against a mock interview helps a lot here, because the failure mode is tone, not content, and you can't hear your own tone reading silently.
The goal isn't to sound agreeable. It's to sound like someone who can argue hard, lose, and still row in the same direction. That person is worth a lot, and this question is the cheapest way for an interviewer to find them.