Conflict Stories 3 of 5: Actions That Show Strong Conflict Resolution Skills
What interviewers really listen for in your conflict stories
This is the third in a series of posts on telling conflict stories, derived from the content in my upcoming book, Mastering Behavioral Interviews.
Want to get early access to the book and follow along with the writing process? All you have to do is subscribe to the substack!
Willing to be a beta reader in exchange for having your name printed in the book? Apply here and I’ll keep you in the loop on how to help with the book.
You've identified a high-stakes workplace conflict where you were deeply involved and ultimately proved right. But how you tell it determines whether the interviewer sees you as someone who skillfully navigates disagreements.
The difference lies in the specific actions you took to move the conflict toward resolution.
Interviewers aren't just listening for the outcome of your conflict. They're pattern-matching the behaviors you describe to predict how you'll handle future disagreements on their team. Show them the right actions, and they'll see someone who can be trusted with complex interpersonal challenges.
Here are seven key actions that transform ordinary workplace disagreements into compelling evidence of senior-level conflict resolution skills.
1. Be Proactive in Raising Concerns
Instead of waiting for conflicts to escalate, you address them early and directly.
Mature builders don't let disagreements fester. When they spot a problem, they initiate the conversation rather than hoping someone else will handle it or that the issue will resolve itself.
What this looks like:
"I noticed we were heading toward a potential architecture mismatch, so I scheduled a meeting with the team lead to discuss it."
"When I saw the product requirements would conflict with our performance goals, I reached out to the PM directly."
"I could tell my teammate was frustrated with the code review feedback, so I suggested we grab coffee to talk through it."
Why interviewers love this: Being proactive shows you take ownership of team dynamics and don't create problems by avoiding difficult conversations. It demonstrates emotional intelligence and leadership potential.
Red flag alternative: "Eventually things got so bad that my manager had to step in and sort it out."
2. Seek to Understand Before Being Understood
You invest time in truly comprehending the other person's position before pushing your own agenda.
This is Stephen Covey's Habit #5 from Seven Habits of Highly Effective People, and it's fundamental to healthy relationships. The best ideas should win, but you can't identify the best ideas without understanding all perspectives.
What this looks like:
"I asked her to walk me through her reasoning for choosing the microservices approach."
"I wanted to understand what specific pain points were driving his preference for the new framework."
"I scheduled a longer meeting so we could really dig into why our estimates were so different."
Why interviewers love this: This shows intellectual humility and collaborative problem-solving skills. It proves you're not just stubborn or argumentative—you're genuinely interested in finding the best solution.
Red flag alternative: "I immediately explained why their approach was wrong."
3. Use Data to Make Decisions
You collect evidence, run experiments, or build prototypes to inform the resolution.
Tech companies thrive on data-driven decision making. When personal opinions clash, the person who brings objective evidence usually wins—and should win.
What this looks like:
"I built a quick prototype to test both approaches and measure the performance difference."
"I analyzed the last six months of bug reports to see which components were causing the most issues."
"I surveyed our beta users to understand how they actually used the feature."
Why interviewers love this: This demonstrates technical judgment, initiative, and the ability to move from subjective arguments to objective analysis. It shows you can cut through debate with facts.
Red flag alternative: "We argued about it for weeks and finally went with the manager’s opinion."
4. Choose the Right Communication Channels
You escalate through appropriate mediums based on the complexity and sensitivity of the conflict.
Knowing when to use Slack vs. email vs. face-to-face conversations vs. formal meetings shows professional maturity and communication skills.
What this looks like:
"I started with a casual conversation, but when we couldn't align, I suggested a formal design review."
"I moved the discussion out of the public Slack channel and into a private call."
"I wrote up my concerns in a shared document so we could both refer to specific points."
Why interviewers love this: This shows you understand the human dynamics of conflict resolution and can adapt your approach based on the situation. It demonstrates both emotional intelligence and professional judgment.
Red flag alternative: "We went back and forth in the pull request comments for two weeks."
5. Demonstrate Empathy and Preserve Relationships
You acknowledge the other person's concerns and maintain respect even during disagreement.
This isn't about being nice—it's about being effective. Conflicts that leave relationships damaged create ongoing team dysfunction. Senior engineers resolve disagreements while keeping collaboration strong.
What this looks like:
"I understood why she was concerned about the migration timeline, given her experience with previous migrations that had gone poorly."
"I acknowledged that his approach would be simpler to implement, even though I thought the trade-offs weren't worth it."
"I made sure he knew I respected his expertise, even though I disagreed with this particular decision."
Why interviewers love this: This shows emotional maturity and long-term thinking about team dynamics. It proves you can disagree without being disagreeable.
Red flag alternative: "He was being completely unreasonable, so we moved ahead with my approach.”
6. Involve the Right People at the Right Time
You bring in additional perspectives or authority when needed, but not before you've tried to resolve things directly.
Knowing when to escalate, when to bring in subject matter experts, and when to keep working one-on-one shows sophisticated judgment about organizational dynamics.
What this looks like:
"When we couldn't agree on the database choice, I brought in the TL to give us a third perspective."
"I escalated to my manager after we'd tried three different approaches and still couldn't align."
"I suggested we include the security team in the conversation since they'd have opinions about the encryption approach."
Why interviewers love this: This demonstrates understanding of when conflicts are beyond your scope to resolve and shows you can navigate organizational resources effectively.
Red flag alternative: "I immediately went to my manager because I knew my teammate’s approach would be ineffective."
7. Drive to Clear Resolution
You don't let conflicts drag on indefinitely—you push for decisions and clear next steps.
Conflicts that never reach resolution drain team energy and stall progress. Senior engineers understand when to stop debating and make a call, even if it's not their preferred option.
What this looks like:
"I suggested we timebox the discussion to one more meeting and then make a decision."
"I proposed that we try their approach for two weeks and then reassess based on results."
"I worked with the team lead to establish clear criteria for making the final call."
Why interviewers love this: This shows you balance perfectionism with pragmatism and understand that good decisions made quickly often beat perfect decisions made slowly.
Red flag alternative: "We never really resolved it—we just kind of moved on to other things."
Putting It All Together
The most compelling conflict stories demonstrate multiple actions from this list. Here's how they might sound in combination:
"When my teammate proposed using MongoDB for our analytics pipeline [Context], I wanted to understand his reasoning first [Action #2], so I asked him to walk me through the performance requirements he was optimizing for. I realized we had different assumptions about query patterns [empathy], so I built a quick benchmark comparing MongoDB and PostgreSQL with some sample data [Action #3]. The results showed PostgreSQL would be 10% faster for our read-heavy workload, so I shared these findings in our next architecture review [Action #4]. He appreciated the data-driven approach and we aligned on PostgreSQL [Action #5]. The system launched on time and has handled our scale beautifully [Result]."
Your Action Audit
Review your conflict story and identify which of these seven actions you can highlight:
✅ Did you proactively raise the concern?
✅ Did you seek to understand their perspective first?
✅ Did you use data or evidence to inform the decision?
✅ Did you choose appropriate communication channels?
✅ Did you demonstrate empathy and preserve the relationship?
✅ Did you involve the right people at the right time?
✅ Did you drive to a clear resolution?
If your story only demonstrates 1-2 of these actions, you might want to choose a different conflict. The best stories show 4-5 of these behaviors clearly.
Remember: conflicts are inevitable in any high-performing team. What matters isn't whether you have them—it's how skillfully you navigate them.