This question has a trap built into it, and most candidates walk straight in. They choose a conflict where they were clearly in the right and the other person was clearly wrong, thinking that makes them look good. It does the opposite. It tells the interviewer that when you clash with someone, you file it under "they were being difficult", which is exactly the person they do not want on a team.
The uncomfortable truth is that a strong answer needs a conflict where the other person had a legitimate point, or at least a legitimate reason. That is harder to tell. It is also the only version that demonstrates the thing being tested, which is not "can you win an argument" but "can you disagree with someone and still work with them afterwards".
What they are checking for
Three things, and the third is the one people forget:
- Did you address it directly, or let it fester? Avoidance is a red flag. So is going over their head as a first move.
- Could you see their side? Even briefly, even while still disagreeing. A candidate who cannot articulate why the other person acted as they did looks rigid.
- What is the relationship like now? This is the real question hiding inside the question. A conflict that ended with a functional working relationship is a success. One that ended with someone leaving, or lasting resentment, is not, however "right" you were.
A worked example
"I was doing an internship in a small marketing team, and I clashed with a colleague who had been there for years over how we handled a client's social content. I wanted to move faster and post more reactively, and she kept slowing everything down with rounds of internal sign-off, which to me felt like bureaucracy.
It came to a head when I posted something without her checking it, thinking I was being proactive, and she was genuinely annoyed. My first instinct was to be defensive, because the post had done well. But I asked her, properly, why the sign-off mattered so much to her, rather than just assuming she was being cautious for its own sake.
It turned out the agency had been burned before by a post that went out with a factual error about a client's product, and it had nearly cost them the account. Her process was not bureaucracy, it was a scar. Once I understood that, it stopped being a fight about speed versus slowness.
We agreed a middle path: a fast lane for low-risk posts that I could publish directly, and full sign-off for anything making a claim about the product. That actually sped us up overall, because most posts were low risk. We got on fine after that, and she was a reference for me when the internship ended.
What I took away was that when someone insists on a process that seems pointless, it usually is not pointless to them, and asking why is faster than assuming."
Why it works
Notice the candidate is partly in the wrong. They posted without sign-off, which caused the flashpoint, and they own it plainly. That admission is what makes the rest believable. An answer where you are flawless throughout reads as fiction, because real conflict is rarely one-sided.
The turn happens when they ask a genuine question instead of defending themselves, and the answer reframes the whole disagreement. The colleague was not obstructive, she was protecting the business. Once that is clear, the resolution is not a compromise imposed on anyone, it is a better system that both of them prefer. And the closing detail, that she became a reference, is the proof point for "what is the relationship like now". It answers the hidden question without stating it.
The answers that fail
"They were just difficult." If the villain of your story is a stubborn, unreasonable colleague and you are the sensible one throughout, you have told the interviewer how you will describe them one day. It is the single most common way to fail this question.
Winning as the goal. Answers that end with "and eventually they agreed I was right" miss the point. The point is not victory. It is a working relationship on the other side.
Going nuclear too fast. If your resolution was escalating to a manager or HR as the first step, it suggests you cannot handle friction yourself. Escalation is sometimes right, but as a last resort, not an opening move, and the interviewer will read it that way.
No resolution at all. "We just avoided each other after that" is an honest answer and a failing one. If the only conflict you can think of ended badly, keep looking. Everyone has one that ended in a functional truce.
If your experience is mostly academic
Group projects are full of usable conflict: someone not pulling their weight, a genuine disagreement about direction, a clash of standards where one person wanted a pass and another wanted a first. The competency structure is identical to the workplace version. What matters is that you engaged with it directly and came out with the relationship intact.
The hardest part of this answer to get right is tone. Even with a good story, people slip into sounding bitter about the other person without realising it. Say it aloud and listen for warmth, or at least fairness, when you describe them. If you practise it and hear it back, you will catch the moment your voice turns cold, which is the moment an interviewer would too.