Product and projects · Job description template
Product Manager job description template
Without a product manager, the most senior voice often decides what to build, and requests from loud customers win over the ones that matter most. The product manager decides what the team builds next and why, based on evidence from customers and data. They are accountable for whether the features shipped actually change customer behaviour and revenue, not for running the schedule.
First-year outcomes
What should be visibly different a year from now. Results, not tasks.
- A written product strategy and a quarterly roadmap exist, and the CEO and engineering lead agree it reflects their priorities.
- Every major feature released has a success measure set before build, and a review of results is shared within 60 days of launch.
- Monthly retention of new customers improves from the starting rate to an agreed target, such as from 70 percent to 80 percent at day 90.
- At least eight customer interviews are held each month, and the findings are stored where the whole team can search them.
- Feature requests from sales and support go through one intake process, and each requester gets a decision with a reason within two weeks.
The work
Recurring work
- Interview customers and prospects about their problems and current workarounds.
- Write problem statements and requirements for the engineering team.
- Prioritise the backlog using evidence on customer value and effort.
- Review product analytics and report on adoption of recent features.
- Explain decisions on the roadmap to sales, support and leadership.
Projects
- Write the product strategy and first quarterly roadmap.
- Set up a single intake process for feature requests.
- Lead a discovery project on why new customers leave in their first 90 days.
Decisions they own
- What goes on the roadmap and in what order.
- What problem a feature solves and what is out of scope.
- The success measure for each feature and whether to keep, change or remove it after review.
People they work with
- The CEO or head of the business unit, to align the roadmap with company goals.
- Engineering and design, to shape solutions and agree trade-offs.
- Sales and customer support, who bring requests and customer evidence.
- Customers, through interviews, tests and feedback.
Requirements
Essential on day one
- Experience deciding what to build and showing evidence for those decisions.
- Skill at interviewing customers without leading them to the answer.
- Clear writing: requirements and decision notes others can act on.
- Comfort reading product data and asking the right questions of it.
Helpful, but can be learned
- Our market, customers and competitors.
- Product analytics tools such as Mixpanel or Amplitude.
- Writing basic queries in SQL.
- Our engineering workflow and release process.
How to assess it
One piece of evidence for each first-year outcome.
| Outcome | Evidence to look for |
|---|---|
| A strategy and roadmap leadership agrees with | Ask for a roadmap they wrote and how they got agreement. Good looks like clear goals linked to each item and a story of handling a disagreement with a senior person. |
| Success measures and post-launch reviews | Ask about a feature that did not work. Good candidates set the measure early, noticed the result and changed or removed the feature. |
| Day-90 retention improved | Give a short case: here is our retention data, what would you investigate first. Good looks like hypotheses, a plan to test them and the data they would need. |
| Eight customer interviews a month | Run a ten-minute mock interview with a staff member playing a customer. Good looks like open questions about past behaviour, not questions about features. |
| One intake process with decisions in two weeks | Ask how they handled competing requests from sales and support. Good answers show a visible process and saying no with reasons. |
Opening for the job ad
We build a lot, but we are not always sure we build the right things. In your first year you will set our product strategy, talk to customers every week, and make sure every feature we release has a clear measure of success. If you would rather decide what to build from evidence than from the loudest request, read on.
Turning this into an ad? See how to write a job ad that gets applicants.
Next: interview for these outcomes
Eight structured questions for this role, each tied to an outcome above.
Product Manager interview questionsSimilar roles
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.