What's the best way to answer 'Tell me about a conflict'?

Pick a real professional disagreement, tell it in STAR order, and focus on how you engaged with it maturely and what the outcome was. The interviewer isn't checking whether you avoid conflict, they want to see that you can disagree without it turning personal: that you listened to the other side, looked for the underlying interest or the data, and reached a resolution that kept the relationship intact. Don't make the other person the villain, and make sure the story ends with a clear outcome and ideally something you learned.

Should I talk about a conflict with my manager or a coworker?

Either works, and a conflict with a manager can be a strong choice if you handle it well, because it shows you can disagree up respectfully and then commit. The key is to show you raised the disagreement professionally (privately, with reasoning or data), heard their view, and either changed your mind or disagreed and committed once the decision was made. Avoid stories where you simply overrode someone or went around them, which signal the opposite of what they're testing.

What if I avoid conflict and can't think of one?

Conflict doesn't have to mean a shouting match. A disagreement over priorities, a design decision two people saw differently, pushback on a deadline, all of these count. Saying 'I don't really have conflicts' is the weakest answer, because it reads as either avoidance or a lack of self-awareness. Think of a time you and someone capable disagreed about the right call, and tell that story, focusing on how you worked it out.

Do interviewers expect the STAR method here?

Yes. Conflict is a behavioural question, so STAR (situation, task, action, result) is the structure that keeps you from rambling or sounding defensive. Keep the situation brief and neutral, spend the action on how you engaged (listening, finding common ground, using data), and land a clear result. Adding a short line on what you learned about working with people makes it stronger.

Interview prep · the behavioural question

How to answer “Tell me about a conflict”

People hear this and reach for a story where they were right and someone else was difficult. That's the trap. The interviewer isn't checking whether you avoid conflict or whether you win it. They're checking whether you can disagree like a professional: engage it, keep it off the personal, and reach a resolution that doesn't burn the relationship. Here's how to tell the story so it shows that.

The short version

It tests mature disagreement, not whether you avoid conflict.
Tell it in STAR order, with the action on how you engaged: listened, found common ground, used data.
Don't make the other person the villain, and end with a clear resolution.

What they're actually checking

Disagreement is normal on any good team; what matters is how you handle it. This question tests whether you can hold a different view without it becoming personal, whether you try to understand the other side rather than just win, and whether you can land on a resolution and move forward. For senior roles it also tests whether you can disagree with authority and then commit. The story you choose and the way you tell it reveal all of that, often more than the conflict itself does.

The answers that backfire

“I don't really have conflicts” reads as avoidance or no self-awareness. Making the other person the villain tells the interviewer how you'll talk about them one day, and it shows you frame disagreement as a fight to win. The steamroller story (“I was right, so I overrode them”) signals you don't actually collaborate. And a conflict with no resolution leaves the interviewer wondering how it ended and whether you can close one out.

The structure that works: STAR, with the focus on engagement

Use STAR and put the weight on how you handled it:

Situation and task, brief and neutral, the disagreement and what was at stake, without painting the other person badly.
Action, how you engaged: heard their view, surfaced the real interest or the data, looked for common ground rather than a win.
Result, how it resolved, and that the working relationship survived. A short line on what you learned makes it stronger.

For example: “A staff engineer and I disagreed on whether to rewrite a service or refactor it. I thought a rewrite was overkill on the timeline. Instead of pushing my view, I asked him to walk me through the failure modes he was worried about, and we spent an hour mapping them against the deadline. It turned out we could refactor the risky parts and defer the rest, which neither of us had framed that way alone. We shipped on time, and I learned to ask what someone is afraid of before arguing about the solution.”

Conflict with a manager: disagree, then commit

A disagreement with a manager is a strong story if you handle it well, because it shows you can push back up the chain professionally. Show that you raised it privately and with reasoning, heard their side, and then either changed your mind or disagreed and committed once the call was made. That “disagree and commit” move is exactly the maturity senior interviewers look for, and it's a long way from going around your manager or sulking about a decision.

The fast way: rehearse it with follow-ups

Conflict stories get probed (“What would the other person say?”, “Would you do anything differently?”), which is where they slip into sounding defensive. Calibrd predicts the behavioural questions for a specific role and lets you practise your spoken answer, then a full mock interview follows up the way a panel would, so the first time you're pushed on it isn't in the room. It's the same practice loop that works for every question.

So what do you actually do

Treat it as a test of mature disagreement, not a story where you won.
Pick a real professional disagreement and keep the other person human.
Tell it in STAR, with the action on how you engaged, and end on a clear resolution.
Practise it and rehearse the follow-ups, since that's where it's tested.

Rehearse the behavioural rounds

Practise your conflict story, with follow-ups

Paste a real job description and Calibrd predicts the behavioural questions, then lets you practise your spoken answers and scores each one. Run a full mock interview for the follow-ups a real panel would ask. Your first mock is free. Free to install.

Add to Chrome Or scan one JD →

Free to install · Preview every posting · Paid plans from $3.99