Product Manager interview question
How do you build a product roadmap?
Build a roadmap around outcomes and strategic problems, not a fixed feature calendar. Show evidence, sequencing constraints, confidence and time horizon, reserve capacity for learning and reliability, and update it as assumptions change.
Direct answer
What a strong answer covers
How it works
A roadmap communicates where the product is going and why, in a form that survives contact with reality. It is organised around outcomes and the problems being solved rather than dated feature promises, with the evidence behind each item, its confidence level, and its horizon: committed for the next quarter, planned for the next two, and exploring beyond. Sequencing shows dependencies and platform work. Capacity is explicitly reserved for learning, reliability, and the unexpected, because a roadmap that allocates 100 percent is fiction. It is reviewed on a cadence and changed when assumptions change, with the changes explained rather than quietly rewritten.
Example
A B2B roadmap listed three outcomes for the year: cut onboarding time in half, reach 99.9 percent uptime on the API, and open the mid-market segment. Under each, the next quarter showed committed problems with evidence links, the following quarters showed candidates with confidence ratings, and 25 percent of capacity was marked for reliability and discovery. When a large prospect demanded a feature, the trade-off was shown against the onboarding outcome and declined with reasoning stakeholders could read.
Common mistakes
- Publishing a feature list with dates that becomes a contract nobody can keep.
- Allocating every hour of the year and leaving no room for what is learned.
- Changing the roadmap silently so stakeholders lose trust in it.
A useful answer structure
Answer from your own work.
Do not memorise a script: use only examples you can explain honestly in follow-up questions.
Open the desktop workspace and rehearse a clear answer in your own words.