How to Hire a Head of Product at a Startup

To hire a head of product, decide first whether you are hiring someone to run product inside the founder's strategy or to take product over. Those are different roles with different candidate pools, and most failed searches never made the choice. Then define the constraint the hire must remove, test candidates on finding that constraint in your own business rather than on presenting roadmaps, and settle decision rights between the founder and the new leader before the offer goes out.

Product management recruitment for tech startups is unusual among technical searches because the role sits directly on top of the founder's identity. A first engineering leader takes over something the founder was happy to hand off. A first product leader takes over the thing the founder believes they are best at. That is why this hire fails on structure more often than on the person.

Do you need a head of product, or a product manager?

The title on the job post is usually chosen for recruiting reasons: "head of" attracts stronger candidates. But the two roles are different jobs, and a strong candidate for one is often the wrong person for the other.

The honest test is a question for the founder: two years from now, who decides what the company does not build? If the answer is still you, hire a senior product manager and be clear about it. If the answer is the new leader, hire a head of product and be prepared to mean it. Either answer is fine. The failure mode is hiring the second and behaving like the first.

Define the constraint, not the job description

Job descriptions for product leaders are almost interchangeable: own the roadmap, work cross-functionally, be customer-obsessed. None of that tells a candidate what is wrong, or tells you what to test for. The useful brief names one constraint.

• Discovery. The team ships, but too much of what ships does not move a metric. The hire needs to build the evidence loop from customers to roadmap.
• Delivery. The roadmap is right and nothing lands on time. The hire needs to run prioritisation and scope, and say no to the founder in writing.
• Complexity. The product has grown past what one person can hold, and decisions are being made locally and inconsistently. The hire needs to create structure without adding process for its own sake.
• Founder capacity. Nothing is broken except that the founder is doing three jobs. The hire needs to absorb one of them entirely, which is the hardest version because it requires trust rather than skill.

Each constraint points at a different candidate. Someone who has run discovery at a company with product-market fit may never have been the person who said no to a founder. Someone who has scaled a product organisation from five to forty may find a twelve-person startup with no data team frustrating rather than interesting. Choosing the constraint first shrinks the search to people who have already solved your specific problem.

What to test for

Standard product interviews test presentation: talk through a product you shipped, critique an app, prioritise a list of features. Candidates who have interviewed before are good at all three, and none of them predicts whether the person will find the right problem in your company.

Three exercises do predict it. Share real data and two customer call recordings, and ask what the constraint is and what they would do in the first ninety days. Ask what they would not build from your public roadmap, and why. And ask, in detail, about the last time they worked with a founder who had previously owned product: what the handover looked like, what went wrong, and what they would do differently. The third one matters most, and it is the one most interview loops skip.

Vet with a practitioner. If nobody on your team has held a product leadership role, you are calibrating against your own guess about what good looks like. Having a current head of product screen the shortlist before your loop is the single highest-return step in the search, because they read a product history for ownership rather than for vocabulary. It is the same argument as for any role you have never hired before.

Decision rights are the hire

A head of product who cannot decide is a very expensive project manager. Before the offer, write down which decisions are theirs, which are the founder's, and which need both. Roadmap priorities within an agreed strategy should be theirs. Changing the strategy should require both. Killing a feature the founder loves is the test case: if that decision is not genuinely available to the new leader, say so during the search, because the strong candidates will ask.

This is also where the search connects to the rest of the organisation. A product leader hired before the first management layer exists will be managing engineers informally within a month. Decide whether that is intended, and whether the engineering leadership hire should come first.

Compensation and the equity conversation

Product leaders at Series A and B companies are expensive relative to the team they join, and the gap is mostly equity. Strong candidates will have several offers and will compare equity on a fully diluted basis with a view on your next round. Be ready to discuss the cap table honestly. A head of product who joins on base salary alone and discovers the equity is thin will start looking within a year, and the search cost is paid twice.

The search itself, if you use a firm, is paid by the company. Exclusive searches run from around 17% of first-year base; retained searches for leadership hires, which this usually is, sit around 20%. Whether that is worth it depends on the same question as whether to use a recruiter at all: do you have the network to reach product leaders who are not applying anywhere, and the time to run the process while doing the job you are trying to hand off.

Common questions

When should a startup hire a head of product?

When the founder is the bottleneck on product decisions and the cost of that is visible: engineers waiting on answers, a roadmap that changes weekly, or customer evidence nobody has time to read. That usually happens between a strong Series A and Series B, once there are two or more engineering teams and the founder can no longer hold every product conversation personally.

Should my first product hire be a product manager or a head of product?

If the founder intends to keep owning product strategy for the next two years, hire a strong senior product manager who can run discovery and delivery inside that strategy. If the founder needs to hand product over, hire a head of product. Hiring a head of product and then continuing to make every product decision yourself is the most common way this hire fails.

What does product management recruitment for tech startups cost?

Two costs matter. The compensation itself, which for a head of product at a Series A or B company sits well above a senior engineer once equity is included. And the search: a specialist agency running an exclusive search charges from around 17% of first-year base, with retained searches for leadership roles at around 20%, paid by the hiring company.

What should I test for in a head of product interview?

Three things, in this order: whether they can find the constraint in your business from your data and a few customer calls, whether they can say what they would not build and why, and how they have worked with a founder who was previously the product owner. Case studies about roadmaps test presentation. These test judgment.

Does a head of product need to be technical?

They need to reason credibly with engineers about tradeoffs, which is different from being able to build. For a technical or AI product, that bar is higher: they should be able to read an architecture discussion and understand what a proposed feature costs. For most startups, product judgment and customer fluency matter more than an engineering background.