Strategy question
How would you prioritize features for the next version of Messenger?
- Slack
- Strategy
- Hard
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
Prioritization framework: can you apply a clear framework (impact vs effort, strategic fit) to rank features rather than listing preferences.
How to approach it
- Clarify scope: Messenger's next version, and confirm what 'features' are under consideration (assume a candidate set if none given).
- State the framework: score each feature on user impact, reach (how many users affected), and implementation effort/risk.
- Weigh strategic fit: does the feature support Messenger's core job (fast, reliable messaging) or is it a distraction (e.g. games, unrelated add-ons).
- Rank a sample set: reliability/speed improvements first (foundational), then a high-reach feature (e.g. better group chat tools), then a niche feature last.
- Explain tradeoffs: a flashy but low-reach feature loses to a boring but high-impact reliability fix.
- State how you'd validate the ranking: usage data on pain points, and a lightweight test before full build.
What a strong answer includes
- Uses an explicit framework (impact, reach, effort, strategic fit) instead of intuition-based ranking.
- Prioritizes core reliability/speed over flashy features, recognizing messaging apps live or die on dependability.
- Gives a concrete example ranking with reasoning for each tier, not just an abstract framework with no application.
- Notes how the ranking would be validated with real usage data, not just interviewer intuition.
Common mistakes
- Ranking features by gut feeling without a stated framework.
- Prioritizing novel/exciting features over foundational reliability, which is usually wrong for a messaging product.
Likely follow-up questions
- How would you handle a high-impact feature that also carries high technical risk?
- Who else would you involve in this prioritization decision?
More strategy questions
- What should be Slack's product strategy for the next 3 years?Adobe · Strategy · Hard
- You are a Product Manager for a B2B enterprise product. You need to do a competitor analysis but the products of your competitors are not openly accessible without a long drawn sales negotiation. How do you go about it?Slack · Strategy · Medium
- Slack recently launched SlackShare, a competitor to Loom. You lead the Growth Charter for Loom and are seeing a steady decline in usage of the core Loom product because of this launch by Slack. Devise a growth strategy that turns around this decline in usage of Loom. Cover: 1. Segmentation, Targeting and Positioning 2. How will you drive adoption? 3. Success criteria and MetricsPayPal · Strategy · Hard
- Google Keep is a free product to save, share notes etc. How would you make it a subscription product & monetize it?Google · Strategy · Hard
- How would you launch (roll out) Amazon Go?Amazon · Strategy · Hard
- With an unlimited network bandwidth what would you build?Google · Strategy · Hard
More questions from Slack
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