Updated September 2026
A strong startup product manager job description says which product decisions move from the founder to the new hire and which stay with the founder. It describes the customers they will talk to, the team they will ship with and the outcomes expected in six months, lists at most six must-haves including how technical they need to be, and gives salary and equity ranges.
Most first product managers join a company where the founder has owned the product since day one. The JD is your chance to agree, before anyone is hired, how that handover will work.
Copy-and-paste product manager job description
About [Company]
[Company] helps [customer] to [outcome]. We're [number] people, backed by [investors], with [number] customers using the product. Until now, [founder name] has run product.
The role
You'll be our [first] product manager, working with [number] engineers and [a designer / no designer yet]. You'll own [area, e.g. the core workflow, onboarding] and the roadmap for it. [Founder name] will keep [e.g. overall product vision and pricing]; you'll own [e.g. discovery, prioritisation and what ships each cycle]. You report to [name].
What you'll do in your first 6 months
- Talk to [number] customers a month and share what you learn with the whole team.
- Set up a planning rhythm the engineers trust, with clear priorities each [cycle / sprint].
- Ship [named initiative] and move [metric, e.g. activation, retention in the first month].
- Put basic product analytics in place so decisions rely on data as well as opinion.
- Work with [sales / customer success] so launches land with customers.
What you'll bring
- You've shipped products that customers used and can show what changed because of your work.
- You run customer interviews well and turn them into decisions.
- You can [technical bar, e.g. read our API docs, write basic SQL, discuss trade-offs with engineers].
- You write clear, short specs and know when a sketch is enough.
- You've said no to a senior stakeholder and kept the relationship.
- Experience with [B2B / B2C / your market] products.
Nice to have
- You've been the first product manager somewhere.
- Experience in [industry].
- You've done some design or research work yourself.
What we offer
- Salary: [£/$/€ X to Y].
- Equity: [X% to Y%], [vesting schedule].
- [Remote / hybrid, X days in City].
- Stage: [Seed / Series A / Series B]. [Benefits].
Our free job description builder gives you a first draft if you prefer. For interviews, use our product manager interview questions, built around the scorecard below.
How the role changes by stage
| Seed | Series A | Series B | |
|---|---|---|---|
| Do you need one? | Often not yet; a product-minded engineer or designer may fit better | Usually the right time for the first PM | Several PMs, perhaps a head of product |
| Scope | The whole product | The whole product or one core area | One area or team |
| Support around them | None: they do research, analytics and launch notes | A designer, some data help | Design, data and product marketing partners |
| Founder's role | Still makes most calls | Sets vision, hands over priorities | Sets strategy with the head of product |
Scorecard: how you'll judge success
| Outcome | What good looks like at 12 months | How you'll test it in interviews |
|---|---|---|
| Customer discovery | A steady rhythm of customer conversations that visibly shapes the roadmap | Ask about their last five customer conversations and what changed |
| Prioritisation | A roadmap the team and founder understand and mostly agree with | Give them your real backlog and ask for the next cycle |
| Shipping with engineering | Predictable cycles; engineers say specs are clear and short | Ask an engineer from their last team (reference) |
| Outcomes | Named metrics moved, not just features shipped | Ask which of their launches failed and how they knew |
| Founder handover | The founder spends less time on day-to-day product decisions | Final conversation about decision rights |
30-60-90 day plan
| Days | Focus | By the end they should have |
|---|---|---|
| 1 to 30 | Listen: at least [number] customer calls, time with sales and support, read the backlog | A short write-up of what customers need and where the product falls short |
| 31 to 60 | Take over prioritisation for [area] with the founder; set the planning rhythm | A roadmap for the next quarter and the first cycle planned by them |
| 61 to 90 | Ship the first initiative they chose; put tracking in place | A launch with measured results and a clear list of what's next |
Mistakes founders make in product manager job descriptions
Hiring a PM to take work, not decisions. If you want someone to write tickets for your ideas, you need a project manager or delivery lead. Strong product managers spot this in the first interview.
Being vague about "technical". Some teams need a PM who can read code; most need one who can follow a technical trade-off and ask good questions. Say which.
Copying a big-company PM job. Large companies surround PMs with researchers, analysts and product marketers. At a startup the PM does much of that alone, so ask for people who have.
Where Funded.club fits
We've helped 500+ startups from Seed to Series D across North America, Europe and APAC, including product hires. Funded.club agrees a low fixed fee upfront, averaging 6 to 9% of salary, from $4,900 to $21,900 per hire (see pricing). One dedicated recruiter runs the search, with first screened candidates within 7 days. Read our guide on hiring your first product manager for the full process.
Frequently asked questions
When should a startup hire its first product manager?
Usually when the founder can no longer keep up with customer conversations and the engineering team at the same time, which often happens around Series A. Before that, a product-minded engineer or designer may be a better first hire.
Does a startup product manager need to be technical?
They need to understand technical trade-offs and earn engineers' respect. Whether they need to read code depends on your product. Say exactly what you mean in the JD.
What is the difference between a product manager and a project manager?
A product manager decides what to build and why, based on customers and data. A project manager makes sure agreed work gets delivered on time. Startups usually need the first.
Worth a brief chat about your next hire? Book a free call.
Hiring after a funding round?
First candidates in 7 days. Fixed-fee, no commission.