Tell me about a time you disagreed with a teammate

Framework

1. S — Situation: 1 sentence setting the scene (concrete: what feature, what stakes)
2. T — Task: your specific responsibility / what was on the line
3. A — Action: focus 60% of your answer here. What did YOU do? Not 'we'.
4. R — Result: quantified outcome. Even better: what you learned.
5. Pick a real conflict (a disagreement, not a personal feud)
6. Show empathy for the other person's position

Sample answer

At Stripe, our team was split on whether to ship the new payouts UX as a
ramped rollout or a hard cutover (S). I was the tech lead and had to make
the call (T). My senior engineer pushed hard for hard-cutover; she argued
ramping would double the testing surface and slow us down by a sprint.

I asked her to walk me through the worst case for both paths (A). On
cutover, a regression would have hit 100% of merchants on launch day. On
ramp, we'd catch issues at 1% before they scaled. I asked her to estimate
the prob of a regression — she said 'low but non-zero.' That's the answer.
We ramped. I made sure she got credit in the launch retro for surfacing
the testing concern, and we built a one-command rollout script that
addressed her real complaint about testing overhead.

We rolled out over 9 days. We caught and fixed two real regressions at the
1% stage that would have hit every merchant on cutover day (R). She agreed
the ramp was the right call. I learned to push for the data underneath
strong opinions instead of trying to negotiate at the level of the
opinion.

Common pitfalls

• Picking a conflict where you were obviously right — sounds smug
• Saying 'we' when they want to hear what YOU did
• Skipping the Result — leaves the story unfinished