When to hire your first product manager
Hire your first product manager when the founder who has run product can no longer talk to customers, decide priorities and write specs for every team, usually somewhere past ten engineers.
The role in one sentence
Before writing a job post, say the role in one sentence. If you cannot, the role is not clear enough to hire for.
"We need a first product manager: B2B, has shipped with a small engineering team, talks to customers every week and is comfortable with data and detail."
Change the details to yours. In Evander this sentence is enough to create the job post, interview stages and scorecards as drafts; see how it works.
Job description template
[Company] builds [product]. Until now a founder has run product. You would be the first product manager: you own [area], decide what gets built next with the team, and are responsible for whether it works for customers.
What you will do
- Talk to customers and users every week.
- Decide priorities for your area with engineering and design.
- Write short, clear specs and keep scope small.
- Follow features after launch and fix what does not work.
- Keep the founders and the rest of the company informed.
What we look for
- You have shipped B2B product with a small team and can describe your part exactly.
- You have made decisions from customer conversations and from data.
- You write clearly.
- You are fine doing whatever the product needs: support, QA, docs.
Add the location, the pay range and equity, and how the interview process runs. Several US states require a pay range in the post, and EU rules require telling candidates the range before the first interview.
Screening brief
A screening brief says who should get an interview. Use it yourself or give it to AI screening.
Must-haves
- Has shipped product as the responsible PM with a small engineering team, because there is no layer above to lean on.
- Regular direct customer contact in recent roles, because priorities come from there.
- Clear written thinking, shown in a sample, because specs and decisions are written.
Either of these profiles works
- Product manager from an early-stage startup.
- Engineer, designer or founder who moved into product and has shipped.
Bonuses
- Technical background.
- Knows your market.
- Has worked directly with a founder who ran product.
Interview plan
| Stage | What it tests |
|---|---|
| Intro call (30 min, founder) | What they have shipped and how they work with founders. |
| Product deep dive (60 min) | One product they shipped: the problem, what they cut, what happened after launch. |
| Working session (90 min) | A real problem from your roadmap: how they frame it, what they would ask customers, what a first version is. |
| Team conversations and references (90 min) | With engineering and design leads. References from an engineer and a manager. |
Scorecard
Rate each criterion from 1 to 4 with a written example, before the debrief and without seeing other ratings. More in interview scorecards.
| Criterion | What strong looks like |
|---|---|
| Customer insight | Knows specific customers and what they struggle with. |
| Prioritization | Makes clear choices and explains what is left out. |
| Scope | Cuts features down to the smallest useful version. |
| Works with engineers | Engineers describe them as helpful, not as a ticket source. |
| Follow-through | Measures results after launch and acts on them. |
Interview questions
- Tell me about something you shipped that did not work. How did you find out, and what did you do?
- What did you last decide not to build, and who disagreed?
- How do you work with a founder who has strong product opinions?
- Take one of our features. How would you find out whether it works?
- Describe a spec you wrote. What was on the first page?
Common mistakes
- Hiring a PM before the founder is ready to give up decisions.
- Hiring for process and frameworks at a stage that needs judgment and hands-on work.
- Choosing big-company experience where the PM never talked to customers.
This kit is also available as Markdown, free to copy and adapt, in the hiring-templates repository on GitHub.
Questions
When should a startup hire your first product manager?
Hire your first product manager when the founder who has run product can no longer talk to customers, decide priorities and write specs for every team, usually somewhere past ten engineers.
What should a job description for your first product manager include?
A short summary of the company and the role, four or five things the person will do, three or four requirements that can be checked, the location, the pay range and equity, and the interview process. Start from one sentence, for example: "We need a first product manager: B2B, has shipped with a small engineering team, talks to customers every week and is comfortable with data and detail."
What interview questions should I ask your first product manager?
Tell me about something you shipped that did not work. How did you find out, and what did you do? What did you last decide not to build, and who disagreed? How do you work with a founder who has strong product opinions?
What are common mistakes when hiring your first product manager?
Hiring a PM before the founder is ready to give up decisions. Hiring for process and frameworks at a stage that needs judgment and hands-on work. Choosing big-company experience where the PM never talked to customers.