What makes a good product roadmap?
What the interviewer wants to hear
- Connected to strategy and outcomes, not just features
- Prioritised themes or problems with clear reasons
- Honest about confidence; near term detailed, later flexible
- Tailored for different audiences
- Reviewed and updated regularly
Model answer
A good roadmap tells a story of where the product is going and why. It starts from strategy and goals, so items are framed as problems or outcomes, like "reduce time to first invoice", rather than a long list of features. Each theme has a reason linked to customer evidence or business goals. It is honest about certainty: the next few weeks can be fairly detailed, while later items stay broad, which is why I like a Now, Next, Later format with dates only where we have committed. I adapt the view for the audience: executives care about outcomes and investment, sales wants to know what customers can expect, and engineers need more detail. Finally, it is a living document. I review it regularly as we learn and communicate changes and the reasons behind them.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy Product Manager questions
- In your own words, what does a product manager do?
- How do you decide which features to build first?
- What is an MVP? Give an example of how you would build one.
- How do you work with engineers and designers?
- Pick a product you use often. How would you improve it?
- Explain how an A/B test works and when you would use one.
- How do you write user stories and acceptance criteria that your team can build from?
- What is the product manager's role in agile ceremonies like planning, stand-ups, reviews and retrospectives?
- Customers send feedback through support, sales, reviews and surveys. How do you use it?