How to Answer 'Tell Me About a Conflict With a Coworker'
Why This Question Trips People Up
The conflict with coworker interview question makes candidates uncomfortable because it feels like a trap: share a real conflict and risk sounding difficult; dodge it and look dishonest. Neither approach works.
The interviewer isn't looking for drama. They're looking for evidence that you can navigate interpersonal friction professionally — without escalating it, avoiding it, or pretending it never happens. The ability to resolve conflict is a baseline professional skill. Saying "I get along with everyone" doesn't prove you have it.
What Makes a Good Conflict Story
Not every disagreement is interview-worthy. A strong story has these elements:
The conflict was about work, not personality. Disputes over approach, priorities, deadlines, or standards are fair game. "I didn't like his attitude" is not a story — it's a complaint.
You played an active role in resolving it. The interviewer wants to see what you did. Not that HR stepped in, not that your manager fixed it, not that the other person eventually came around. You took a step.
The outcome was constructive. It doesn't need to be perfect. It needs to show that the relationship or the work improved.
It's recent. A conflict from your first job fifteen years ago tells them nothing about how you'd behave on their team.
The Structure: Conflict → Your Move → Resolution
Don't force STAR rigidly here — this question has a specific emotional arc. Try this instead:
- Set the conflict clearly — What was the disagreement and why did it matter for the work?
- Show your thinking — What made it difficult? What did you consider before acting?
- Describe your specific action — What did you say or do, and how?
- Land the result — What changed? What did you both walk away with?
Bad Answer
"I had a conflict with a coworker who wasn't pulling their weight on a shared project. It was really frustrating. I eventually talked to my manager about it and things got better."
This escalates immediately to management (passive), signals the coworker as the villain (unfair), and gives no detail on what the candidate actually did.
Good Answer
"I was co-leading a feature rollout with a colleague from a different team. We kept disagreeing about timelines — she wanted to ship faster than I thought was safe given the QA coverage. It wasn't personal, but the tension was slowing us down.
I asked for a one-on-one and came prepared: I laid out specifically which test cases we'd be skipping if we hit her timeline and what the estimated defect risk was. I also acknowledged that her deadline pressure was real — her team had a hard customer commitment. We ended up agreeing to ship a reduced scope on her date, with the remaining functionality following two weeks later. Both sides got something, and we actually built a better working relationship from that conversation because we'd cleared the air directly."
The candidate owns a clear action (requested a 1:1, came prepared), acknowledges the other person's legitimate concern, and shows a concrete resolution.
What to Avoid
Blaming the other person. Even if they were objectively wrong, framing them as the problem makes you look like someone who deflects. Own your part of the friction, even if it was just "I could have raised this earlier."
Picking a conflict with a manager. That's a separate question and a separate dynamic — don't conflate them.
Vague resolutions. "It worked out" or "we moved past it" isn't a result. Say what actually changed — in the work, the process, or the relationship.
Over-dramatizing. You don't need a high-stakes crisis. A genuine professional disagreement handled well is more compelling than a fabricated disaster.
How to Prep This Answer Before the Interview
Pull up your last three roles. For each one, ask:
- Was there someone I regularly found difficult to work with?
- Was there a project where I disagreed with a colleague on approach?
- Was there a moment where friction between two people affected the team's output?
Pick the story where your role in the resolution is clearest. Write it down. Time yourself — you want 90–120 seconds, not four minutes. If you're still explaining context at the one-minute mark, you've buried the lead.
Practice This Now
Answering conflict questions out loud feels very different from writing them down. Tone matters — the same story sounds composed or defensive depending on how you say it.