How to Answer "Tell Me About a Time You Had a Conflict With a Coworker"

This question makes a lot of people nervous, because it feels like a trap — say the wrong thing and you sound difficult to work with; say nothing meaningful and you sound like you're dodging. Here's how to actually handle it.

Why interviewers ask this

Conflict happens on every team, so interviewers usually aren't looking for someone who's never had one — they're looking at how you handle disagreement. Do you stay professional? Can you see another person's perspective? Do you resolve things directly, or let them fester? This question is really about communication style and emotional maturity under friction, not about who was "right."

The structure that works

Same STAR foundation as any behavioural question — Situation, Task, Action, Result — but for conflict stories, the Action step is where you need to be most specific. Vague answers ("we talked it out and figured it out") don't show anything. Specific answers show exactly how you approached the person and what you actually said or did.

A good conflict story usually shows three things: you addressed it directly rather than avoiding it or escalating it immediately, you tried to understand the other person's side, and the outcome was a resolution — not just an ending.

Example answers

Disagreement over approach: "A coworker and I disagreed on how to structure a shared project — I wanted to split tasks by feature, they wanted to split by role. Rather than pushing my view in the group chat, I asked to talk it through one-on-one first. It turned out they were worried about accountability gaps with my approach, which was a fair concern I hadn't fully considered. We ended up combining both ideas — feature ownership with clear role check-ins — and it worked better than either original plan."

Personality clash: "I worked with someone whose communication style was much more blunt than mine, and early on I took some of their feedback more personally than intended. Instead of letting it build up, I brought it up directly and asked if we could agree on how we gave each other feedback going forward. It turned into a good working relationship — we just needed to name the style difference out loud."

Conflict over credit or ownership: "A teammate and I both felt we'd led a project that ended up going well, and it created some tension in a review meeting. I asked to talk privately afterward rather than litigating it in front of others. We realised we'd both genuinely contributed in different, overlapping ways, and going forward we started documenting who owned what earlier in projects to avoid the ambiguity."

Each of these shows a direct, low-drama approach: address it privately, understand the other side, land on an actual resolution — not just "and then it was fine."

Common mistakes to avoid

• Throwing the other person under the bus. Even if they were clearly in the wrong, focus on how you handled your side of it, not on making them look bad.
• Picking a conflict that's too minor to say anything. "We disagreed about which font to use" doesn't give the interviewer anything to evaluate.
• No resolution. If the story ends with the conflict just fading away rather than being addressed, it doesn't demonstrate the skill they're testing for.
• Sounding rehearsed or overly diplomatic. A story with zero tension in it can come across as insincere. It's fine to admit the moment was uncomfortable.

Practice it out loud

Conflict stories are one of the easiest to either underplay or overplay when you're nervous in the room. If you want to hear how your version actually sounds, the Interview Practice Lab has a free 3-question mock interview that gives you structured feedback — no signup required.