Alex · Interview Prep Interview Prep — Guides Tell Me About a Conflict at Work: How to Answer (With Examples)
To answer “tell me about a conflict at work,” pick a real, specific disagreement, explain what caused it in one or two sentences, then spend most of your answer on how you personally worked toward a resolution and what the outcome was. Choose a conflict you actually resolved professionally — never a screaming match, a story where you were the villain, or one where you “won” by steamrolling someone.
This is a behavioral question, so the interviewer expects the STAR structure: Situation, Task, Action, Result. What they’re really testing is whether you can disagree with a colleague and still keep the work — and the relationship — intact.
What the Interviewer Is Actually Testing
Nobody asks about conflict because they want drama. They ask because conflict is inevitable on any team, and they need to know how you behave when it happens. A trained interviewer is scoring four things in your answer:
- Emotional control. Did you stay professional, or did the conflict become personal?
- Perspective-taking. Did you try to understand the other person’s position, or just defend yours?
- Initiative. Did you move toward resolution, or wait for someone else to fix it?
- Outcome. Did the working relationship survive, and did the work improve?
The trap is that “conflict” sounds like an invitation to vent. It isn’t. The candidate who describes a coworker as “impossible” and themselves as blameless fails the emotional-control and perspective-taking checks in one sentence.
Pick the Right Story
Not every conflict makes a good answer. Use this filter before you commit to a story.
| Good conflict to tell | Conflict to avoid |
|---|---|
| A professional disagreement over approach, priorities, or standards | A personality clash or personal grudge |
| One where you took initiative to resolve it | One where a manager fixed it for you |
| One with a concrete, positive outcome | One that ended badly or is still unresolved |
| One where you can show empathy for the other side | One where you’re clearly the hero and they’re the villain |
| A peer or cross-team conflict | A conflict with a direct report you had to discipline (unless the role is managerial) |
The strongest choice is usually a disagreement about how to do the work — two competent people who wanted the same outcome but disagreed on the path. That framing lets you show judgment without making anyone look bad.
The Structure, Beat by Beat
Situation (about 20%). Set the scene in two or three sentences. Who was involved, what was at stake, and what the disagreement was about. Keep it factual and neutral — describe the other person’s position fairly, not as a caricature.
Task (one sentence). What you needed to achieve. Usually: resolve the disagreement without damaging the relationship or the deliverable.
Action (about 60%). This is where the answer is won. Describe the specific steps you took. The best conflict answers almost always include some version of: you listened first, you looked for the shared goal, you brought data or a concrete proposal, and you found a path both sides could accept. Speak in first person singular — “I,” not “we.”
Result (about 20%). How it ended. The resolution, the state of the relationship afterward, and ideally a measurable outcome. Close with a short reflection on what you learned about handling disagreement.
Phrases That Score Well
Interviewers respond to language that signals maturity. Work these instincts into your answer:
- “I wanted to understand where they were coming from before I pushed my view.”
- “We both actually wanted the same outcome — we just disagreed on how to get there.”
- “I brought the data so it wasn’t my opinion versus theirs.”
- “I proposed a compromise that gave each of us the part we cared about most.”
- “The relationship was fine afterward — we worked together again on the next project.”
Avoid absolute framing: “I proved I was right,” “they finally admitted their mistake,” “I refused to back down.” Even if true, it reads as rigid.
Two Full Example Answers
Example 1: Disagreement over approach
Situation: “On a analytics dashboard project, the backend engineer and I disagreed on the data model. He wanted to denormalize everything for query speed; I was worried it would make the data impossible to keep consistent as the product grew. We were blocking each other and the deadline was three weeks out.”
Task: “I needed us aligned on one model fast, without turning it into a standoff that would slow the whole team.”
Action: “Instead of trading opinions in Slack, I asked him to pair for an hour and walk me through his reasoning. His concern was real — a normalized model would have made the main dashboard query slow. So I stopped arguing for pure normalization and instead proposed a hybrid: normalize the source tables, but build a denormalized read layer just for the dashboard. I sketched it out, we stress-tested it against his query-speed worry, and it held up.”
Result: “We shipped on time with a model we both trusted. The read-layer pattern became how the team handled every reporting feature after that. What I took from it: when two competent people dig in, they’re usually each protecting something legitimate — the fix is to find the design that protects both, not to win the argument.”
Example 2: Cross-team conflict over priorities
Situation: “I was a product manager, and our support lead was escalating a bug fix as urgent while my roadmap had it as low priority. She was frustrated because her team was fielding the same complaint daily, and I was frustrated because I thought the volume didn’t justify pulling engineers off a launch.”
Task: “I needed to resolve the disagreement fairly, because we were about to have the same fight every sprint.”
Action: “I asked her to send me the actual ticket data instead of debating the impression of urgency. When I pulled it, the bug was consuming far more support hours than I’d assumed — she was right about the cost, I was right that it wasn’t a fire. So I proposed a middle path: I’d slot a scoped two-day fix into the next sprint rather than a full rewrite, and in exchange she’d route those tickets through a temporary macro until then. I also set up a shared monthly review so priority calls stopped being one team’s guess.”
Result: “The fix shipped, support tickets on that issue dropped by more than half, and the monthly review killed the recurring tension between our teams. I learned that most cross-team conflict is really an information gap — once we were looking at the same numbers, the disagreement mostly dissolved.”
Common Mistakes
Picking a conflict where you were wrong or aggressive. The story is a character reference. If you come across as combative, no polish saves it.
Making the other person a villain. “She was completely unreasonable” tells the interviewer you can’t take another perspective. Describe them as a reasonable person you happened to disagree with.
No resolution. A conflict story that ends with “we just kind of avoided each other after that” is a failure story you didn’t mean to tell.
Answering in the abstract. “I always try to see both sides” is not an answer. They asked for a specific time. Give them one real event.
Choosing something trivial. A five-minute disagreement about lunch shows nothing. Pick a conflict with real stakes that you handled well.
Running long. Two minutes maximum. The backstory is not the point — your behavior is. Practicing your conflict story out loud, ideally in a timed mock interview with Alex, an AI interview coach, is the fastest way to catch yourself rambling through setup and burning the clock before you reach the resolution.
FAQ
What if I’ve never had a real conflict at work?
You have — you’re likely defining “conflict” too narrowly. A disagreement over an approach, a deadline, a priority, or a standard all count. Pick a professional difference of opinion you worked through. If you genuinely can’t find one, use a conflict from a project, volunteer role, or team setting outside your job, and say so.
Should I admit I was partly wrong in the conflict?
Yes, if it’s true — a small, honest concession (“looking at the data, she had a point I’d missed”) makes you far more credible than someone who was flawlessly right the whole time. It signals you can update your view, which is exactly the trait the question is probing.
Can I use a conflict with my manager?
Carefully. It can work if you frame it as respectful disagreement that you raised professionally and resolved well. Avoid any story that makes you look insubordinate or your manager look incompetent. When in doubt, a peer or cross-team conflict is the safer choice.
How is this different from “tell me about a difficult coworker”?
They’re close cousins and the same structure works for both. “Difficult coworker” leans toward an ongoing relationship you had to manage; “conflict” leans toward a specific disagreement you had to resolve. Prepare distinct stories for each so you’re not reusing one project across every behavioral question.