Conflict with a Teammate

The question — "Tell me about a time you had a conflict with a teammate." Variants: "Describe a time you disagreed with a colleague.", "Tell me about a time you had to work through a difficult interpersonal situation at work."

What they're assessing — Handling interpersonal conflict maturely; empathy and ability to see the other person's perspective; clear, direct communication; putting the shared goal and outcome above personal ego; reaching genuine resolution rather than avoidance.

STAR-L scaffold

Fill in your own story:

• Situation — Describe the team context and how the conflict surfaced. What were the stakes and who was involved?
• Task — What did you personally need to achieve, and why did the disagreement matter to the outcome?
• Action — How did you initiate a direct conversation? What did you do to understand the other person's view? How did you propose a path forward — use "I", not "we", and name the specific behaviors (e.g., scheduled a 1:1, listened without interrupting, suggested a time-boxed spike to test both approaches)?
• Result — What was the concrete outcome? Was the conflict resolved? Did the work ship? Quantify if possible (e.g., decision reached in 2 days, no schedule impact).
• Learned — What did this change about how you handle disagreements? What do you do differently now (e.g., raise concerns earlier, separate the idea from the person)?

Pitfalls / red flags

• Framing the other person as the villain and yourself as entirely right — interviewers notice hero-vs-villain narratives.
• Saying "we resolved it" without explaining what you specifically did — use "I".
• Describing avoidance rather than resolution (e.g., "we just moved on").
• No mention of empathy or understanding the other side's reasoning.

Example (generic — replace with your own)

Situation: On a backend team of four, a colleague and I disagreed on whether to introduce a new event-sourcing pattern for a feature with a two-week deadline. He wanted the pattern for long-term flexibility; I was concerned about the learning curve and schedule risk.

Task: I needed us to reach a technical decision quickly without damaging our working relationship or delaying the sprint.

Action: I asked him for a 30-minute 1:1 to understand his reasoning fully before sharing my concerns. After listening, I proposed a small time-boxed spike — two days, both of us — to prototype the event-sourcing approach against our acceptance criteria. I framed it as "let the data decide" so neither of us had to back down based on opinion alone.

Result: The spike showed the pattern added three days of complexity we couldn't absorb. We both agreed to use the simpler approach. The feature shipped on time and our relationship stayed strong — we actually collaborated closely on the next sprint.

Learned: I learned to separate the idea from the person early. Now when I sense a brewing technical disagreement, I explicitly invite the other person to walk me through their reasoning first — it almost always surfaces a valid concern I hadn't considered, and it makes the conversation collaborative rather than adversarial.