Tell Me About a Conflict With a Coworker: Answers
How to answer the coworker conflict interview question without sounding difficult, with a scoring framework and two full example answers.
You hear “tell me about a time you had a conflict with a coworker” and your first instinct is to protect yourself: either claim you’ve never really had one, or reach for the mildest possible disagreement so nothing you say could make you look difficult. Both instincts are understandable and both make for a weak answer.
Interviewers aren’t asking this to catch you out or to find a reason to worry. They’re asking because conflict is inevitable on any team, and they want to know whether you handle it directly and professionally or whether it turns into something messier, avoidance, escalation, or a grudge that outlasts the disagreement. A well-told real conflict story is one of the more reassuring answers you can give.
The strongest answer to this conflict interview question names a real, specific disagreement about work, not a personality clash, describes the other person’s position fairly before your own, and spends most of the answer on how you resolved it directly. Close on the state of the relationship afterward. The goal isn’t to win the story. It’s to show you handle friction like a professional.
Why this question worries people more than it should
Most candidates over-index on the risk that any conflict story makes them look combative. That fear pushes people toward one of two bad answers: the fake non-answer (“I don’t really have conflicts, I just try to get along with everyone”), which reads as either dishonest or conflict-avoidant, or an overly sanitized story with no real tension in it, which answers nothing.
The actual risk isn’t mentioning a conflict. It’s telling a conflict story where you come across as unreasonable, unable to see the other side, or someone who let a work disagreement become personal. Avoid those three things and a real conflict story is safe territory, not a trap.
How to pick the right coworker conflict story
Look for a disagreement that meets three conditions.
- It’s about the work, not the person. A disagreement over how to approach a project, which feature to prioritize, or how to handle a shared deadline. Not a story about someone’s personality, habits, or a clash that was really about likability.
- You can describe the other person fairly. If you can’t say one honest, non-sarcastic sentence about why they saw it their way, the story is too one-sided for an interview. The best conflict stories make the other person sound reasonable, which is what makes your resolution sound skillful rather than lucky.
- It resolved, and the relationship survived. Interviewers want the ending to be a working relationship that continued normally, or even improved, afterward. A story that ends with ongoing tension or someone getting in trouble undercuts the point.
A framework for structuring the answer
Use a version of STAR weighted toward the resolution, similar to how you’d handle a failure question, but with one added step: representing the other side fairly before you explain your own position.
- Situation, one to two sentences. What you were both working on and how your views diverged.
- Both positions, two to three sentences. State your coworker’s reasoning fairly first, then your own. This single move does more to make you look mature than almost anything else in the answer.
- How you resolved it, three to four sentences. What you actually did: asked to talk directly, proposed a way to test both approaches, brought in a third opinion, whatever really happened. This should be the longest part of the answer.
- The outcome and the relationship after, one to two sentences. What got decided, and importantly, how you two worked together afterward.
Two full example answers
Example one, a disagreement over approach with a peer:
“A colleague and I disagreed about how to roll out a new process to the rest of the team. She wanted to introduce it all at once with a single training session, since she was worried a phased rollout would create confusion about which version people were using. I wanted to phase it in with one team first, because I was worried a single big change would overwhelm people and generate resistance. We were both trying to avoid a real risk, just different ones. I asked her to grab fifteen minutes so we could talk it through directly instead of going back and forth over messages. We ended up combining both ideas: one team piloted it for two weeks, we fixed the two issues that came up, and then rolled it out to everyone at once with those fixes already in place. It ended up smoother than either of our original plans, and we’ve partnered on two projects since without any friction.”
Example two, a disagreement after a dropped handoff:
“A teammate and I shared responsibility for a client report, and a piece he was supposed to send me came in a day late, which meant I had to stay late to finish it before the deadline. I was frustrated and it showed a little the next morning, which he noticed. Rather than let it sit, I asked him directly what had happened, and it turned out he’d been juggling a family issue that week and hadn’t wanted to flag it. I apologized for how I’d reacted, we agreed on a heads-up system for either of us to flag when we’re at risk of missing a deadline, and that system has caught two potential misses since. We still work together regularly and it’s one of the smoother working relationships I have.”
Both stories name a real, specific tension, treat the other person as reasonable, and spend the bulk of the airtime on the resolution rather than the disagreement.
Should you mention a conflict with your boss?
You can, but it needs more care than a peer story. Frame it as a disagreement about a decision or an approach, never as a complaint about their management style or character, and keep any criticism of them light and forward-looking rather than pointed. If you have an equally strong example with a peer, use that instead, since a boss conflict is easier to accidentally tell in a way that reads as trouble with authority rather than professional disagreement. If the honest story you have is closer to an ongoing bad dynamic with a manager than a single resolved disagreement, that’s better addressed through a different lens; see our guide on dealing with a toxic boss rather than trying to force it into this answer.
A quick comparison table
| Weak version | Strong version |
|---|---|
| ”I don’t really have conflicts” | A real, specific disagreement about work |
| Other person described as wrong or difficult | Other person’s reasoning stated fairly |
| Story ends on unresolved tension | Story ends on a working relationship intact |
What interviewers are actually listening for
Beyond the story itself, they’re checking three things: do you address friction directly instead of avoiding it or escalating it to someone else first, can you hold two people’s reasoning in your head at once without needing to be the one who was right, and did the relationship actually survive. An answer that hits all three tells them more about how you’ll behave on their team than almost any other interview question, including the more obviously important ones about your technical skills.
Practice the tone, not just the words
This story is easy to get wrong in either direction: too soft and it says nothing, too sharp and it raises a flag about how you handle disagreement. The best way to catch that is to say it out loud to someone who will react honestly, not just read it silently and assume it lands the way it sounds in your head. Our guide to common interview questions and answers covers the other behavioral question families you’re likely to hit in the same interview, and pairs well with practicing this one.
If you want to test the tone of this answer against someone who has actually sat on the hiring side of the table, interview prep coaching runs a real mock interview and tells you plainly whether your version comes across as mature or defensive. Take the two-minute quiz and get matched with a coach; the first session is fully refundable within 48 hours.
Frequently asked questions
How do you answer a conflict interview question?
Pick a real, professional disagreement over something that mattered, like an approach to a project or a missed handoff, rather than a personality clash. Describe the other person's position fairly, even generously, before explaining your own. Spend most of your answer on how you resolved it directly with them, and close on the state of the working relationship afterward. The goal is to show you can disagree with someone and still work well with them.
What is a good example of workplace conflict?
A good example is a disagreement over how to approach shared work: two people wanting to prioritize a project differently, a disagreement about a decision that affected both your work, or a case where one of you dropped a handoff and it caused friction. It should be specific enough to have real detail, but not so personal or severe that it suggests an ongoing pattern or a relationship that never recovered.
Should I mention a conflict with my boss?
You can, but be more careful with tone than you would with a peer. Frame it as a disagreement about approach or a decision, not a complaint about their management or character, and keep any criticism of them minimal and forward-looking. If you have a strong example with a peer instead, that is often the safer choice, since a manager conflict is easier to accidentally tell in a way that sounds like you struggle with authority.
What are interviewers looking for in this answer?
They are checking whether you can disagree with someone professionally without escalating it, whether you take the initiative to resolve friction directly rather than avoiding it or going over someone's head, and whether the relationship survived the disagreement. A candidate who says they've never had a real conflict, or who tells a one-sided story where they were entirely right, raises more concern than one with an honest, well-handled example.