How to hire a product manager

A product manager decides what the team builds and why, working between customers, engineers, design and the business. This playbook covers when to hire your first PM, which kind you need, what it costs, where to find candidates, a full interview plan with take-homes and questions, how to evaluate candidates and how to close the offer.

When to hire your first product manager

Most early startups do not need a PM. Founders usually hold the product vision, talk to customers every week and make roadmap calls in the hallway, and that is the right setup for a long time. A PM adds cost and a layer of communication, so hire one when the layer is cheaper than the problem.

Signs you are ready:

• You, as founder or CEO, are the bottleneck. Engineers wait on you for decisions, and you cannot give product the attention it needs while also selling, fundraising and hiring.
• Several people are building in different directions. There is no single, written priority order and teams argue about what is next.
• Customer input is piling up unprocessed in support threads, sales calls and Slack. Nobody is turning it into decisions.
• You are shipping features without knowing whether they worked. There is no habit of defining success before launch or checking it after.

Signs you should wait:

• The founder is a strong product person and still has time for it.
• You are still searching for product-market fit and the product changes weekly. A PM can slow down a team that mostly needs to build and talk to customers.
• Your real gap is design or engineering leadership. A PM will not fix a missing tech lead or a missing designer.
• You are looking for a project manager or someone to take notes and run standups. That is a different job.

If you are unsure, try a trial period where a strong engineer or designer owns the roadmap and see where it hurts. If you do decide to hire, read what a strong design hire looks like too, since your PM and first designer will work as a pair.

Types of product managers

The title means different things at different sizes, so write down which version you are hiring.

Before you open the role, write a one-page role definition with three parts: the outcomes you want in the first six to twelve months, the decisions this person will own, and the decisions that stay with you. Candidates ask about the last one, and vague answers drive good PMs away. Use it to write the job description, and see how to describe the role without bias before you publish.

What to look for in a product manager

• Product sense. They explain why, not just what. They start from users and company goals, generate options and prune.
• Judgment under ambiguity. They form a hypothesis, decide with incomplete data and can say what happened afterward.
• Execution. They have taken something from idea to launch and can describe where it went off track.
• Technical fluency. They work well with engineers on tradeoffs and know what to understand before committing to a roadmap item.
• Stakeholder management. They lead people they do not manage, say no clearly and deliver bad news early.
• Analytics. They define success before launch and check the result after.
• Clear communication. Their writing and speaking are short and structured, and the recommendation comes first.

Write these down before the first interview. They become the criteria you evaluate candidates against below.

Red flags to probe. Jumping straight to features without choosing a user, credit that is always “we”, conflict stories that end with the other person being wrong, no view on how they would know whether something worked, and treating other teams as service providers. Each is a reason to ask more, not an automatic no.

What it costs to hire a product manager

Hiring a product manager has three costs: the recruiting fee if you use outside help, your team’s time across the screens, take-home and final loop, and the pay package itself. For pay, see the compensation section below and our compensation strategy guide. For the recruiting fee, Dover’s Marketplace publishes what companies actually paid for product manager hires:

Recruiters on Dover set their own pricing, and you can engage them without a long-term contract.

Where to find product managers

Strong PMs are often employed and not looking, so a posting alone rarely fills the role.

• Your network and referrals. Ask founders, investors, engineers and designers who they would want to work with again. Peer recommendations are the best signal for PMs because the work is hard to see from a resume.
• Outbound. Look for PMs at companies one stage ahead of you, or one stage behind, who have shipped something relevant to your domain. Personalize the first message around something they built. See how to source candidates.
• Adjacent roles. Engineers, designers, solutions engineers and founders of failed startups often make good first PMs. Look for people who already behave like product owners.
• Job boards. Post the role widely and write the description around outcomes. See where to post jobs and find candidates.
• Product meetups and alumni networks from the companies whose products you admire.
• A vetted recruiter. Recruiters on Dover’s Marketplace who hire product managers can run the search while you stay in the interviews. See what a fractional recruiter does for how those engagements work.

In Dover’s ATS, post the job to 50+ job boards from one place, post to Dover Startup Jobs if you are a venture-backed startup, and see which source produces hires in Reporting & Analytics. See Managing job boards.

The interview plan for a product manager

A good plan tests different competencies in each round so interviewers are not asking the same questions. Tailor the plan to your stage; for a seed-stage PM you might skip the team conversation and compress the final loop.

The loop is about two and a half hours. Run it in one sitting when you can, or split it across two days so nobody is exhausted. See interview process best practices for how to assign competencies to interviewers and avoid duplicate questions, and how to run the first call for the screen.

Take-home exercises

Keep the take-home to three or four hours and give candidates about a week to return it. Pick one exercise, not three, and discuss it live afterward; the follow-up conversation is where you learn the most. Never ask candidates to do work on your actual roadmap.

Writing exercise: a recommendation memo

Give the candidate a real strategic question that your company or a similar company could face, with enough context to answer it. Ask for a one to three page memo, in text rather than slides. For example:

Our company sells [product] to [customer]. We are considering expanding into [adjacent offering]. Write a memo for the CEO that recommends whether we should. Cover the potential upside, how you would implement it (product and go-to-market changes, and pricing), the short-term and long-term risks, and your overall recommendation. Diagrams are fine, but keep the main format as text.

What good looks like: a clear recommendation in the first paragraph, explicit assumptions, honest risks, and a plan for what they would test first. Weak responses list pros and cons without choosing.

Product design exercise: a user unlike the candidate

This tests empathy and problem framing, with business constraints deliberately set aside. Ask the candidate to design something for a user who is very different from them, for example:

• Design an alarm clock for a blind person.
• Redesign the dashboard of a self-driving car.

The key is whether they choose a specific user and use case before designing anything. Candidates who start drawing features immediately have skipped the hardest step.

Product intuition and prioritization

Two short versions work well:

1. Pick a product you know. Ask the candidate to name three products they use regularly that you are likely to know about too, ideally mid-sized rather than giant. Then say they are head of product at one of them and ask what three features they would build and why. Strong candidates state the company goal first (revenue, retention, activation), generate more than three ideas, then prune.
2. Design a new product line live. Ask them to design, for example, a ride service for kids whose parents are tired of driving them around. Spend an hour on key tradeoffs and risks, not wireframes. Give a concrete feature list and ask for a priority order with back-of-the-envelope impact estimates. Use a well-known company that is not yours so neither side has an information advantage.

If an exercise takes more than a few hours, pay for the candidate’s time or shorten it.

In Dover, build the plan on the job’s Interview Plan tab. Use a single-part stage for the screen and hiring manager interview, a multipart stage for the final loop, and an assessment stage for the take-home. Assign each a feedback form and an email template, and send candidates a scheduling link from their profile. See Setting up your interview plan.

Product manager interview questions

Pick two or three questions per competency rather than asking every one. Always follow up with “What did you do specifically?” and “What happened as a result?”

Product sense

• Tell me about a product you love and one you think is bad. What would you change first, and why?
• Walk me through a product decision where customer feedback and your own instinct disagreed. What did you do?
• How do you decide who your customer is when a product could serve several groups?
• Pick a product we use. What are its biggest risks and its biggest unmet needs?
• Tell me about something you learned from a customer that changed your plan.

Execution

• Describe a project you took from idea to launch. Where did it go off track, and how did you recover?
• How do you decide what to cut when the deadline does not move?
• Walk me through how you write a spec. Who reads it, and how do you know it worked?
• Tell me about a launch that did not work. What would you do differently?
• How do you keep a team moving when requirements are still unclear?

Technical depth

• How have you worked with engineers on a decision with a technical tradeoff, like build versus buy or refactor versus ship?
• Explain how [a product or technology relevant to us] works to someone who is not technical.
• Tell me about a time an engineer pushed back on your plan. How did you resolve it?
• What do you want to understand technically before you commit to a roadmap item?

For some roles you may need real technical depth, such as APIs, data models or infrastructure. If so, have an engineer run this round and say what level of depth the role needs.

Leadership and stakeholder management

• Tell me about a time you had to influence people who did not report to you.
• Describe a disagreement with a founder or executive about priorities. How did it end?
• How do you say no to a request from sales or a big customer?
• Tell me about a time you had to deliver bad news about a project.
• How do you build trust with a team that already has a strong culture of its own?

Analytics and prioritization

• How would you define success for a new feature before you build it?
• Tell me about a time data changed your mind.
• A key metric dropped 15% this week. Walk me through what you do first.
• How would you prioritize these five items? Give them a list and ask for an order and the reasoning.
• What metrics would you look at to judge whether our product is working?

Reference checks for product managers

Do them for finalists, after the final loop and before the offer. A PM’s work is spread across other people, so references tell you things the interviews cannot.

• Ask about working style: how they handled disagreement, how they communicated and what a manager would need to know about working with them.
• Ask an engineer or designer who worked with them what the PM decided, what they shipped and how they treated the team when a launch went badly.
• Ask a former manager whether they would rehire the candidate and what kind of support got the best out of them.
• Compare the stories to what the candidate told you. Gaps matter more than flattering adjectives.

Ask candidates for permission before you contact a current employer.

How to evaluate product manager candidates

Evaluate each candidate against the same criteria right after the interview, before you compare notes with other interviewers. Write what you saw and heard, not a number.

Decide in advance which criteria are must-haves. A weak showing on a competency the role depends on should outweigh strength elsewhere. When feedback conflicts, hold a short debrief and ask each interviewer to name the evidence behind their view.

Interview feedback form

Give every interviewer the same short form and ask them to complete it before the debrief.

1. Overall recommendation: strong yes, yes, no, strong no.
2. For each criterion assigned to you, one or two lines of evidence: what the candidate said or did.
3. The strongest signal from this interview.
4. The biggest concern, and whether onboarding could address it.
5. What we should probe in the next round.

Ask interviewers to submit their feedback before they read anyone else’s. Compare notes in a short debrief, not in a chat thread.

In Dover, create this as a feedback form in Settings → Feedback Forms and assign it to each stage, so every interviewer answers the same questions. On Premium, the AI Notetaker can capture the conversation and fill in the form. See Interview feedback forms.

Product manager compensation and closing the offer

How to think about product manager pay

Decide the package before you post the role, so you can discuss it in the first conversation. For market data, see our compensation strategy guide; this section covers the decisions, not figures.

• Level and scope. A seed-stage generalist who owns the whole product and a growth-stage owner of one area are different levels. Say which one you are hiring so the range matches.
• Base salary and equity. At a startup, equity is often a large part of the offer. Explain the number of shares, the vesting schedule and what they are worth in plain terms.
• Bonus. Decide whether any pay is tied to company or product goals, and say how it is measured.
• Pay transparency. Many jurisdictions require a pay range in the posting. See compensation requirements for job postings.

Close a product manager hire

• Speak to what the PM will own. Strong PMs want decision rights, a real problem and a direct line to the founder. Say what you would be handing over and what you would keep.
• Let the finalist meet the engineers and designer they will work with. PM candidates judge the company by the quality of the people around the role.
• Move fast between the final loop and the offer. Good PMs interview at several companies at once.
• Explain how you think about pay and equity before the offer call, then make the offer on a call and follow in writing. See how to make an offer.

Common mistakes when hiring a product manager

• Hiring a PM too early. If the founder still has time for product and the product changes weekly, a PM adds a layer without removing a bottleneck.
• Hiring a project manager by mistake. Taking notes and running standups is a different job from deciding what to build.
• Leaving the role undefined. Without outcomes and decision rights written down, good candidates cannot tell what they would own.
• Hiring for the wrong stage. A big-company specialist may struggle at seed, and a generalist may struggle to own one area at scale.
• Asking for work on your real roadmap. Use a short exercise on a fictional case and pay for the candidate’s time if it runs long.
• Skipping the engineers and designers. A PM works through them, so they should be in the final loop.
• Moving slowly. Strong PMs interview at several companies at once. Decide within a few days of the final loop.

Get help hiring a product manager

A first PM search is hard for a small team: the best candidates are employed, and the work is hard to judge from a resume. Dover’s Marketplace connects you with vetted independent and fractional recruiters who have made product manager hires, and you can engage them without a long-term contract. They run sourcing, screening and scheduling, and every candidate stays in your own free ATS.

• Browse recruiters who hire product managers and see what past hires cost.
• Run the process in Dover’s free ATS with interview plans, feedback forms and offers.

Frequently asked questions

When should a startup hire its first product manager?

Hire a PM when product decisions are the bottleneck, not when you simply feel you should have one. Typical triggers are a founder who can no longer own both the company and the roadmap, several engineers working without a shared priority order, or customer feedback piling up with nobody synthesizing it.

How long should a product manager interview process take?

Plan for about two to three weeks from first call to decision: a 30-minute screen, a 60-minute hiring manager interview, a take-home of three to four hours, and a final loop of about two and a half hours. Give candidates a week for the take-home and decide within a few days of the final loop.

Should I give product manager candidates a take-home exercise?

Yes, if it is short, relevant and you will discuss it with the candidate afterward. A three to four hour writing or product exercise shows how a PM thinks and communicates far better than questions alone, but long or unpaid spec-work for your real roadmap is not fair to candidates.

What is the difference between a PM at a seed-stage and a growth-stage startup?

A seed-stage PM is a generalist who talks to customers, writes specs, runs the roadmap and often does analysis and design work themselves. A growth-stage PM owns one area, works with dedicated design, data and engineering leads, and spends more time on prioritization, alignment and metrics.

How much does it cost to hire a product manager?

It depends on how you hire. A traditional recruiting agency typically charges 15 to 25% of first-year salary, while Dover's Marketplace publishes the all-in cost of each product manager hire, shown in the live table on this page. Add your team's interview time and the pay package.

Where do you find product managers?

Start with referrals from founders, engineers and designers, then outbound to PMs at companies a stage ahead or behind you, and adjacent roles such as engineers, designers and solutions engineers. Job boards add volume, and a vetted recruiter can run the search for you.

What should I look for in a first product manager?

Judgment under ambiguity, direct customer contact and clear writing. Look for someone who picks a position, defines success before launch and has shipped with engineers, rather than someone who only describes frameworks.