The Product Manager (PM) is the person responsible for what the team builds and why: they identify the user problems worth solving, set priorities and make sure the delivered product creates value for customers and for the company.
Their work is split between:
- discovery: user interviews, data analysis, competitive research
- prioritization: choosing what to do, and above all what not to do, in line with strategy
- delivery: working with developers and designers so the right features ship
- measurement: checking the real impact of what was delivered
They usually have no line authority over the team: they persuade through the clarity of their vision and the quality of their arguments.
It differs from the Product Owner, a role defined by Scrum and more focused on managing the team's backlog, although the two are often confused in job ads.
Why it matters when hiring
The first PM often arrives when founders can no longer carry the product vision alone, usually after the first customers. The strong signal on a resume: well-argued product decisions and measured results, not a list of shipped features. In the interview, ask them to describe a feature that was dropped and why. Do not confuse a PM with a project manager: the former chooses what to do, the latter organizes how.