WadeCV

Hiring guides

How to Hire a Product Manager: A Step-by-Step Guide for Small Hiring Teams

The first product manager hire is a decision about who makes decisions. This guide is for a founder or engineering lead handing over prioritisation, discovery and the roadmap for the first time, and for a team adding a PM to a product that has outgrown its original owner.

60-second answerUpdated September 2026
Hiring a Product Manager in 2026: the process
  1. Decide what you are handing over: Discovery? Prioritisation? Specs? Metrics? Stakeholders? A PM given all of it in a company where the founder still decides everything will fail in six months. The role description is the first screening step, and it decides who applies.
  2. Match the product type before the industry. B2B versus consumer, technical versus not, early versus scaling: PMs adapt to a new industry in a quarter and to a new product type in a year.
  3. Source where product managers already are: engineers' and designers' recommendations: the PMs they would work with again, and pMs at companies one stage ahead who want more ownership than a large product team allows.
  4. Screen every CV against a written rubric of the four things the job cannot be done without, then interview for evidence: what the candidate built, decided or fixed, scored against notes written before the interview.
  5. Decide within a week of the final interview and make the offer with reasons. The common mistakes below, starting with hiring a PM and keeping every decision, so they become a project manager, are how good candidates are lost.

The process

  1. 1

    Decide what you are handing over

    Discovery? Prioritisation? Specs? Metrics? Stakeholders? A PM given all of it in a company where the founder still decides everything will fail in six months. Write down which decisions become theirs and tell the team.

  2. 2

    Match the product type before the industry

    B2B versus consumer, technical versus not, early versus scaling: PMs adapt to a new industry in a quarter and to a new product type in a year. Hire someone who has done your type.

  3. 3

    Source through the people who work with PMs

    Engineers and designers know which PMs they would follow. Ask yours, and ask friends at other companies which PM they would hire back. Product communities are useful; job boards are noisy for this role.

  4. 4

    Screen against a rubric, not a feeling

    Write down the four things the job cannot be done without and score every CV against them before reading any further. Three minutes per CV with a rubric beats fifteen without one, and the decisions can be explained afterwards.

  5. 5

    Interview for evidence

    Every interview question should ask for something that happened: a system, a deal, a decision, a failure. Score answers against what a strong one contains, written down before the interview, so two interviewers agree.

  6. 6

    Decide fast and tell everyone

    Candidates judge a company by its process. Decide within a week of the final interview, tell the ones you passed on, and make the offer with the reasons you chose them. The best candidates have other offers.

Where to find candidates

  • Engineers' and designers' recommendations: the PMs they would work with again
  • PMs at companies one stage ahead who want more ownership than a large product team allows
  • Founders of small companies that did not work out, who have done every part of the job
  • Your own customers' product people, where the domain overlaps
  • A posting that names the decisions the PM will own

Screen your next batch of CVs against your own criteria

Set up your organisation, describe the role, and upload the CVs. Every one is read, scored and explained. Ten screenings are free; there is no subscription.

  • 10 free CV screenings
  • Every score explained
  • Free job posting

Mistakes that lose good candidates

  • Hiring a PM and keeping every decision, so they become a project manager
  • Using 'design an app for X' case interviews that reward performance over judgement
  • Weighting an MBA or a big-company title over decisions actually made
  • Not involving engineers and designers in the interview, then wondering why they do not trust the hire
  • Expecting a first PM to also do marketing, support and sales enablement

Running it well

Interview for decisions. Every question should ask for one the candidate made: what they knew, what they chose, what happened. A case exercise on your own product, on a problem you have not solved, is the one exercise worth running; you learn how they think and you might get a good idea.

Have the engineers and designer who will work with the PM interview them, with their own questions, and give their view real weight. A PM the team does not trust cannot do the job however good they are.

Write the offer with the decisions in it. 'You own prioritisation for the core product and the quarterly roadmap; the founder owns pricing' is a sentence that saves months of friction, and the candidates worth hiring will ask for it anyway.

Frequently asked questions

  • Should the first PM be senior?

    Usually. A first PM sets the practice everyone else inherits and has to hold their own with the founder. A junior PM with no senior PM to learn from struggles.

  • How technical should they be?

    Enough to have credible conversations with engineers about trade-offs. For a developer-facing product, more. A computer science degree is neither necessary nor sufficient.

  • What if the founder is not ready to let go?

    Then do not hire yet. A PM hired into a company where the founder still decides everything leaves within a year, and the team learns that product managers do not matter.

Related guides

More on this role

Screening product manager CVs this week?

Paste the job description into WadeCV, check the rubric it drafts, and upload the CVs. Each one is read against the rubric and scored with an explanation. Ten screenings are free; there is no subscription.

Screen your first CVs free