Conflict & Disagreement
Intermediate · 14 min read · Question Bank by Theme, Working With People
Disagreeing with a peer or manager, and resolving it with data and respect.
Conflict questions are in almost every behavioral loop, because every team disagrees and the way you handle it decides whether people want to work with you. The interviewer isn't hoping you've never had a conflict. Someone who claims that is either inexperienced or not being honest.
The question in its many forms
What they're scoring
Choosing the story
The shape of a strong conflict answer
Weak vs strong
Weak: "Our tech lead wanted to use MongoDB for the new service, which was obviously wrong because our data was relational. I told him in the meeting that it was a bad idea. Eventually the manager agreed with me and we used Postgres. It worked out fine."
If you lost the argument
That's a great story too. Show that you committed fully: "I still thought the cache added risk, but the decision was made, so I wrote the invalidation tests myself and owned the rollout." If you turned out to be right, say what you did then. Constructive answers propose a fix, not "I told you so".
At senior and staff level
At senior levels, conflicts are less about one design and more about direction, priorities and organisational trade-offs. The interviewer is looking for whether you can disagree with senior leaders constructively and change a decision at a larger scale.
Follow-ups to expect
Further reading
Key takeaways
- They want open, respectful, evidence-based disagreement, followed by full commitment.
- Show that you understood the other side's reasons before arguing your own.
- Prefer a private conversation plus data over public confrontation or escalation.
- A story you lost, then committed to, can be stronger than one you won.