← Google Interview Insights

Google·Product Manager·Onsite - Product Sense / Strategy·Senior

Senior
Apr 2026

Summary

Interviewed for a PM role at Google and got hit with a classic stakeholder conflict question that sounds straightforward but really isn't once you're sitting in the room.

Questions Asked (1)

Q1

When product requirements conflict with each other, how do you resolve that, and who actually gets the final say on priority?

Conflict ResolutionStakeholder ManagementRoadmap Prioritization
Author's notes

I went straight to a framework about business impact vs user impact and kind of forgot to address the second half of the question, which is the harder part.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by framing conflicts as opportunities to align on shared goals, then walk through a structured process for resolving them. Emphasize that while you facilitate and recommend, the final prioritization decision often rests with a cross-functional leadership group or the executive sponsor, depending on the scope.

Pro tip: At Google, decisions are data-driven and consensus-oriented, but when consensus fails, the PM often escalates to a VP or the product area lead. Show you know when to escalate and how to do it constructively.

1. Clarify the conflict

Identify the specific requirements in conflict and the underlying goals or user needs each serves. Ensure all parties agree on the problem before debating solutions.

2. Gather data and perspectives

Collect quantitative data (e.g., user impact, revenue, effort) and qualitative input from stakeholders. Use frameworks like RICE or weighted scoring to evaluate trade-offs objectively.

3. Facilitate a decision-making discussion

Bring stakeholders together to review data and discuss trade-offs. Aim for consensus, but be prepared to make a recommendation if consensus isn't reached.

4. Escalate if needed

If consensus remains elusive, escalate to the appropriate decision-maker (e.g., product lead, VP, or executive sponsor) with a clear summary of options and your recommendation.

5. Communicate and document the decision

Once a decision is made, communicate it transparently to all stakeholders and document the rationale. Ensure everyone understands the final priority and next steps.

Key Points to Mention

  • Alignment on overarching product vision and company goals
  • Use of data and objective frameworks (e.g., RICE, Kano) to evaluate trade-offs
  • Stakeholder management and building consensus
  • Clear escalation path and knowing when to involve leadership
  • Transparent communication and documentation of decisions
  • The role of the PM as a facilitator and recommender, not sole decision-maker

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.