Tell me about a time you disagreed with a teammate.
Break down this behavioral question with a model STAR answer, the pitfalls that cost candidates points, and the follow-up questions worth rehearsing next.
A strong STAR example answer
The compromise shipped in five weeks, conversion ticked up, and the engineer I had clashed with became the colleague I now call first when a decision feels one-sided. That is the short version of a scope fight on a checkout redesign — and the relationship coming out stronger is the part I am proudest of.
He was the senior engineer, arguing for a full rewrite of the legacy payment code. I owned the feature and wanted an incremental improvement in a fraction of the time. The tension was real; standups got terse and the team could feel it. Rather than escalate, I asked him to walk me through his technical concerns one-on-one, away from the audience. His real worry — that the old payment module made even small changes risky — was legitimate, and I had underestimated it.
So we split the difference: he got time to build a thin abstraction layer over the payment module first, and we shipped the UI improvement on top of it. I took that plan to our manager with the revenue risk of slipping a full quarter, and she approved it. The abstraction later cut integration bugs noticeably. My takeaway: most disagreements are about a risk someone has not said out loud yet. Surface the risk, and the fight shrinks to its real size.
How to structure your own answer
- Situation: Set up the project and the nature of the disagreement.
- Task: Clarify your role and what was at stake.
- Action: Explain how you made your case and sought a resolution.
- Result: Share the outcome and what you learned about collaboration.
Common mistakes to avoid
- Don't cast the teammate as the villain — interviewers are listening for maturity, not victory stories.
- A trivial disagreement about code style reveals nothing about your judgment; pick one with real stakes.
- The answer dies when the resolution is vague — how you settled it is the whole point.
- Why claim you were simply right? A story with no concession or learning reads as self-serving.
Follow-up questions to prepare for
Expect the interviewer to dig past your first answer. Common follow-ups for this question include:
- What would you do differently if the same disagreement happened today?
- Has a teammate ever changed your mind completely? Tell me about it.
- How do you handle disagreements with someone more senior than you?
Related practice questions
Keep drilling with these, or browse the complete question bank.
Describe a time you had to meet a tight deadline.
Tell me about a time you took initiative beyond your assigned role.
Related guides
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator