How to Answer “Tell Me About a Conflict or Disagreement at Work”
· by the InterviewCrusher team
This question isn't about the conflict: it's about how you behave inside one. The interviewer takes for granted that every team has friction; what they want to see is your maturity in handling it. Do you listen to the other side or dig in? Do you separate the problem from the person? Are you looking for a way out or just to be right? It's a textbook behavioral question, and it's assessed with STAR.
There are two nearly guaranteed ways to fail it. The first is to say “I've never had a conflict”: either you're not self-aware, or you haven't really worked with anyone, or you're not being honest. The second is to tell a real conflict but come out of it as the victim or pin all the blame on the other person (“my boss had no idea,” “the team didn't back me up”). The moment you place blame, you stop talking about your maturity and start demonstrating the opposite.
The answer that convinces picks a concrete professional disagreement (not a personal drama), explains both positions with respect, tells what you did to resolve it, and ends with a result and a lesson. The conflict is the setting; the protagonist is how you communicate and resolve.
What mistakes should you avoid when answering “Tell me about a conflict or disagreement at work”?
- Saying “I've never had a conflict”: it sounds evasive or unbelievable. We've all had them.
- Playing the victim or blaming the other person: the moment you point a finger, the answer turns against you.
- Choosing a personal or emotional clash (personality dislikes, office drama) instead of a professional disagreement.
- Telling a conflict you won by “steamrolling” the other person: managing conflict isn't about imposing your will, it's about resolving it.
STAR applied to conflict
- 1
Situation and task
Set the frame quickly: who the disagreement was with (a colleague, your boss, another team) and what it was about. Make it a professional, legitimate issue, not a petty grudge. “My design colleague and I didn't agree on whether to launch with fewer features or wait.”
- 2
Action
This is where 80% of the value is. Tell what YOU did: listen to their reasoning, lay out yours with data, look for common ground, propose a way forward. Speak about the other person with respect. This is what demonstrates your maturity and how you communicate.
- 3
Result and lesson
How it ended, ideally with a number or a concrete fact, and what you took away. The ideal is an ending where the relationship stayed intact or came out stronger. Close with what you learned about working with people who think differently.
This kind of behavioral question is answered with a story organized into four parts: Situation, Task, Action, and Result. Complete guide to the STAR method.
Sample answers
“During a launch, my design colleague wanted to push it back two weeks to polish the interface, and I was arguing to ship now with what we had so we wouldn't miss the market window. The discussion was getting entrenched, so I suggested we stop and look at the data together: we reviewed the reported issues and saw that only two of the six changes he wanted were truly blocking. We agreed to launch with those two fixed and leave the rest for the next version. We shipped only three days late instead of two weeks, with no user complaints about the interface, and ever since we've had the habit of settling this kind of question with data rather than by who pushes hardest. I learned that almost no disagreement is as fundamental as it seems when you're worked up.”
“My manager wanted us to spend the quarter acquiring new customers, and I could see in the numbers that we were losing the ones we already had: the churn rate had risen to 9%. Instead of debating it in the meeting in front of everyone, I asked for ten minutes alone, brought him the data, and proposed splitting the effort: 70% on retention, 30% on acquisition, for one month, then review. He agreed to try it. In that month we brought churn down to 5%, and the cost of winning back a customer was far cheaper than acquiring a new one, so we kept the focus. My takeaway was that raising a disagreement with data and in private carries far more weight than being right out loud.”
Quick tips
- Have an example prepared and chosen with care: a professional disagreement that ended well and where you acted with a level head.
- Talk about the other person as someone reasonable, not as the villain of the story: that's exactly what they're measuring.
- Always close with the result and the lesson; without them, it just sounds like you're recounting a fight you won.
Knowing the answer isn't the same as saying it out loud
Practice this question with an AI recruiter that asks follow-ups, keeps the pressure on, and gives you honest feedback. In your language and no credit card.