Interview Question · Behavioral

How to Answer “Tell me about a conflict with a coworker”

Q: Tell me about a conflict with a coworker

STAR, with the temperature down: Frame it as a disagreement about the work — Pick a conflict over priorities, methods, or ownership — not a personality clash — and describe the other person neutrally. Show that you went direct — The key action interviewers listen for: you talked to the person, privately and early, instead of escalating or simmering. Show that you listened — Include the moment you understood their side. A resolution where you were simply right teaches them nothing about you. End with the working relationship — The result isn't just the resolved issue — it's that you could work together afterward, ideally better than before.

Why they ask it

Every team has friction, so the interviewer isn't looking for someone who's never had a conflict — that answer reads as either dishonest or untested. They're watching how you talk about the other person, whether you went direct or went political, and whether the relationship survived. How you tell this story is how they'll assume you handle their team.

How to answer it

STAR, with the temperature down

1
Frame it as a disagreement about the work. Pick a conflict over priorities, methods, or ownership — not a personality clash — and describe the other person neutrally.
2
Show that you went direct. The key action interviewers listen for: you talked to the person, privately and early, instead of escalating or simmering.
3
Show that you listened. Include the moment you understood their side. A resolution where you were simply right teaches them nothing about you.
4
End with the working relationship. The result isn't just the resolved issue — it's that you could work together afterward, ideally better than before.

Example answers

Sample answers to steal the structure from — swap in your own stories, never someone else's.

Sample answer 1 · Early-career, team project

In my first year at my previous company, another coordinator and I shared responsibility for event logistics, and we kept stepping on each other — I'd confirm a vendor she'd already renegotiated, she'd change a layout I'd finalized. It came to a head when a double-booking embarrassed us both in front of our manager, and honestly, at that point we were barely speaking.

I asked her to grab coffee and opened by owning my half: I'd been treating the shared checklist as mine. It turned out she'd read my constant confirmations as me not trusting her work, which wasn't how I'd meant them at all. The actual problem was that nobody had ever split the ownership clearly.

We divided the checklist by vendor category, set a fifteen-minute Monday sync, and the overlap problems stopped. By the next event season we requested to be paired together — the sync habit we invented ended up being adopted by the whole team.

Sample answer 2 · Experienced professional, cross-team conflict

At my previous company, I ran implementation and a colleague ran sales engineering, and we had a running conflict over handoffs: deals arrived with commitments my team couldn't deliver on schedule, my team's complaints made his team look dishonest, and both of us were escalating to our managers instead of talking.

After one particularly bad handoff, I asked him for an hour, one on one, no managers. I came in with a genuine question instead of a case file: what pressure was driving the commitments? His answer reframed the whole thing — his team was quoting from a capabilities document mine had written two years earlier and never updated. Half the problem was ours.

We rebuilt the document together and added a fifteen-minute pre-commitment check for any nonstandard deal. Handoff escalations basically disappeared, and he became one of my closest working partners there. The lesson I carry: most cross-team conflict is a stale interface, not a bad actor.

Common mistakes

✕
Trashing the other person. The moment your story needs a villain, you've lost. The interviewer identifies with the absent coworker, not with you.
✕
Claiming you've never had one. It doesn't read as easygoing — it reads as avoidant, oblivious, or too green for the role.
✕
A story where you were purely right. If the resolution is “they eventually saw it my way,” you've shown stubbornness winning, not conflict skill.
✕
Escalating first. A story that starts with going to your manager signals you can't resolve friction yourself. Going direct is the behavior they're hiring for.

Reading about it only gets you so far.

The candidates who nail “Tell me about a conflict with a coworker” have said their answer out loud before the interview. Practice it in a free mock interview and get coaching on the answer you actually gave.

Start Free Mock Interview

Keep going