Tell Me About a Time You and a Product Manager Disagreed on What to Build
Behavioral and LeadershipCross-Functional CollaborationAsked atMidSeniorUpdated
“Tell me about a time you and a PM had different views on what to build.”
They're checking how you work through a disagreement with product. Strong answers respect what the PM knew, settle the question with evidence, and commit once it's decided.
Rubric by Level
Junior
- Raised your concern with the PM directly, with a reason.
- Listened to the user or business reason behind the request.
- Built what was agreed and shared what you learned.
Mid
- Shows respect for the PM's role and the information you didn't have.
- Made the case with data, prototypes, or user feedback.
- Reached a decision and committed to it.
- Wrote the decision down so it could be revisited if assumptions changed.
Senior
- The disagreement was about a roadmap item or a large investment.
- Proposed a test, like an experiment or a staged launch, that let data decide.
- Shows the partnership got stronger afterward.
Principal
- Shaped product strategy with executives, using technical insight.
- Explains a bet where you and product leadership disagreed and how it resolved.
- Shows how the decision played out over a year or more.
Red Flags
- Treated PM as 'not technical' or dismissed their input.
- Built what you wanted instead of what was agreed.
Follow-Ups to Expect
- What did the PM know that you didn't?
- How did you handle it when the data went against you?
A Story Shape That Holds Up
The Two Views
What the PM wanted, what you wanted, and why.
What They Knew
The context the PM had that you didn't.
Settling It
The evidence or test that decided it.
After the Call
How you committed, and how it turned out.