# Conflict and Disagreement — Part 1: Disagreeing Well

Every team disagrees. Interviewers ask about conflict to learn whether you can **disagree on substance without damaging relationships**, change your mind when the evidence says so, and **commit** once a decision is made. Seniors are also expected to resolve conflict between others.

![Healthy conflict resolution: understand, find shared goals, compare options with data, decide, commit](diagrams/01-conflict.svg)

## 1. Typical Questions

- "Tell me about a time you disagreed with your manager."
- "Tell me about a conflict with a teammate. How was it resolved?"
- "Tell me about a time you disagreed with a decision but went ahead with it."
- "Describe a time you received pushback on your design."
- "Have you ever had to deal with a difficult stakeholder?"

## 2. What a Strong Answer Shows

| Signal | Sounds like |
|---|---|
| **Curiosity first** | "I asked what they were optimizing for; it turned out they were worried about on-call load." |
| **Shared goal** | "We both wanted fewer incidents; we disagreed on how." |
| **Evidence over opinion** | "I proposed a one-day spike so we could compare with real numbers." |
| **Private and respectful** | "I raised it 1:1 first, not in the review meeting." |
| **Willing to be wrong** | "Their benchmark showed my approach was slower, so I dropped it." |
| **Disagree and commit** | "We went with their design; I helped make it succeed." |
| **Relationship intact** | "We still pair regularly." |

## 3. A Resolution Playbook

1. **Understand**: restate their position until they agree you got it right.
2. **Find the shared goal** and the real constraint behind each position.
3. **Make options concrete**: a short doc or table with the trade-offs of each.
4. **Get data** cheaply: a spike, a benchmark, a user test, a cost estimate.
5. **Decide** with the right decision-maker (owner, tech lead, manager) if you can't agree. Escalation is fine when it's framed as "we need a decision", not "they're wrong".
6. **Commit** fully, and agree on a signal that would make you revisit it.

## 4. Choosing the Story

The best conflict stories have **real stakes** (a design, a deadline, a quality bar), a **reasonable counterpart** (not a villain), and an outcome where you **learned something**. Stories where you were partly wrong are often the strongest.

Avoid: interpersonal drama, stories where the other person was simply incompetent, or "I've never had a conflict" (it reads as either conflict-avoidant or lacking self-awareness).

## Common Pitfalls

1. **Villain stories**: making the other person look bad makes *you* look bad.
2. **Winning as the goal**: the story ends with "and I was right". Interviewers want to see the relationship and the outcome.
3. **Escalating as a first step** instead of talking directly.
4. **Silent compliance**: "I disagreed but said nothing" fails the courage test.
5. **No resolution**: the story stops at the argument.

## Quick Reference

```text
Understand → shared goal → concrete options → cheap data → decide → commit
Be curious, private, evidence-driven and willing to be wrong
Escalate as "we need a decision", never as "they're wrong"
Best stories: real stakes, reasonable counterpart, you learned something
```