Tell me about resolving a conflict between two developers
Model answer
Use the STAR structure.
Situation. Two developers disagreed repeatedly in code reviews. One thought the other's comments were nitpicking, the other felt his feedback was ignored. The tension was visible in the stand-ups and slowing pull requests.
Task. Restore a working relationship and keep the team's flow, without taking sides.
Action. I spoke with each person privately and listened for the interests behind the complaints. Then I brought them together for a facilitated conversation, with ground rules: describe the behavior and its impact, not the person. They agreed on a team review guideline that separated blocking issues from suggestions, and a rule to discuss complex points by call instead of comments. I checked in a week later.
Result. Review times dropped and the two began pairing on a feature.
The lesson: act early, listen first, and let the people involved own the agreement.
Key points
- Listen privately to each side first
- Facilitate with ground rules: behavior and impact, not blame
- Let them agree on a concrete working practice and follow up
Likely follow-ups
- What would you do if the conflict continued after that conversation?
- When would you involve a manager or HR?
Common mistakes
- Taking one side or deciding who is right
- Ignoring the tension hoping it will go away