How to Handle Conflict With a Colleague in Interviews

When the clash is with a fellow developer, tester, or designer rather than a manager, interviewers want to see whether you resolve peer conflict professionally and directly — or make it worse through gossip, avoidance, or running to the boss. This page teaches the golden rule of peer conflict: make it problem vs problem, not person vs person, and talk to the person directly before involving anyone else.

Disagreeing with a manager is a different situation — see Disagreeing With Your Manager. Here the focus is a teammate at your own level. The interviewer wants proof that you can handle friction like an adult: privately, factually, and with the relationship intact at the end.

The core answer

“To me, conflict means a disagreement, not hostility. When I disagree with a teammate, I first talk to them directly and in private — not in public or in a group, because that makes people defensive. I listen to their point first, because I may not have the full picture. Then we focus on the common goal — ‘we both want this project to turn out well’ — and build a solution from there. If it still doesn’t resolve and the project is stuck, only then do I involve the lead, in a neutral way. But that’s the last step, not the first.”

Scenario: a code-review disagreement

Manager: “Suppose a teammate keeps asking for changes in your code review that you feel are unnecessary. What would you do?”

You: “First, I wouldn’t take the feedback personally — the whole point of review is to make the code better. I’d go through each comment: the valid ones I’ll accept, even if I don’t love them. For the ones I disagree with, I’d ask for the reasoning, in the code or on a quick call — ‘why is this change needed, is there a case I’m missing?’ If they’re right, I learn something; if I’m right, I’ll explain my reasoning with data. If we get stuck on a small point, I’d suggest we check the team standard or ask a senior once, so the PR doesn’t get blocked by an ego battle. The goal is to get the PR merged, not to win the argument.”

Follow-up: “What if they’re targeting you personally?”

Manager: “What if it feels like they’re deliberately targeting you, picking faults in your work every time?”

You: “Even then, I wouldn’t assume bad intent first — they might just be strict with everyone. I’d talk to them directly and calmly, in private: ‘I feel my work is getting extra scrutiny — is there something specific I can improve?’ That’s non-aggressive, but the message is clear. Often that alone resolves it. If the pattern continues and starts affecting the work, then I’d take the facts to the manager — with specific examples, without emotion — not as a personal complaint, but as a work problem to solve.”

Follow-up: “Why didn’t you go to the manager first?”

Manager: “Why did you talk to them directly instead of telling the manager?”

You: “Because resolving small things yourself is more mature, and it keeps the relationship intact. If I take every disagreement to the manager, first I waste their time, and second the team starts seeing me as a complainer. I involve the manager only when the conversation didn’t resolve it, when the project is getting blocked, or when it’s something serious like harassment. Otherwise the first route is always a direct, respectful conversation.”

A real example, told in STAR

Keep one concrete example ready, structured with the STAR method:

• Situation: “A teammate and I were working on the same module; our coding styles differed and we kept overwriting each other’s code.”
• Task: “We needed to agree on a common approach without bruising anyone’s ego.”
• Action: “I talked to them casually over a call and suggested we divide the module clearly — who owns what — and write down a small shared style rule. I also adopted two of their ideas that were genuinely better than mine.”
• Result: “The overwrites stopped, work sped up, and that teammate went on to become one of my best collaborators.”

Ending with the relationship improved is the strongest possible close. It shows the conflict made the team better, not worse.

For situations where the friction is about workload rather than opinion — like a teammate not pulling their weight — see Teamwork & Collaboration.

Tips & mistakes to avoid

• ❌ “I’ve never had a conflict with anyone.” → unbelievable; it sounds like you avoid things or you’re lying.
• ❌ Describing the teammate as “very egotistical” or “lazy.” → it makes you look bad.
• ❌ Involving the manager or HR right away. → immature.
• ✅ Direct + private + problem-focused. “Person vs problem, not person vs person.”
• ✅ Always show that you listened to the other person’s point too — it signals empathy.
• ✅ End with the relationship having improved — that’s a strong, memorable close.