Hiring your first product leader is the most consequential hire you will ever make.
Most founders we speak with already know this.
What they are less likely to know is how to evaluate candidates, when it seems everyone talks about the same themes: product strategy, product delivery, leadership, AI, organizational effectiveness and nurturing cross-functional alignment to achieve objectives.
In this article, we break down how to cut through the sameness of a candidate pool and what 3 things to focus your candidate evaluation on.
Understand the community you need to hire from
Before you write the job description or begin a search process, decide which community of product people you are going to hire from.
This is foundational because this decision will determine whether the next three months end in a hire or begin a restart after admitting you were meeting the wrong people.
OR worse, you hire the best person from a community that has a low likelihood of succeeding in your company.
Understanding communities
A community is not a skill set.
It’s a population of product leaders who share a formative experience. There are four that founders typically choose from:
Domain Expertise
Most Founders will admit their founding team is already a community of domain experts. Either they came from the industry, or they have lived with the problem set long enough to consider themselves experts, and they are usually right.
Many Founders also admit that what they actually lack is product management experience. The craft, the processes, the judgment about what to build and what to kill, and how to ensure that the investments are on the right bets, likely to convert into commercial success: revenue.
Stage
Most founders hiring their first product leader recognize that the community with the greatest likelihood of success is the one that has been in the trenches of a startup before and advanced a product business toward commercial success.
Commercial success might mean finding product-market fit. It might mean getting the first paying customers, or getting to a GA release. It might mean expanding the TAM total. It might mean pushing into an ecosystem through integrations and partnerships. A leader who has taken a product 0-1 is not necessarily the same leader who has a playbook for what should happen after a Private Equity event.
Delivery and Process
Some founders are not ready to let go, or they don’t want to. They intend to keep the vision. They want the customer feedback loops running through them. They have opinions about how the product looks and feels. They are the Founding CEO/CPO and intend to keep things that way a little longer.
Founders in that position are usually better served hiring from a community whose strength is delivery and process: leaders who establish a scalable, repeatable process for how products get built, shipped and managed.
We see this most often with founders whose background has been finance, legal or sales, or who came out of the industry they now sell into.
A Future State
The last community is product leaders from larger organizations, operating at scale, often carrying an employer brand their industry recognizes.
Founders choose this community for reasons worth being honest about. Sometimes it’s aspirational, a picture of the company you intend to become. Sometimes it’s ego, or an investor’s ego. And sometimes it rests on an assumption that deserves more examination than it usually gets: that only big tech knows how to win.
Evaluating “Playbooks”
At some point in the process, you will meet the candidate who has a playbook.
In fact, you may have even asked candidates whether they have one.
They will tell you they have done this before. They will walk you through their operating cadence, their discovery process, and how they structure a product org at various stages of a business. They have the lingo, have read the books that matter and cite the experts. It will be the most confidence-infused meeting you will ever have with this candidate.
However, it is important to realize that someone’s playbook is a record of what worked somewhere else, often under different circumstances. And not every candidate understands WHY their playbook worked and whether it will again.
Some candidates, earlier in their career and fortunate to have had a “one-hit wonder,” may naively believe it was their genius that was responsible for the success of the product and company. And they have a playbook to prove it.
This is in contrast to a more experienced candidate who has had many different experiences to draw from. They often seek to understand the extent of an opportunity before citing which of many playbooks or best practices they would apply.
Questions to help you unpack someone’s playbook:
👉 “What did your process assume was already in place?”
👉 “Which parts of it would you NOT bring here?”
👉 “Tell me about the times things didn’t work out.”
👉 “Who did you have to convince, and what did they say no to?”
You are not hiring a playbook.
You are hiring the judgment and experience that will adapt a playbook or set of best practices that will ultimately achieve the outcome you have hired them to achieve.
Evaluating Ramp Up
Most founders ask some version of “what would you do in your first 90 days?”
It’s the most anticipated interview question for any leadership role, whether sales, marketing, engineering or product management.
This question is a playbook question wearing a different hat.
So let’s turn it around.
Ask them what they need from YOU, and what they intend to figure out on their own.
This is the more useful question because of how most companies actually work.
For a start-up Founder hiring their first product leader, there is no onboarding program.
There is no predecessor to shadow.
Whatever ramp happens, they are going to have to run it themselves, while you are in investor meetings, travelling to customers or engaged in any number of matters.
A candidate who has done this before knows that.
What a real ramp-up answer sounds like
It has texture and detail. Ask them to walk you through their last one, week by week, at the company they joined most recently.
Real answers are specific:
- The eight customer calls they sat in on in the first ten days.
- The support queue worked for an afternoon.
- The three engineers they took for coffee because those three had been there since the beginning.
- The decision from eighteen months earlier they went and asked about because everything downstream of it looked strange.
Rehearsed answers stay at the level of principle.
“I spent the first 30 days listening.” Everyone says this. You cannot tell from it whether this person will be contributing in month two or still forming impressions in month four.
What they need from you
Pay attention to what they are asking you to commit to.
Good asks are small, specific and finite.
- Introductions to 3 customers.
- An hour a week on your calendar for the first six weeks.
- Being told explicitly which decisions are theirs and which are still yours.
- Permission to say no to the sales team on your behalf, in writing, once.
Weak asks are large and abstract. They need the team to be “aligned.” They need “executive buy-in.”
These are not requests; they are conditions, and the candidate who leads with them is describing an environment they would like to work in, rather than one they intend to build.
A candidate who cannot tell you what they need from you has not thought about working with you. They have thought about getting hired.
Where THEY see the gaps
Ask it directly. “Where do you see your gaps in this role?”
The candidate who names a real one is showing you authenticity and humility and confirming for you where your support is going to be needed.
Perhaps they have never worked in a regulated industry before.
Perhaps they have never worked without a design team.
Hiring your first product leader is a decision you will make with incomplete information, and no interview process changes that.
What changes the odds of a successful hire is deciding which community you are hiring from before you meet anyone, listening past the confidence of a well-rehearsed playbook, and getting specific with each other about what the first ninety days will require from both of you.
This is not an absolute list, but it separates candidates who work out from the ones who interview well.
Hiring your first product leader? Talk to us before you meet your first candidate. Book a call.