“Tell me about a time you had a conflict”: how to answer (with examples)

Updated October 21, 2026

Choose a real professional disagreement about the work, not a personal feud, and tell it calmly: the situation, the other person's point of view, what you did to resolve it (a private conversation, listening, facts, a compromise or a proper escalation), and the result for the work and the relationship.

To answer “Tell me about a time you had a conflict with a coworker”, pick a real disagreement about the work and walk through it calmly: the situation, how the other person saw it, what you did to resolve it and what happened to the work and the relationship afterwards. The interviewer isn't trying to find out who was right. They want to see how you behave when people don't agree.

What is the interviewer testing with conflict questions?

You'll hear it as “Tell me about a time you had a conflict with a colleague”, “Describe a disagreement with your manager”, “How do you handle conflict?” or “Tell me about a time you worked with someone difficult.” In every version, the interviewer is listening for:

Calm. Do you stay level when describing tension, or does the frustration come back as you talk?
Empathy. Can you explain the other person's position fairly, even if you disagreed?
Communication. Did you talk to them directly, and how?
Focus on the result. Did you keep the goal of the work in view, rather than winning the argument?

How do you choose the right conflict story?

A professional disagreement, not a personal feud. It should be about how to do the work: priorities, a decision, a deadline, quality, workload. Not about personalities or office gossip.
Something you actively handled. You need to have done something, not just waited for it to pass or for a manager to step in.
Resolved, or at least handled well. A clear ending for the work, even if you didn't fully agree in the end.
Fair to the other person. If you can't describe their view without sounding annoyed, choose another story.

How should you structure your answer?

Four steps, about two minutes:

The situation. What you were working on and what the disagreement was about, in two or three sentences.
The other person's point of view. What they wanted and why it made sense from where they stood. This step is what most candidates skip, and it's what sets good answers apart.
What you did. A private conversation rather than a public argument, listening before arguing, bringing facts, proposing a compromise, or escalating properly if it couldn't be solved between you.
The result and the relationship afterwards. What happened to the work, and how you worked together after.

This is a version of the STAR method, with one extra step for the other person's view. That guide goes deeper on structure and timing.

How do you adapt it to each version of the question?

Conflict with a colleague

The most common version. Show that you went to them directly before involving anyone else, and that you looked for a solution that worked for both of you.

Conflict with your manager

Here the interviewer checks whether you can disagree with respect for their role. Show that you raised your concern in private, with facts, and that you accepted the final decision if it went the other way.

Conflict with a client

Show that you kept the relationship professional and protected both the client's interests and your company's. Explaining the client's constraints matters even more here.

Conflict in a team project at school

Perfectly fine if you're a student or recent graduate. Group projects are full of real disagreements about workload and quality. Treat it with the same structure; our guide to behavioral interview questions has more ideas for finding stories with little work experience.

“How do you handle conflict?” asked in general

Give your approach in one or two sentences, then back it with a short example straight away. A general principle without a story sounds like a textbook.

Sample answers

All the examples below are fictional.

With a colleague

Fictional example: Tyler Brooks, junior software developer.

“On my first team, a senior developer, Sam, kept rejecting my code reviews with very short comments, and I started to feel he was blocking me. Before getting frustrated, I asked him for a twenty-minute call. It turned out he'd been burned by a bug from a similar change the year before and wanted more tests, but he didn't have time to explain each time. I didn't agree with everything he asked for, but I understood it. We agreed on a short checklist of what he needed to see in a review, and I added it to our team's guidelines. My reviews started going through on the first or second pass, and Sam became the person I went to with questions.”

With a manager

Fictional example: Monica Reyes, operations coordinator at a warehouse.

“My manager wanted to move all of our picking to a single early shift to cut overtime. I could see the logic, since overtime costs had been flagged by finance. But I'd been tracking late orders, and most came in after 2 p.m., so I was worried same-day shipping would drop. I asked for a meeting and brought two weeks of order times. I suggested keeping a small afternoon team of three instead of the full shift. She didn't agree at first, but she agreed to a one-month trial. Overtime still went down, and we kept same-day shipping. She now asks me to pull the data before any schedule change.”

With a client

Fictional example: Derek Owens, project manager at a small design agency.

“A client kept adding new pages to a website project after we'd agreed the scope, and wanted it all by the original launch date. I called the client's marketing lead directly and asked what was driving the changes. It turned out their sales team had just launched a new product line. I explained what we could deliver by the date, and offered to launch the agreed pages first and the new ones two weeks later, as a separate phase. They accepted. The site launched on time, and they signed for a second project the following quarter.”

What follow-up questions should you expect?

“What would you do differently?” Even in a good story, name one thing.
“How did the other person react to your approach?” Describe their reaction honestly.
“What would you have done if they hadn't agreed?” Explain how you'd escalate properly.
“Tell me about a conflict you didn't handle well.” Some interviewers ask this to test honesty. It overlaps with the failure question, so prepare one.

Which mistakes should you avoid?

“I don't really have conflicts.” It sounds either untrue or like you avoid hard conversations.
Badmouthing the other person. The interviewer will wonder what you'd say about them.
A story where you were simply right. If the whole point is that you won, you've missed the question.
No outcome. A story that ends at the argument leaves the interviewer guessing.
Going straight to the manager. Escalating before talking to the person directly is usually a red flag, unless the situation required it.

How do you practice this answer out loud?

Write your story as four bullet points, then say it out loud and time it. Pay attention to step 2: say the other person's view in a neutral voice, as if they were in the room. Then record yourself. Tension often shows in tone more than in words, and a sentence that reads as neutral can sound sharp when spoken.

Prepare at least two stories (one with a colleague, one with a manager or client) so you can pick the one that fits the question you're asked.

Frequently asked questions

What if the conflict was never really resolved?

You can still use it if you handled it well. Say what you did, what the outcome was for the work, and how you kept the working relationship functional. “We never fully agreed, but we found a way to deliver together” is an honest and acceptable ending.

Can I talk about a conflict with my current manager?

Yes, as long as the story is about a work decision and you describe your manager fairly. Interviewers often ask this specifically, because it shows whether you can disagree upward with respect. Avoid anything that sounds like you're still frustrated with them.

Should I say who was right in the end?

Only if it matters to the result, and briefly. The interviewer cares much more about how you handled the disagreement than about who won. Stories where you were proven right tend to sound like a victory lap; stories where you changed your mind can be the strongest ones.

What if I really can't think of a conflict?

Think smaller. A disagreement about priorities, a deadline, a design choice or how to split tasks all count. Interviewers aren't expecting dramatic stories. “Disagreement” is often a better word to search your memory with than “conflict”.