← Google Interview Insights

Google·Technical Product Manager·Hiring Manager Screen·Senior

Senior
May 2026

Summary

Google TPM interview with a classic resource constraint scenario. One question, no fluff, just a situation designed to see if you'll push back or fold.

Questions Asked (1)

Q1

You need to deliver 12 features in 6 months, but your team can realistically only build 6 in that time. Stakeholders refuse to move the deadline, cut scope, or add budget. What do you do?

Stakeholder ManagementRoadmap PrioritizationAdaptability & Ambiguity
Author's notes

The constraint here is that all three levers are locked, which is the whole point.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Acknowledge the constraints and reframe the problem as a prioritization challenge, not a capacity one. Propose a data-driven framework to evaluate features based on impact and effort, and facilitate stakeholder alignment on the top 6 features that deliver the most value. Commit to delivering those 6 exceptionally well while creating a transparent backlog for the rest.

Pro tip: Don't just present a prioritization framework—show how you'd use it to drive a decision with stakeholders, including handling disagreements and securing buy-in. Emphasize that delivering 6 high-impact features is better than 12 mediocre ones, and tie it back to user and business outcomes.

1. Acknowledge and Reframe

Acknowledge the constraints and reframe the challenge as an opportunity to focus on highest-impact work. Emphasize that delivering fewer features well is better than many poorly.

2. Prioritize with Data

Use a prioritization framework (e.g., RICE, WSJF) to objectively rank features by impact, effort, and strategic alignment. Gather data on user needs, business value, and technical feasibility.

3. Align Stakeholders

Facilitate a workshop to review the prioritization and agree on the top 6 features. Address concerns by showing trade-offs and the cost of trying to do all 12.

4. Commit and Communicate

Commit to delivering the top 6 with high quality and set clear expectations. Create a transparent roadmap for the remaining features, with a plan to revisit after the 6 months.

5. Monitor and Adapt

Track progress and be ready to adjust if priorities change. Keep stakeholders informed with regular updates and celebrate the delivery of the selected features.

Key Points to Mention

  • Prioritization frameworks like RICE or WSJF to make objective decisions
  • Stakeholder alignment through transparent communication and trade-off discussions
  • Focus on delivering high-impact features rather than spreading thin
  • The cost of context switching and trying to do too much
  • Creating a transparent backlog for future consideration
  • Tying features to user and business outcomes to justify prioritization

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