When an interviewer asks you to describe a conflict with a coworker, they aren’t looking for drama. They want evidence that you can disagree with someone and still get the work done. The most common mistakes are easy to fix once you see them, so this guide is built around side-by-side comparisons: three typical workplace conflicts, each told badly and then told well, with notes on what changed.
Why this question comes up so often
It is a behavioural question: your past behaviour is treated as evidence of how you will act in the new job. Career advice site The Muse says interviewers are gauging emotional intelligence, collaboration and conflict resolution, and that the answer reveals your self-control, communication style and ability to defuse tense situations. Jobs site Snagajob puts the core test more plainly: whether you are a team player capable of resolving minor issues, talking to the coworker directly rather than escalating to a manager unless it is necessary.
Between them, The Muse and Snagajob describe a strong answer as containing:
- A work-related disagreement, such as how to run a project or handle a customer, rather than a personal annoyance.
- The facts told neutrally, without criticising the other person.
- The specific steps you took, usually including a direct conversation.
- A resolution, ideally through compromise or shared goals, and what you learned.
The STAR structure (Situation, Task, Action, Result) keeps this in order, but the comparisons below matter more than the acronym. All examples are illustrative; they don’t describe real people or companies.
Situation 1: A peer disagrees with how to do a task
This is the safest and most common choice. Two people at the same level want to approach a piece of work differently.
Weak version
A colleague on my team always wanted to do things his own way and wouldn’t listen. On one report he insisted on using his old template even though mine was clearly better. In the end I just did my sections my way and he did his, and our manager sorted it out.
Strong version
A colleague and I were jointly preparing a monthly sales report, and we disagreed about the format. He preferred the existing template because the regional managers were used to it; I wanted to add a summary page because managers kept asking us the same questions by email. We were both behind schedule, and it was starting to cause tension. I suggested we take fifteen minutes to compare the two versions against what the managers actually needed. We agreed to keep his template and add my one-page summary at the front, then asked two managers for feedback after the first month. Both preferred it, and the follow-up emails dropped noticeably. I learned to argue from the reader’s needs rather than my own preference. It made the conversation much easier.
What changed
- Labels became reasons. “Wouldn’t listen” and “clearly better” were replaced with each person’s actual reasoning, which shows you understood his point of view.
- The candidate acted. In the weak version, the manager resolved it. Snagajob recommends talking to the coworker one-to-one rather than escalating unless it is necessary.
- There is an outcome and a lesson. The strong version ends with a result and a transferable habit.
Situation 2: A conflict with your manager
Disagreeing with someone senior is riskier to describe, but a good example shows maturity: you raised a concern respectfully, accepted the decision or changed it with evidence, and the relationship stayed intact.
Weak version
My manager set an impossible deadline for a client proposal. I told him it couldn’t be done and he didn’t like that. We had a bit of an argument, but I was proved right because we missed the deadline anyway.
Strong version
My manager agreed a Thursday deadline with a client for a proposal that normally takes our team a week, and we had three days. I thought it was too tight to do well, but I didn’t want to just say no. I listed the sections, estimated the time for each and asked to meet. I showed him that we could deliver a strong proposal on Thursday if we reused an approved case study and moved the detailed pricing to an appendix sent the following Monday. He agreed to check that with the client, who accepted it. We delivered on time and won the work. Since then I bring a plan with options when I disagree with a deadline, not just the problem.
What changed
- “Proved right” disappeared. Being right at your manager’s expense is not the point; reaching a workable outcome is.
- Evidence replaced opinion. A task list and time estimates turned a complaint into a proposal.
- The decision stayed with the manager. The candidate offered options and respected his role.
Situation 3: Miscommunication in a multinational team
If you work in an international team, as many people in the UAE do, some disagreements start as differences in communication style rather than in substance. A well-told example of this kind shows you check assumptions before acting on them.
Weak version
One of my colleagues was very rude in emails. She would just reply with one line and no greeting, so I stopped working with her as much as I could and asked others to deal with her.
Strong version
In a previous role I worked closely with a colleague in another office who replied to my requests in one or two lines, with no greeting. I read it as irritation, and I noticed I was starting to avoid sending her requests, which was slowing down our shared work. Instead of guessing, I set up a short video call to plan the next quarter. During the call it became clear that short, direct emails were simply normal in her team, and that she found my longer messages hard to act on quickly. We agreed I would put the request and deadline in the first line, and she would flag anything urgent in the subject. Our turnaround improved, and I’ve since made a habit of discussing communication preferences early with new colleagues.
What changed
- The assumption was named. The strong version admits the candidate misread the situation, which shows self-awareness.
- Avoidance became action. The Muse warns that answers suggesting avoidance count against you; the strong version replaces avoidance with a conversation.
- No nationality stereotypes. The difference is described as a team habit, not a judgement about anyone’s culture.
Quick reference: phrases to avoid and what to say instead
| Avoid | Why | Try instead |
|---|---|---|
| “She was lazy / difficult / rude.” | Criticises the other person and sounds unprofessional. | “We had different expectations about…” |
| “I don’t really get into conflicts.” | The Muse says this suggests avoidance or a lack of self-awareness. | A small, real disagreement that ended well. |
| “I took it to my manager straight away.” | Suggests you can’t resolve minor issues yourself. | “I spoke to him directly first, and we agreed…” |
| “In the end I was proved right.” | Sounds like you were trying to win. | “We agreed on an approach that…” |
| “It was entirely their fault.” | The Muse flags this as a sign of low self-awareness. | “Looking back, I could have…” |
If you genuinely can’t think of a conflict
Saying you have never disagreed with anyone at work is a poor answer. Interviewers rarely believe it, and it suggests you either avoid difficult conversations or don’t notice them. If nothing dramatic comes to mind, that is normal. Most useful examples are small. Try these prompts:
- A time you and a colleague wanted to prioritise different tasks.
- A handover that went wrong because of unclear expectations.
- A group project at university where someone wasn’t contributing.
- A customer request where you and a colleague disagreed on what to offer.
- A meeting where you challenged a plan and it changed, or didn’t.
A minor disagreement, handled calmly and resolved well, is a perfectly good answer. If you are a fresh graduate, examples from internships, part-time jobs, volunteering or group coursework are acceptable. Say so briefly and tell the story the same way.
Preparing your answer
- List three or four disagreements from the last few years and choose the one with the clearest resolution.
- Write each person’s reasoning in one sentence. If you can’t state the other person’s view fairly, pick another example.
- Write down the specific steps you took and the outcome, with real figures only if you have them.
- End with one habit you have kept since.
- Say it aloud. If setting up the disagreement takes longer than explaining how you resolved it, shorten the set-up.
After each interview, jot down any follow-up the interviewer asked about your conflict story, such as “what did your manager think?” or “would you handle it the same way now?”. Those notes show where the story is thin. Keeping them next to each application in your career profile means they are to hand before the next round. If an example shows a skill you don’t yet mention on your CV, such as stakeholder management or cross-office coordination, consider adding it before the interview with the resume builder.
Frequently asked questions
Can I talk about a conflict with my current employer?
Yes, as long as you describe it neutrally and don’t share confidential details. Interviewers may wonder how you would describe them later, so tone matters even more.
What if the conflict wasn’t fully resolved?
Be honest about the outcome, then explain what you did to keep the work moving and what you would do differently. An unresolved but professionally handled disagreement is still a reasonable example.
Is it wise to choose a conflict with a client instead?
Only if the question allows it. “A conflict with a coworker” asks about internal relationships, so a client story may sound like you are avoiding the question. Keep client examples for questions about customer service or difficult stakeholders.
Should I mention that I involved HR?
Only if the situation genuinely required it, such as harassment or a serious policy breach. For ordinary disagreements, choose an example you resolved through direct conversation.