How to answer "Tell me about a time you had a conflict at work"

This question sounds like a setup, and in a way it is. "Tell me about a time you had a conflict with a coworker." There is no safe-sounding answer, so a lot of people freeze, then either claim they have never really had a conflict, which nobody believes, or they pick a story where they were clearly right and the other person was clearly the problem.

Both of those misfire. Saying you have never had a conflict reads as either dishonest or as a sign you avoid hard conversations. Telling a story where you are the hero and your coworker is the villain reads as someone who will be difficult to work with. The interviewer is not looking for proof that you win arguments. They want to see how you behave when you and another reasonable person disagree.

Handled well, this is one of the best questions to get, because it lets you show maturity, empathy, and judgment in about ninety seconds.

The short version

• They are not grading the argument. They want to see how you behave when two reasonable people disagree.
• Use the STAR structure: Situation, Task, Action, Result. Spend most of the time on your specific actions, not the drama.
• Pick a real professional disagreement that ended in a workable outcome. Treat the other person as reasonable throughout.

The instinct under pressure is to go vague or assign blame. The fix is reps. Try a real story right now.

Free practice. No signup.

Try it: Tell me about a conflict at work

Tell me about a time you had a conflict at work and how you handled it.

Use the STAR structure: situation, task, action, result. Pick a real disagreement, stay solution-focused, and do not trash the other person. You have about 90 seconds.

Your answer

Type your answer here. Say it out loud first if you can, then type what you said.

Get feedback0/2000

What the interviewer is really checking

Every job involves friction. Priorities collide, two people read the same situation differently, someone pushes back on your plan. The interviewer already knows that. What they cannot tell from your resume is how you act inside that friction. Do you dig in and make it personal, or do you stay focused on the work and find a path forward?

So the content of the conflict barely matters. Your behavior inside it is the whole answer.

The STAR method, in plain terms

STAR is the structure that keeps a story like this clear instead of letting it wander. Four beats.

1. Situation. Set the scene in a sentence or two. Who was involved and what was at stake.
2. Task. What you were responsible for, or what needed to happen.
3. Action. What you specifically did to work through the disagreement. This is the longest part and the most important.
4. Result. How it turned out, ideally with something concrete, and what you took away from it.

The reason STAR works is that it forces you to spend most of your time on your actions, which is exactly what the interviewer wants to hear, and it gives you a clean ending instead of a story that just trails off.

A STAR answer in action

Here is how the structure sounds when it is filled in.

"On a product launch, a designer and I disagreed hard about the timeline." That is the situation. "I owned the schedule, and we were two weeks from a date we had already announced." That is the task. "Instead of pulling rank, I asked her to walk me through what was driving her estimate, and it turned out she had caught a usability problem I hadn't seen. We sat down, mapped what was truly required for launch versus what could ship a week later, and I took the cut list to the stakeholders myself." Those are the actions. "We hit the date with the core experience intact, fixed the usability issue in the first update, and she and I worked together a lot more smoothly after that because we had each seen the other take the work seriously." That is the result, plus the lesson.

Notice what the answer does. It treats the other person as reasonable, it keeps the focus on what the speaker did, and it ends somewhere good.

The traps to avoid

• The blame story. If your answer is mostly about what the other person did wrong, you have lost. Spend your words on your own choices.
• The fake harmony. "I just always get along with everyone" is not an answer. It dodges the question and signals you may avoid necessary conflict.
• The unresolved grudge. Do not pick a conflict you are still angry about. The resentment leaks into your voice, and the interviewer hears it.
• The trivial pick. A squabble over where to get lunch does not show anything. Choose a disagreement that actually mattered to the work.

Choosing the right story

The best conflict stories share a shape. Two reasonable people wanted different things, the stakes were real but not catastrophic, you did something specific to bridge the gap, and it ended in a workable outcome. Before the interview, have one or two of these ready, because trying to invent one on the spot is how people end up rambling or reaching for a grudge.

If you genuinely changed your mind partway through, even better. Showing that you updated your view once you had more information is one of the strongest things you can demonstrate, and almost nobody does it.

The mindset that helps

The instinct in this question is to defend yourself, to prove you were right. Resist it. The interviewer is not grading the argument. They are imagining you on their team, in the inevitable moment when you and a colleague disagree, and they are asking themselves whether you will handle it like an adult.

So tell it that way. Pick a real disagreement, give the other person their due, keep the spotlight on what you did, and land on a result. Do that and the question that felt like a trap becomes the easiest way to show them exactly who they would be hiring.

Run the practice round above with one of your real stories. Tighten it until it follows the four beats without you having to think about them, and the conflict question stops being the one you dread.