Conflict Resolution Framework

The STAR-C Framework

When answering conflict questions, structure your response: Situation → Task → Action → Result → Closure (what you learned).

Common Conflict Scenarios

1. Technical Disagreement on Architecture

Situation: Team split on microservices vs monolith for a new feature.

Good approach: "I proposed we spike both approaches for 2 days, then present pros/cons with metrics (latency, deployment complexity, team velocity). We documented trade-offs in a decision record, voted, and the lead made final call. I supported the decision even though it wasn't my preference."

Why it works: Data-driven, time-boxed, documented, shows maturity.

2. Prioritization Conflict with PM

Situation: PM wants new feature, but tech debt is causing weekly incidents.

Good approach: "I quantified the cost: 10 hours/week firefighting, 3 customer escalations/month. Proposed compromise: 2 sprints of tech debt + monitoring, then feature work. PM agreed after seeing incident metrics. Tech debt work reduced incidents by 80%."

Why it works: Business impact quantified, compromise offered, outcome measured.

3. Code Review Conflict

Situation: Senior engineer repeatedly blocking your PRs over style preferences.

Good approach: "I requested 1:1 to understand their concerns. Turns out they had context on a past outage caused by similar patterns. We agreed to document the pattern in team guidelines with rationale. I refactored the code and they approved."

Why it works: Assumed positive intent, sought to understand, created shared documentation.

Red Flags to Avoid

• Blaming: "The PM was being unreasonable..."
• Ego: "I was clearly right, but they didn't listen..."
• Escalating too fast: "I immediately went to their manager..."
• Avoiding: "I just let them have their way to avoid drama..."

Key Principles

1. Assume positive intent: Everyone wants the product to succeed
2. Focus on data, not opinions: Metrics > gut feelings
3. Seek to understand first: Ask "help me understand your concern"
4. Propose compromises: Rarely all-or-nothing
5. Document decisions: Write down trade-offs and rationale

Practice Questions

• Tell me about a time you disagreed with a technical decision.
• Describe a conflict with a coworker and how you resolved it.
• How do you handle code review feedback you disagree with?
• Tell me about a time you had to convince a team to change direction.