In this article
Before you start
Why interviewers ask this
A conflict question is a window onto how you behave when someone disagrees with you, and the answer you give shows that behaviour more directly than a claim about being a team player. A behavioural question is a question that asks about what you did in a past situation. Google's guide to structured interviewing describes them as asking candidates to describe prior achievements and match them to the job, and says they are good at revealing patterns of behaviour (Google re:Work, March 2026).
Google also says it often documents what a poor, borderline, solid and outstanding answer would cover, so your story is graded against a scale, not a feeling. A weak answer says there was never a conflict or casts the other person as the problem. A strong answer lets the interviewer watch you listen. The behavioral interviews hub places this question among the others in the round.
How to answer a conflict question from first principles
- Conflict mode
- A conflict mode is one of five ways of behaving in a disagreement, competing, accommodating, avoiding, collaborating or compromising, placed by how far you try to satisfy your own concerns and the other person's. Everyone uses all five, depending on the situation, so a mode describes what you did in one story, not what kind of person you are.
- Position
- A position is the specific outcome a person says they want in a disagreement, such as "ship it this week", which may hide the reason they want it.
In plain words
Telling a conflict story is like reporting how you settled a clash over a road map. You do not say who was right. You say where each of you was heading, and why. Then you say which route you took together. The analogy breaks in one place. A map has one true route. A workplace disagreement often has several fair ones. So the interviewer scores how you chose.
Said precisely, the answer is one disagreement about the work. It shows the other person's interest. It names your action. It ends on a change. Speaking pace is easy to check. A story of about 90 words takes about 33 seconds. That uses the 164 words per minute that a study of 2,438 telephone conversations found as the turn-wise speaking rate (Yuan, Liberman and Cieri, 2006).1
Step 1: Pick a real disagreement about the work
The first step is choosing a story where the disagreement was about a decision, not about a person. The input is your list of work stories; the output is one disagreement with a real cost to one side or both. Harvard's Program on Negotiation lists "separate the people from the problem" as the first principle of the method in Getting to Yes (Program on Negotiation, read 2026-10-24), and a story framed that way gives the interviewer nothing to dislike.
Pick one with stakes: a deadline, a design choice, a priority call. It need not be heated. Avoid a disagreement you won easily, since there is little to learn from it, and avoid a story about a personality clash with no decision in it.
Step 2: Show how you understood the other side
The second step is the step that is easiest to leave out. The input is the other person's stated position; the output is their interest, the reason behind it, found by asking. The same Harvard page lists "focus on interests, not positions" as the second principle (Program on Negotiation, read 2026-10-24).
In the sample answer below, the position was "ship it this week" and the interest was a customer demo on Friday that the candidate had not known about. Say the sentence in the first person: "I asked what worried them, and learned that..." Without that sentence the interviewer cannot tell whether you listened or merely prevailed. What you now know: understanding is a sentence you say, not a feeling you have.
Step 3: Say what you did, in the first person
The third step names your action. The input is the interest you found; the output is what you did about it, not what the team did. The Thomas-Kilmann model describes five modes, competing, accommodating, avoiding, collaborating and compromising, each placed by how much a person pursues their own concerns and the other person's (Kilmann Diagnostics). Use that vocabulary to check your story, as the table shows: if every sentence is competing, there is no understanding to score, and if every sentence is avoiding, there is no decision. A strong action is specific and bounded, such as an agreed plan with a date. Say "I" for your part and "we" for the agreement.
Text description of the diagram
- The five modes are competing, accommodating, avoiding, collaborating and compromising.
- A story that is all one mode gives the interviewer little to score.
Step 4: Report what changed, and what the other person would say
The fourth step ends the story on the result and on a lasting change. The input is the outcome; the output is two things: what happened, and what you do differently now. Stopping at "it worked out" leaves the point unscored. The strongest answers add a change in practice, such as asking about the other side's deadline first, and show that the relationship survived by saying what the other person would report. Interviewers often ask that very question next, so answer it before they do. Then stop speaking. What you now know: a closed story invites the next question rather than a defence.
Step-by-step description
- Choose a real disagreement about the work.
- Show you asked for their reason.
- Say what you did, in the first person.
- Report what changed afterwards.
- A conflict answer has four moves: the disagreement, the understanding, the action and the change.
- The answer ends on what changed and what the other person would say.
Two sample answers side by side
Both samples are illustrative composites written for this page: no real person and no named company, and every detail is made up. The weak answer is 39 words, about 14 seconds. The strong answer is 90 words, about 33 seconds.1
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
A Staff-level answer works at the level of the system around the disagreement, owns an early wrong assumption, and leaves behind a mechanism, not only a resolution. It is still under a minute, about 48 seconds.
Tell me about a time you had a conflict with a colleague or another team.
Our team and a platform team disagreed about when to remove an old interface that both of us depended on. I had assumed they were stalling, so I asked for thirty minutes and listened first, and learned that my date collided with a hard migration deadline of theirs. We agreed on one criterion, no customer-facing breakage, and on a dated plan: they kept the old interface for six more weeks and my team moved its calls in the first two.
The migration finished on the new date, and their lead told me the dated plan was what let them agree. I wrote the plan into a one-page contract both teams signed off, so the next change needs no meeting, and I now ask for the other side's deadline before I propose mine.
What makes it Staff-level: it admits the wrong assumption, it finds the interest, and it ends on a contract that changes how two teams work. It runs 132 words, about 48 seconds, and 32 of them describe the lasting change, against 10 in the strong sample. By part, the strong sample uses 24 words on the situation, 24 on understanding, 20 on action, 12 on the result and 10 on change, and the Staff sample uses 20, 28, 32, 20 and 32 words on the same five parts.1
Text description of the diagram
- The strong sample uses 24 words on the situation, 24 on understanding, 20 on action, 12 on the result and 10 on change.
- The Staff sample uses 20, 28, 32, 20 and 32 words on the same five parts.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Choice of story | No conflict, or a personality clash | A real disagreement about work | A disagreement across teams or with stakes for the business |
| Understanding | The other person was wrong | Asked for their reason | Owns a wrong assumption, then finds their interest |
| Action | Argued until they agreed | A specific, agreed step | A shared criterion and a dated plan |
| Result | "It worked out" | A named outcome | An outcome plus the other side's view |
| Ending | Stops at the result | A changed habit | A mechanism others can reuse |
Three variants of this question
"Describe a disagreement where you turned out to be wrong."
Use the same four moves, with the wrong assumption as the centre. Say what you believed, what showed it was wrong, and what you changed. The interviewer is checking that you can update without defending yourself, so keep the admission to one plain sentence.
"How do you handle conflict with someone who will not respond?"
Treat silence as a position with an interest behind it. Say what you tried, such as a direct message, then a short call, then a written summary to both parties, and where you stopped and involved a manager. Name the point at which you chose to escalate, and why.
"How would you resolve a conflict between two people on your team?"
The manager's version of the question puts you in the third-party seat. Speak to each person alone first, find each interest, agree one criterion, and decide if they cannot. See the stakeholder management guide for engineering managers and the engineering management hub for the longer treatment.
Common mistakes
Saying there was never a conflict. (wrong) "I get along with everyone." (right) "The disagreement I remember best was about a release date." It gives the interviewer no behaviour to score, and it reads as unaware or avoidant.
Making the other person the villain. (wrong) "He was being difficult." (right) "He had a reason I had not asked about."
Skipping the understanding. (wrong) "I explained why I was right." (right) "I asked what worried them first."
Stopping at the result. (wrong) "And it worked out fine." (right) "Since then I ask about deadlines first." Pair this with a story that has stakes, as in driving a big cross-team change.
Follow-up questions
How do you handle conflict with a colleague?
Say the method in one sentence before the story: understand their interest, agree a shared criterion, then act on a dated step. The method is what the interviewer remembers, and the story proves it. The wider set of story prompts is in the STAR method guide.
What would the other person say about it?
The other person would describe the same disagreement as being about their deadline or their risk, and say you listened. Answer in their words, and name one thing they would say you did badly, such as moving slowly at first.
Did you escalate to your manager, and why or why not?
Say what you tried first and what made escalation the right step, or why it was not needed. Both are good answers; an automatic escalation or an automatic refusal to escalate are not.
Has the same conflict happened again?
Answer with the change from Step 4: if you fixed the mechanism, the same disagreement stops arriving, and if it recurs you can say what you are still adjusting.
What if you have never had a conflict at work?
Use a small, honest disagreement, such as a priority call or a design choice, because the interviewer wants the pattern of how you respond. Related prompts include greatest weakness and tell me about yourself, and the interview loop overview shows where they fall.
- Pick a real disagreement about the work, not about a person.
- Say the sentence that shows you asked for their reason.
- Name your action in the first person and end on what changed.
- About 90 to 140 words, which is under 52 seconds at 164 words per minute.
Sources
- A guide to structured interviewing for better hiring practices — Google re:Work, 1 Mar 2026
- A brief overview of the Thomas-Kilmann Conflict Mode Instrument (TKI) — Kilmann Diagnostics (Thomas and Kilmann, the instrument's authors), 9 Aug 2015
- Getting to YES: Negotiating Agreement Without Giving In — Harvard Program on Negotiation (date = read date), 24 Oct 2026
- Towards an Integrated Understanding of Speaking Rate in Conversation — Interspeech 2006 (Yuan, Liberman, Cieri; University of Pennsylvania), 17 Sep 2006
