Describe a time when you had to resolve a conflict between team members. What was the situation, how did you approach it, and what was the outcome?

Question

Accepted Answer

I will share a specific situation that taught me a lot about effective conflict resolution.

The situation was that two senior engineers on my team had a persistent disagreement about our API strategy. One strongly advocated for GraphQL, citing its flexibility and efficiency for our mobile clients. The other preferred REST, arguing for its simplicity, better caching, and the team's existing expertise. What started as a technical debate became personal, affecting team meetings and code reviews.

For my approach, I started by meeting with each engineer privately. My goal was to understand their underlying concerns, not just their stated positions. I discovered that the GraphQL advocate was frustrated by repeatedly building custom endpoints for the mobile team. The REST advocate was worried about the learning curve and maintenance burden of a new technology stack.

Next, I reframed the conflict. Instead of GraphQL versus REST, the real question was how to efficiently serve our mobile clients while maintaining team productivity. Both engineers agreed on the underlying goal.

I then facilitated a structured evaluation. We defined objective criteria together, including development velocity, client performance, team ramp-up time, and long-term maintainability. Each engineer created a small proof-of-concept. We measured performance and got feedback from the mobile team. We scored both options against our agreed criteria.

The outcome was that the data showed GraphQL performed better for our mobile use cases, but the learning curve was real. We decided to adopt GraphQL for new mobile-facing endpoints while maintaining REST for internal services. I paired the two engineers on the first GraphQL implementation, which turned their conflict into collaboration.

More importantly, the process itself improved our team dynamics. By focusing on shared goals and objective criteria, we established a pattern for resolving future technical disagreements. Both engineers later told me they appreciated how the conflict was handled.

The lessons I took away were to separate people from positions, find common ground first, use data to depersonalize decisions, and turn conflict into collaboration when possible.