Guides · Common questions · 9 October 2026

Tell me about a conflict with a coworker: how to answer

Ask candidates about a conflict, and two kinds of stories come back.

The villain story:

"There was this guy, Rahul, who never did his share. Everyone knew it. I finally told our manager, and he got moved off the project."

The no-conflict story:

"Honestly, I get along with everyone. I can't think of a conflict."

The first makes the interviewer wonder what you'll say about them. The second sounds like you avoid hard conversations, or aren't being honest.

What is the interviewer really asking?

"Can you disagree with someone and still get good work done together?" Every team has friction. They want someone who handles it directly, fairly and without drama.

Choose the right conflict

• About work, not personality. Priorities, deadlines, approach, quality.
• With a resolution. Even if it was a compromise.
• Where the other person had a point. That's what makes you sound fair.
• Not with your current manager, ideally.

The structure

1. The disagreement: what each of you wanted and why. Be fair to them.
2. What you did: usually a direct conversation, listening, finding shared goals.
3. The outcome: what was decided and how it went.
4. What you learned, in one sentence.

Suggested answers

Priorities clash

"A designer and I disagreed about whether to delay a launch for a redesign. I wanted to ship; she was worried users would get confused. Instead of arguing in the channel, I asked for 20 minutes to go through her concerns. She was right about one screen, so we fixed that one and shipped the rest on time. I learned to ask 'what are you worried about?' before defending my plan."

Quality versus speed

"A senior engineer kept rejecting my pull requests over style, and I felt it was slowing the team. I asked if we could agree on a written style guide so reviews were about the code, not preferences. We wrote it together in an afternoon, and review time dropped noticeably. We still disagree sometimes, but now about real issues."

Workload

"On a group project, one teammate was missing deadlines. I asked to chat one-to-one rather than raising it in the group. It turned out she was covering for a sick colleague on another team. We rebalanced the tasks, and the project went out on time. I learned not to assume someone's not trying."

Customer-facing role

"A colleague in sales kept promising features we hadn't built. I set up a 10-minute weekly call to share what was actually coming. His promises got more accurate, and our support tickets about missing features dropped."

What should you avoid?

• Villains. If they're entirely bad, you sound like the problem.
• Escalating as your first move. Going to the manager should come after talking directly.
• No ending. Always reach an outcome.
• Gossip or names. Keep it professional.

Same skill, different question

This question shows up as "a disagreement with your manager", "a difficult colleague", or "a time you pushed back". Prepare one story and adjust it. It's closely related to how you talk about leaving a job: both test whether you stay fair about people.

Quick answers

What's a good conflict example for an interview?

A work disagreement about priorities, quality or deadlines, where you talked directly and reached a good outcome.

What if I've never had a conflict at work?

Use a smaller disagreement, or one from studies or volunteering. Saying you've never disagreed with anyone isn't convincing.

Should I say I went to my manager?

Only after trying to resolve it directly. Starting with escalation can look like you avoid hard conversations.

Can I talk about a conflict I didn't resolve well?

Yes, if you explain what you'd do differently. That shows self-awareness.

How long should my answer be?

About one to two minutes, covering the disagreement, your actions, the outcome and the lesson.