How to Answer: "How do you handle disagreements with a Product Manager?"

“When I disagree with a Product Manager, I start by separating business goals from technical implementation. For example, on a recent project, our PM wanted to launch a real-time analytics feature in two weeks. Building it live would have degraded our core database performance. Instead of shutting down the idea, I quantified the risk—showing that peak load could increase API latency by 40%. I presented two alternatives: a cached hourly rollup that could ship in two weeks, or the true real-time feature delivered in four weeks. By framing the discussion around user latency and delivery risk, we agreed on the phased approach, launching v1 on time while protecting platform stability.”

“I focus on active listening and shared metrics. If a PM proposes a feature deadline that I feel is unrealistic without sacrificing quality, I schedule a 1-on-1 to review the scope together. I break down the engineering complexity into clear components and highlight where technical trade-offs exist. By offering a MVP option that satisfies 80% of the user requirement in the target timeframe, we usually find common ground without compromising on system stability.”

“I try to understand the user impact behind the PM's request first. If I see a potential issue or disagreement, I ask clarifying questions to ensure I'm not missing context. Then I present data or code examples to my senior engineer or PM to explain my concern clearly and work together on the best solution.”