What they're really testing
Risk, not curiosityDisagreement is normal on any good team; what matters is how you handle it. This question tests whether you can hold a different view without it becoming personal, whether you try to understand the other side rather than just win, and whether you can land on a resolution and move forward. For senior roles it also tests whether you can disagree with authority and then commit. The story you choose and the way you tell it reveal all of that, often more than the conflict itself does.
- Alarm · no conflicts"I don't really have conflicts" reads as avoidance or as no self-awareness. Neither is the answer they want.
- Alarm · the villainMaking the other person the problem tells the interviewer how you'll talk about them one day.
- Alarm · the steamroller"I was right, so I overrode them." Winning is not the signal, and this says you don't collaborate.
- Alarm · no endingA conflict with no resolution leaves them wondering how it closed, and whether you can close one.
The shape of a strong answer
STAR, weighted to the actionUse STAR and put the weight on how you handled it. Situation and task: brief and neutral, the disagreement and what was at stake, without painting the other person badly. Action: how you engaged, meaning you heard their view, surfaced the real interest or the data, and looked for common ground rather than a win. Result: how it resolved, and that the working relationship survived. A short line on what you learned makes it stronger.
Fill this in
“[Person and I] disagreed on [the decision]. Rather than pushing my view, I [how you engaged: asked, listened, brought data]. We landed on [the resolution], and [what happened to the relationship after].”
Worked through: “A staff engineer and I disagreed on whether to rewrite a service or refactor it. I thought a rewrite was overkill on the timeline. Instead of pushing my view, I asked him to walk me through the failure modes he was worried about, and two of them turned out to be real. We scoped a partial rewrite of just those paths. It shipped on time, and he's the person I go to first on design calls now.”
The hard cases, answered honestly
Where it gets stressfulThe clean story is a technical disagreement with a peer that resolved well. Most real conflicts aren't that tidy. Here's how to tell the ones that aren't.
It was with your manager
Move · disagree, then commitThis is the strongest version of the story if you tell it right: you raised it properly, they decided, you got behind it. Seniority interviews are specifically looking for that second half.
The other person was genuinely unreasonable
Move · describe behaviour, not characterSay what happened in neutral, factual terms and let the interviewer draw their own conclusion. The moment you supply the adjective, the story becomes about your judgment of people.
You lost the argument
Move · say what changed your mindBeing persuaded is a good outcome to describe, not a weak one. It shows you were arguing about the decision rather than defending a position.
It never really resolved
Move · resolve the working relationshipNot every disagreement ends in agreement. Show that you landed a working arrangement even without consensus: an escalation, a trial, a decision owner. That still counts as closing it.
You genuinely avoid conflict
Move · find the low-stakes oneYou've disagreed about something: a code review, a deadline, a scope call. A small disagreement handled well is a real answer; "I don't have conflicts" is not.
What's your greatest weakness? →It was cross-team and political
Move · keep it about the interestsDescribe the competing priorities rather than the org politics. Politics stories are hard to tell without a villain, and the interviewer can't verify any of it.
Listen for the villain. Most people stay generous about the other person on paper and lose it somewhere in the retelling.
Score my answer →What not to say
The short blacklist- Don't claim you have no conflicts. It reads as avoidance, which is the thing being screened for.
- Don't make them the villain. It tells the panel how you'd describe them later.
- Don't describe overriding someone. Winning by authority answers the opposite of what was asked.
- Don't make it personal when the real disagreement was about the work. Keep it on the decision.
- Don't leave it open. Without an ending, they can't tell whether you close things out.
Rehearse it out loud before it's live
Saying it is the testThis is the answer most likely to drift when it's spoken. The written version stays fair about the other person; the spoken one, twenty seconds in, starts explaining why they were wrong. Say yours below and Calibrd will score it on engagement, professionalism and resolution. The method for building the whole story bank is in how to prepare for interview questions.
Answer out loud · free · nothing to sign up for
“Tell me about a conflict”
Disagreeing well, out loud
Tell it without making anyone the villain.
Paste any real job and Calibrd shows you the questions that company and level asks, then lets you rehearse out loud: record, get transcribed, and have your answer calibrated against the bar. Any role. Free to start.
Free to start · No credit card · Your CV stays on your device