Strategy question
This is an interview question, with a few sub-questions I was able to get after asking them: How would you determine the roadmap for a product? (Assume any product and any feature). What are the key criteria's/aspects you will consider to create this road map? How much weight will your roadmap have for user-driven features?
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Understanding of how PMs build and weight a roadmap across strategic, user, and data-driven inputs.
How to approach it
- Confirm the specific product and current strategic goal with the interviewer, since roadmap weighting depends heavily on stage and priorities.
- Gather inputs: company strategic goals, user research and support feedback, usage data, and competitive gaps.
- Score candidate initiatives against a consistent framework, such as impact versus effort, or reach, impact, confidence, and effort (RICE).
- Weight user-driven requests meaningfully, roughly a third to half of roadmap capacity, but not the majority, since users rarely see the full strategic picture.
- Balance with must-do technical debt, strategic bets, and quick wins, ensuring the roadmap isn't 100% reactive.
- Revisit the roadmap quarterly against new data rather than treating it as fixed.
What a strong answer includes
- Gives a concrete weighting, e.g. roughly 40% user-driven, 30% strategic bets, 20% technical health, 10% quick wins, clearly marked as an illustrative split.
- Explains why user requests alone can't drive the majority of a roadmap, since vocal users are not always representative.
- Names a specific framework (RICE or similar) rather than a vague 'we prioritize by impact.'
- Shows how the roadmap adapts when new data (like a metric drop) forces reprioritization mid-quarter.
Common mistakes
- Giving a generic answer with no framework or concrete weighting.
- Treating user-driven features as either everything or nothing, instead of a bounded share.
Likely follow-up questions
- How would you handle a strong executive request that conflicts with your roadmap?
- How often would you revisit and re-prioritize the roadmap?
More strategy questions
- How would you launch (roll out) Amazon Go?Amazon · Strategy · Hard
- Imagine you're a PM at Amazon and you're working on a partnership with Facebook that has the goal of leveraging FB's friend network to drive Amazon sales. Walk through the lifecycle for building this integration/partnership.Amazon · Strategy · Hard
- How will you reduce Paypal's operating costs by 50%?PayPal · Strategy · Hard
- Define a strategy of loyalty program for Google Pay.Google · Strategy · Hard
- How would you determine if a specific block in your neighborhood is suitable for a new grocery store?Shopify · Strategy · Medium
- Compare Amazon Prime, Netflix and Hotstar. Which is your favorite and why?Amazon · Strategy · Easy
More questions from these companies
- Amazon PM interview questions
- Airbnb PM interview questions
- YouTube PM interview questions
- LinkedIn PM interview questions
- Meta PM interview questions
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop