How to Answer 'Describe a Conflict With a Coworker'

"Describe a conflict with a coworker" catches people off guard more than it should, because a good answer means admitting something went wrong at work and then explaining, to a stranger, how you handled it. Some candidates freeze and reach for something too minor to count as a real conflict, a disagreement about which coffee machine to buy. Others swing the other way and turn the story into a grievance session about a colleague who wronged them. Neither approach tells the interviewer what they're actually trying to find out.

Why Interviewers Ask This Question

Nobody's looking for proof that you've never clashed with a colleague, and claiming that would work against you anyway. What the interviewer wants to see is three things at once: whether you can recognise your own part in a disagreement, whether you can describe the other person's position without contempt, and whether you actually resolved something rather than just outlasted it or had a manager step in and fix it for you. A team that avoids conflict quietly builds resentment under the surface, and a team that handles conflict badly loses good people over things that should have been a five-minute conversation. Interviewers are hiring for the ability to disagree with someone and still work with them afterward, which matters far more than simply appearing to get along with everyone.

Choosing the Right Story

The best answer to this question is real, specific, and small enough to have been fully resolved by the time you tell it. Good source material: a disagreement over how to split work on a shared project, a difference of opinion on the right approach to a task, friction caused by different working styles or communication habits, or a moment where you and a colleague read a client's priorities differently. Avoid anything involving HR, a formal complaint, a manager who had to intervene, or a relationship that stayed damaged afterward: these signal a conflict that outgrew you, not one you managed. Keep the other person anonymous by role rather than name ("a colleague on the design team", not naming them), and describe their reasoning fairly even where you didn't agree with it. If your internal version of the story still makes them sound unreasonable or difficult, it's the wrong story to tell in an interview, whatever actually happened.

Structuring Your Answer With STAR

STAR (Situation, Task, Action, Result) works for this question the same way it works for any behavioural question, but the weighting matters more here than usual. Keep the Situation and Task brief: a sentence or two is enough to set up what the disagreement was about and why it mattered. Spend most of your answer on the Action, specifically what you said, how you approached the conversation, and what you did to move things toward a resolution rather than just waiting for it to blow over. The Result should cover both the practical outcome (the project shipped, the process changed, the decision got made) and, where it's true, what happened to the working relationship afterward. An answer that ends with "and we still work well together" or "we ended up collaborating on two more projects after that" lands better than one that stops at the decision itself.

What Not to Say

Three answers reliably undermine this question. The first is blaming the other person entirely, painting yourself as the reasonable one and them as the problem: even if that's actually closer to what happened, it reads as a lack of self-awareness rather than honesty. The second is claiming you've never really had a conflict with a colleague, which interviewers hear often enough to recognise as evasion, not a spotless record. The third is oversharing, turning a professional disagreement into a story about someone's personal conduct, a grudge that's still live, or a situation involving other people's private business that has no place in an interview room. If you find yourself needing to explain a lot of background just to make yourself look reasonable, that's usually a sign the story is too complicated or too raw for this question, and it's worth picking a different one.

A Worked Example Structure

A strong answer might run something like this. Situation and Task: "I was working with a colleague on a client proposal, and we disagreed about which approach to lead with, mine focused on cost savings, theirs on speed to implementation." Action: "I asked them to walk me through why speed mattered so much to them, which turned out to be based on a conversation they'd had directly with the client that I hadn't been part of. Once I understood that, I suggested we combine both angles rather than picking one, and we split the proposal so each of us wrote the section we felt strongest on." Result: "The client responded well to having both points covered, we got the work, and it became our default way of dividing proposals afterward." Notice how little of this is about who was right: the emphasis sits on listening, understanding the other person's reasoning, and finding a way forward together.

Handling the Follow-Up: What Would You Do Differently

Almost every version of this question is followed by some version of "what would you do differently" or "how would you handle it if it happened again", and candidates who haven't prepared for it tend to either repeat their answer with no new content or invent a flaw that sounds rehearsed. Prepare a genuine reflection in advance: perhaps you'd have raised the disagreement earlier instead of letting it sit for a week, or asked a clarifying question sooner instead of assuming you already understood the other person's reasoning. The goal is to show that you keep learning from how you work with people, rather than to manufacture a flaw for its own sake, and that's exactly the trait the original question was trying to uncover.