Handling a Product Manager Requirement You Strongly Disagree With
Company: Docker
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Technical Screen
In a hiring-manager round for a senior software engineer role, made up mostly of behavioral questions and deep dives into past work, you are asked:
"Suppose a product manager proposes a requirement that you clearly disagree with. How do you handle it? Do you have a real story like that?"
The interviewer wants an actual example, not only a general process. Prepare one in advance even if your current team has no product manager: in the reported interview, a candidate who had never worked with one and tried to improvise a loosely related story had the question skipped.
```hint Separate the goal from the request
Before deciding how to push back, ask what user or business problem the requirement is meant to solve. Is your disagreement with that goal, or with this particular way of reaching it?
```
```hint Decide how the disagreement ends
Think about what evidence would let the product manager decide together with you, who makes the final call, and what you did after the decision was made.
```
### Clarifying Questions
- Should the story involve a product manager specifically, or does another requirement owner, such as a customer-facing team or a partner team, count?
- Is a story in which the final decision went against you acceptable, or should it show the disagreement resolved your way?
- How much technical detail about the requirement is useful in this round?
### What a Strong Answer Covers
- A specific, real situation: the requirement, why you disagreed (cost, risk, user impact, long-term maintenance), and what was at stake
- Understanding the product manager's goal and constraints before arguing against the proposal
- Pushback grounded in evidence (data, estimates, a prototype) and an alternative that meets the same goal
- A deliberate choice of forum and of whether to escalate, respecting the product manager's ownership of the decision
- The outcome and how you acted afterwards, including committing fully to a decision you had argued against
- Reflection on what you learned and on the working relationship, at a scope that fits a senior engineer
### Follow-up Questions
- What would you have done if the product manager still insisted after seeing your evidence?
- Tell me about a disagreement like this in which you turned out to be wrong.
- How would you handle a requirement that had already been promised to a customer for a fixed date?
- How did you keep the disagreement from damaging your relationship with the product manager?
Overview: A behavioral question from a senior software engineer hiring-manager round: how do you handle a product manager's requirement that you clearly disagree with, told through a real example. It tests understanding the goal behind a request, evidence-based pushback, escalation judgment and committing to the final decision.
Read the full Docker Software Engineer interview experience this question came from