Interview questions

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

Every team has disagreements, and the interviewer knows it. What they can't tell from your resume is how you behave in one. This question is how they find out.

What the interviewer is really asking

Will you be easy to work with? They're listening for whether you stay calm, listen and look for a fix, or dig in and make it personal.

Can you disagree about the work without falling out with the person? The best answers are about a decision or a process, not someone's personality.

Do you see your own part? Saying what you'd do differently tells them more than a story where you were right all along.

The structure: STAR, ending on how it was resolved

Situation. The project and what you disagreed about, in a sentence or two. Keep it about the work.
Task. Why it mattered to you and what you needed to get done.
Action. What you did to sort it out: talking one on one, asking about their side, finding the shared goal. This is the core of the answer.
Result. How it ended, how you work with that person now, and what you took from it.

Aim for 60 to 90 seconds out loud, roughly 150 to 200 words. Keep the disagreement brief and spend most of the time on how you handled it.

An example answer

A marketing specialist who disagreed with a colleague about a campaign deadline. Everything in brackets is a fact from your own story.

On [a project] at [company], a colleague on [their team] and I disagreed about [what you disagreed on].

I thought [your view], and they wanted [their view].

After a couple of tense threads, I asked if we could talk it through one on one instead.

I started by asking what they were worried about,

and it turned out [the concern you hadn't seen].

Once I understood that, we agreed to [the compromise you reached],

and the result was [an outcome you can back up].

Looking back, I'd have suggested that conversation a week earlier.

Now when I disagree with someone, I talk to them before I write another long message.

Why it works

The conflict is about the work, not about a difficult person, so nobody comes off as the villain.
Most of the answer is what they did to fix it, which is what the question is testing.
They listened first and found something they had missed, which shows they can change their mind.
They name what they'd do sooner next time, so it doesn't sound like they think they were perfect.

Write your own answer

Paste in your role and a few real facts, and the free answer generator builds this answer around them. It won't invent your numbers: anything only you know comes back in brackets.

Write my answer, free

Adjusting it to where you are

Recent graduate. A group project, a part-time job or an internship all count. A teammate who wasn't pulling their weight works if the story is how you raised it and what changed, not how annoying they were.

Manager. A disagreement with a peer or your own manager often works better than one with someone you managed, because the power is equal and you had to persuade, not decide.

Technical role. A disagreement over an approach, a code review or a deadline is ideal. Explain both options in a line each so it doesn't turn into a technical lecture.

Common mistakes

Saying you've never had a conflict. It sounds either untrue or like you avoid hard conversations. A small, ordinary disagreement is fine.
Making the coworker the villain. However bad they were, a story about someone else's flaws makes the interviewer wonder what that person would say about you.
A story about who won. The point is how you reached an outcome, not that you were right. An answer that ends with "and they admitted I was right" misses it.
Picking a personal clash. Arguments about personalities, gossip or anything outside the work are hard to tell without sounding petty. Stick to a disagreement about the work.
Going straight to your manager. Escalating can be the right call, but if it was your first move, the story says you can't sort things out yourself.
Leaving it unresolved. Pick a conflict that has a clear ending. A story that's still going raises more questions than it answers.

The question you didn't practice

Practicing the common questions helps. The hard part is the one you didn't see coming, asked live while someone waits for you to think. InterviewWhisperer is a Mac app that hears the interviewer and puts an answer like the one above on your screen while you talk, built from your resume and the job description. Your first 30 minutes of live answers are free, no card.

Try it free on your Mac See pricing

Questions people ask

What kind of conflict should I talk about? A disagreement about the work, like priorities, an approach or a deadline, that you helped resolve. Avoid personal clashes and anything involving harassment or ethics, which belong in a different conversation.

Should I use the STAR method? Yes. Situation, task, action, result keeps it short. Spend the least time on the situation and the most on the action, because how you handled it is what they're asking about.

Can I use a conflict with my manager? Yes, if you disagreed respectfully and the outcome was good for the work. It shows you can push back without damaging the relationship.

Is "tell me about a time you disagreed with someone" the same question? Yes, and so is "tell me about a difficult coworker". The same structure works for all of them.

Should I name the coworker or the company? No need. "A colleague on the sales team" is enough, and leaving names out keeps the story about what happened rather than who.