Conflict & disagreement
How to answer: “Tell me about a conflict with a coworker”
A collaboration test. Show you can disagree on substance, stay professional, and reach a durable resolution.
Why it is asked
What this question is really testing
Conflict questions are not looking for someone who has never disagreed; they are looking for someone who handles disagreement like a professional. The interviewer wants to see that you separate the person from the problem, that you seek to understand before you push your view, and that you can land on a resolution that holds rather than a truce that resents.
Pick a real, substantive disagreement (a technical direction, a priority call, an approach to a project) rather than a personality clash. Describe your counterpart's position fairly, which itself signals maturity, then walk through how you moved from disagreement to a shared decision. The resolution matters: a strong answer ends with a better outcome and an intact relationship.
Avoid stories where you simply won or where you caved. The best answers show a third path: new information, a compromise, or a small experiment that settled the question with data instead of opinion.
The signal
What interviewers listen for
- You describe the other person's view fairly, not as a strawman.
- Focus on the problem and the work, never personal attacks.
- Active steps to understand before pushing your own position.
- A durable resolution and a preserved working relationship.
Worked example
A STAR answer you can adapt
Scenario: Engineers split on a build-versus-buy call. Read it for the shape, then swap in your own story.
Situation
A senior teammate and I disagreed hard on whether to build our own queueing layer or adopt a managed service.
Task
We were blocking the roadmap and both digging in.
Action
Instead of escalating, I asked to spend a day writing down both options with the same criteria: cost, on-call load, and time to ship. I steelmanned his build case in the doc, which lowered the temperature, and we walked through it together.
Result
Seeing the on-call cost side by side, he agreed the managed service was right for now, and we wrote down the conditions under which we would revisit building. We shipped on time and have collaborated well since, because the disagreement was about the work, not about us.
Answer skeleton
Fill-in-the-blank template
We disagreed on [substantive issue]. I made sure I understood their view by [step], then [how you moved it forward, e.g. a doc or prototype]. We landed on [resolution] and [the relationship stayed intact].
Avoid these
Common mistakes
- Choosing a petty or personality-based conflict.
- Painting yourself as entirely right and the other person as the problem.
- Ending with no resolution, or a resolution where you simply gave in.
- Bad-mouthing the colleague, which makes the interviewer worry about you.
By role
How the answer shifts by role
Engineering
Technical disagreements resolved with a doc, a prototype, or data are ideal. Show you let evidence decide.
Product management
A priority conflict with engineering or design works if you show how you aligned on the user outcome.
Engineering management
A disagreement between two reports, or with a peer manager, lets you show you can mediate without taking sides.
Be ready for
Likely follow-up questions
- What would you have done if they still disagreed afterward?
- How is your relationship with that person now?
- Tell me about a time you were the one who was wrong.
Last reviewed by the site editor: June 2026
Nearby topics
Questions that often follow this one
Interviewers rarely stop at one story. These prompts sit close to this one and reward the same preparation.
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.