How to Answer: “Tell Me About a Time You Disagreed With a Decision”
Why interviewers ask it, what they are actually scoring, a repeatable structure that works, three sample answers for different levels, and the quiet mistakes that sink otherwise strong candidates.
What the Question Is Really Testing
On the surface it sounds like a story prompt. In practice, “tell me about a time you disagreed with a decision” is a compact test of professional maturity — whether you can hold an opinion, express it well, and move forward gracefully whether or not it wins.
The question shows up in almost every behavioural interview loop, from first-round screens to executive rounds. It is deliberately open-ended because the interviewer is not fishing for a single “right” disagreement — they are watching the shape of your answer to see how you approach conflict, communicate under pressure, and behave once a decision has been made. Everything that follows is a way to make sure the shape of your answer says what you want it to say.
The strongest answers are not about being right. They are about how you disagreed — respectfully, with evidence, at the right time, to the right person — and what you did after the decision was made, whether or not it went your way.
Why Interviewers Ask This
This question isn’t really about the disagreement itself. Interviewers use it to check three things at once, all rolled into a single story prompt.
First, whether you can hold a professional opinion without being either a pushover or a bulldozer. Second, whether you communicate disagreement constructively rather than destructively. Third, whether you know how to move forward once a decision is made — even one you didn’t agree with. Rolled together, it is a proxy for a much blunter internal question the interviewer is quietly answering on your behalf: “will this person be easy to work with when they don’t get their way?”
Do you hold an opinion at all?
Candidates who cannot recall a single professional disagreement, or who describe themselves as “pretty easy-going, I usually just go with the team,” often read as either inexperienced or conflict-avoidant. Interviewers want to see that you have a spine and use it.
Do you disagree constructively?
The interviewer is watching whether you raise concerns with evidence, at the right time, to the right person — or whether you vent, escalate too fast, or corner people in public settings. The how matters more than the what.
Can you commit after losing?
What happens after the decision is made is the quiet second half of the question. Interviewers want to hear that you shifted from advocate to executor cleanly — not that you kept relitigating, undermined the choice, or waited to say “I told you so.”
Do you learn from it?
Answers that end in self-aware reflection almost always outscore answers that end in vindication. If your whole story climaxes at “and then they realised I was right,” you have missed the point of the question.
Notice how none of the four signals rely on the outcome going your way. A candidate who lost the argument can still score at the top of the rubric — and a candidate who won can absolutely land at the bottom if the way they won painted them as difficult to work with.
What “Good” Looks Like
Almost every behavioural rubric for this question maps onto a small set of green flags and their matching red flags. Reading down both columns before you rehearse is the fastest way to notice which side your current draft leans toward.
| Signal interviewers look for | Signal that raises concern |
|---|---|
| You raised the disagreement directly and early, not passive-aggressively. | You went along silently, then complained about it afterward — to peers, a partner, or in a later 1:1. |
| You used data, reasoning, or a specific risk to make your case. | Your objection was based purely on personal preference or “gut feeling” with nothing behind it. |
| You stayed respectful even when the other person held firm. | You describe the other person as wrong, foolish, or incompetent — even in gentle language. |
| You committed fully once the decision was made (“disagree and commit”). | You quietly undermined the decision or kept re-litigating it in later meetings. |
| You reflect on what you learned, win or lose. | The story has no self-reflection — it’s just “I was right and they realized it.” |
Interviewers pick up on tone as much as content. Even factually correct stories delivered with residual resentment (“honestly, I still think it was a bad call”) can flip a green-flag answer into a red-flag one. Aim for calm, retrospective, and grown-up — especially about people who are not in the room to defend themselves.
A useful reframe: pretend the person you disagreed with will read the transcript of your interview. Would they recognise their reasoning as fairly represented? If not, tighten it. The strongest candidates describe the other side’s position generously enough that the disagreement sounds like two reasonable professionals looking at the same facts differently — which is almost always closer to what actually happened.
The Structure — STAR (plus one extra beat)
Use the standard STAR framework, but add a fifth beat at the end — Reflection — because this question specifically rewards self-awareness about how you handle disagreement, not just what happened.
Situation
Briefly set the scene: what was the decision being made, and who was involved? Two or three sentences, no more. Enough context for the interviewer to picture the room, no scene-setting for its own sake.
Task
What was your role, and why did you disagree? What was actually at stake — a deadline, a cost, a customer risk, a technical debt trap? Anchor the disagreement to something concrete an interviewer can hold in their head.
Action
How exactly did you raise the disagreement? What did you say, and to whom? Did you bring data or an alternative proposal? This is where interviewers really lean in — the specifics of how you handled the moment do more work than the rest of the story combined.
Result
What happened? Did the decision change, stay the same, or land somewhere in between? Be honest about the outcome — especially if it didn’t go your way. A story where you gracefully lost often scores higher than a story where you won.
Reflection
What did you learn about disagreeing well, and how has it changed how you approach similar situations since? This is the beat almost everyone drops under time pressure — and it is the one interviewers remember.
Keep the whole answer to roughly 90 seconds to 2 minutes when spoken aloud. Interviewers will ask follow-up questions if they want more detail — a common mistake is over-explaining the technical backstory and running out of time before reaching the actual disagreement and its resolution.
A quiet cheat that helps under real interview pressure: write the five beats onto a single sticky note, in order, and glance at them once before the round starts. It sounds trivial, but candidates who mentally chunk their story into five discrete beats almost never run out of time, because they can feel themselves lingering too long in Situation or Task before they get to the parts that actually score.
Choosing the Right Story
Not every disagreement makes a good interview story. Before you commit to one, put it through the four filters below — a strong story picked well often outperforms a weaker story delivered brilliantly.
Professional, not moral or personal
Pick a real professional disagreement, not a moral or personal one. A disagreement about a technical approach, a project priority, or a process decision works far better than anything involving ethics violations, HR issues, or conflict with a difficult personality — those read as either too heavy or too personal for this format.
Aim up or sideways, not down
Pick a disagreement with someone senior to you, or a peer — not a direct report. Disagreeing “up” or sideways shows more courage and is more relatable to most interviewers than disagreeing “down.” Disagreements with a report can drift into “how you manage” territory, which is a different question entirely.
You didn’t automatically win
Pick a story where you didn’t automatically get your way. A story where you disagreed and were immediately proven right can come across as self-congratulatory. A story where the decision went the other way — and you handled that well — is often more convincing, because it lets the interviewer see how you behave when the outcome isn’t what you wanted.
No villains, especially clueless ones
Avoid stories where you were clearly right and the other person was clearly incompetent. Even if true, this framing makes you look difficult to manage, not thoughtful. The best stories describe a reasonable person making a reasonable decision that you happened to see a specific problem with — not a foolish person being rescued by you.
Prepare two stories, not one. One where the decision changed after your input, and one where it didn’t — and you committed anyway. Which you tell depends on which signal the interviewer seems to be probing for by the time the question lands.
Sample Answer 1 — IC vs. Technical Lead
This first sample answer is aimed at an individual contributor disagreeing with their technical lead over the timing of a framework migration. Notice how the outcome ends up as a compromise rather than a clean win — and how the reflection at the end does more scoring work than any individual sentence in the body.
“On my last team, our tech lead wanted to rewrite our reporting service in a new framework mid-quarter, mainly because a couple of other teams were adopting it. I disagreed — we had a release deadline in six weeks, and the existing service, while not perfect, was stable and well-tested.
I asked for 15 minutes to walk through the risk: the migration would touch our most business-critical reports, we’d lose a week just to learning curve, and if anything broke, finance couldn’t close the books on time. I proposed we ship the current release on the existing stack, then run the migration as its own project with proper testing time afterward.
He still felt strongly about starting the migration immediately, so we agreed to a middle ground: he’d prototype the new framework on a low-risk internal tool first, and we’d revisit the bigger migration after the release. That prototype actually surfaced two integration issues we hadn’t anticipated, which made the eventual full migration — which we did do, three weeks later — much smoother.
What I took from it is that timing matters as much as being right. I wasn’t against the idea itself, just the timing, and framing it that way — rather than just saying ‘no’ — made it much easier to find a path we both felt good about.”
Why this answer works
- Concrete risk, not opinion. The candidate names the exact business impact — finance couldn’t close the books — instead of arguing on abstract technical grounds.
- Alternative proposal, not a flat “no.” Suggesting the prototype-on-a-low-risk-tool compromise shows collaborative problem-solving rather than opposition.
- Generous framing of the other person. The tech lead is described as reasonable and thoughtful, not stubborn. The disagreement was about timing, not competence.
- Self-aware reflection at the close. “Timing matters as much as being right” is a real, transferable lesson — not a boilerplate “communication is important.”
Sample Answer 2 — Disagreeing With a Product / Priority Decision
This sample answer covers a cross-functional disagreement — an engineer pushing back on a product manager’s roadmap priority. Notice how the entire disagreement gets reframed as a data question, which is almost always the most productive way to disagree across a functional boundary.
“A product manager wanted us to prioritize a flashy new integration over fixing a checkout bug affecting about 2% of orders. On the surface 2% sounds small, but I pulled the numbers and showed it was actually costing us a meaningful chunk of monthly revenue, and support tickets about it were trending upward.
I didn’t just say ‘I disagree’ — I put together a one-page comparison: estimated revenue impact of the bug fix versus projected adoption of the new integration in its first month, based on similar past launches. I shared it in our planning meeting, not as a confrontation, but as ‘here’s the data, what am I missing?’
She hadn’t seen the revenue breakdown before and agreed to swap the priority order — we fixed the bug first, then shipped the integration two weeks later than originally planned. What stuck with me is that disagreements land much better as questions backed by data than as flat statements of opinion. It also wasn’t personal — she made a reasonable call with the information she had, and giving her better information, respectfully, was enough.”
Why this answer works
- The disagreement is framed as an information gap, not a judgement call. The PM isn’t wrong — she just didn’t have the revenue numbers. That framing preserves her professional dignity while still making the case.
- The one-page comparison is doing real work. Written artifacts prepared before the meeting let complex trade-offs be considered without anyone needing to react in the moment in front of others.
- Asked as a question, not a verdict. “Here’s the data, what am I missing?” is one of the highest-leverage phrases in cross-functional disagreements — it invites correction rather than demanding capitulation.
- Reflection generalises well. “Disagreements land much better as questions backed by data than as flat statements of opinion” is a lesson interviewers can imagine you applying on their team next quarter.
Sample Answer 3 — When the Decision Didn’t Change
The third sample is the most under-rated of the three. It is a story where the candidate raised a real concern, lost, committed fully, and turned out to be partly right — but never says so smugly. This is often the single strongest “disagree and commit” story to have in your back pocket.
“My manager decided to consolidate our three regional data pipelines into one shared pipeline to cut infrastructure costs. I disagreed, because I thought the shared pipeline would create a single point of failure and make on-call rotations harder across time zones.
I raised it directly in our 1:1, laid out the failure-mode risk, and even sketched an alternative that kept some redundancy. She heard me out, but ultimately decided the cost savings were worth it given budget pressure that quarter, and made the call to move forward with full consolidation.
Once the decision was made, I didn’t keep pushing it in every meeting — I focused on making the shared pipeline as resilient as I could, and made sure we had strong alerting and a clear on-call runbook to cover the risk I’d flagged. About four months later we did have an incident that touched all three regions at once, and having pushed hard for good monitoring up front meant we caught and fixed it in under 20 minutes instead of it becoming a much bigger problem.
That experience taught me that disagreeing doesn’t mean you get to slow-walk a decision once it’s made. My job at that point was to make the decision we did make work as well as it possibly could.”
Why this answer works
- Real dissent, cleanly documented. The candidate raised the concern in the right forum (a 1:1), with a specific risk and an alternative — not a vague objection.
- Genuine commit, not performative. They didn’t drop the concern — they hedged it by investing in monitoring and a runbook, which is what “committing fully” actually looks like in practice.
- Vindication without gloating. The incident happened, but the story credits the outcome to the up-front resilience investment, not to being right. That framing is nearly impossible to over-index on.
- Reflection is grown-up. “Disagreeing doesn’t mean you get to slow-walk a decision once it’s made” is precisely the sentence interviewers hope to hear.
Do’s and Don’ts
Almost every strong answer to this question shares the same handful of habits; almost every weak one falls into the same handful of traps. The table below is the shortest usable version of both lists.
| Do | Don’t |
|---|---|
| Use a real, specific example with concrete detail. | Speak in vague generalities (“I often disagree with things…”). |
| Show you raised it early, directly, and privately when appropriate. | Describe complaining to peers instead of the decision-maker. |
| Bring data, a risk, or an alternative — not just an opinion. | Frame it purely as “my gut told me it was wrong.” |
| Acknowledge the other person’s reasoning, even if you still disagreed. | Paint the other person as clueless or incompetent. |
| End with what you learned or how you’ve grown. | End the story right at “and I was right,” with no reflection. |
| Show you committed fully once a decision was made, even if it wasn’t yours. | Imply you quietly worked around or undermined the decision. |
Watch for “we” drifting into “they” as your story reaches its climax. Candidates who describe the setup as “our team was deciding” and the aftermath as “they made the wrong call” give away that they haven’t fully integrated the outcome. Keep it “we” the whole way through, even when you disagreed with the decision.
Likely Follow-Up Questions — Prepare for These
Behavioural interviewers rarely stop at the first answer. They almost always probe in the same four directions, so preparing a one-sentence reflex for each of them will keep the second half of the conversation as controlled as the first.
“What would you have done differently if they still hadn’t listened?”
Interviewers are checking whether you have a next move that isn’t “give up” or “go around them.” A strong answer names the specific next step — a written memo, a broader stakeholder conversation, or a legitimate escalation path — without sounding threatening about it.
“How did the relationship with that person evolve afterward?”
This is the interviewer checking whether disagreements damage your working relationships long-term. A strong answer notes concretely that trust either held or actively improved — because that is the exact outcome the whole process is meant to preserve.
“Was there a moment you considered escalating further, and why didn’t you (or why did you)?”
They are probing your judgement on when to escalate. The best answer distinguishes clearly between a preference (rarely worth escalating) and a genuine non-negotiable such as safety, legal, or security concerns (where prompt escalation is the responsible move).
“Looking back, do you still think you were right?”
Resist the urge to simply say yes. A more compelling answer acknowledges genuine trade-offs on both sides, even if you’d still lean the same way today. It shows you can hold nuance rather than needing to “win” the story in hindsight.
The wrong shape of answer is “yes, absolutely.” The right shape is more like: “I still lean the same way, but I understand better now why the other side made the call they did — and if I’d had their context at the time, I might have framed my concern differently.” That is the answer that says calibrated professional.
A Quick Pre-Interview Checklist
Ten minutes with this checklist the evening before an interview is usually the difference between a good story and a rehearsed-sounding one. Run down the list, tick each item off in your head, and stop rehearsing once you’ve done it once.
- Have 2 stories ready — one where the decision changed, one where it didn’t — so you can pick based on how the conversation is going.
- Screen both stories against your own filters: make sure neither one involves an HR issue, an ethics violation, or a conflict with a subordinate.
- Practice saying it out loud once, timed — aim for under 2 minutes. If you cross that, cut from the Situation and Task beats first, never from Action or Reflection.
- End with a genuine, specific reflection, not a generic lesson like “communication is important.” If your reflection could apply to any behavioural question, it’s too generic.
- If asked a follow-up you haven’t prepared for, it’s fine to pause and think for a few seconds before answering — a beat of visible thinking always beats a rushed non-answer.
Say each story out loud once to a friend or into a voice memo. If, on playback, you cringe at any line, that line is telling you something — usually that you’re editorialising about the other person or that your reflection sounds hollow. Fix that line and you have almost certainly fixed the story.
Summary & Key Takeaways
“Tell me about a time you disagreed with a decision” is one of the highest-leverage behavioural questions in a modern interview loop. Answered well, it demonstrates judgement, communication, and professional maturity in a single two-minute story. Answered badly, it quietly closes the door on offers that would otherwise have come through.
Key takeaways
- The question isn’t about the disagreement itself — it is a proxy for “will you be easy to work with when you don’t get your way?”
- The strongest answers focus on how you disagreed — respectfully, with evidence, at the right time, to the right person — not on being right.
- Use STAR + Reflection, keep the whole answer under two minutes, and never drop the reflection beat under time pressure.
- Choose a story that is professional (not personal), aimed up or sideways (not down), and one you didn’t automatically win.
- Prepare two stories — one where the decision changed, one where it didn’t — and pick based on which signal the interviewer seems to be probing for.
- Describe the other person generously. No villains, no clueless coworkers, no residual resentment.
- The “disagree and commit” half is the second half of the question — show you shifted cleanly from advocate to executor.
- Prepare one-line reflexes for the four common follow-ups, especially the “do you still think you were right?” trap.
Behavioural questions like this one are effectively an audition for your future colleagues. The interviewer is trying to imagine you sitting across the table from them the next time they hold a different opinion. If your story leaves them thinking “I’d want to be on that side of the table with this person,” you’ve answered the real question — not just the one on the sheet.
