Why job boards keep sending the wrong Head of Product candidates, how product-native signal recognition actually works, and how to stage a search from Senior IC through CPO.
If you've been flooded with CVs for a Head of Product role and not one of them has actually done the job at your stage, the sourcing channel is almost always the culprit. Job boards surface people who are looking, and the person you actually need almost never is. Sophia Philippou leads Perpetuate Talent's Product Leadership practice on exactly this problem: finding senior product people who are already succeeding somewhere else and have no reason to check a careers page.
Most of the founders we work with are running $10M-$50M ARR venture-backed B2B SaaS and DeepTech scaleups across Australia and Silicon Valley. Here's why volume sourcing fails product leadership roles specifically, what evaluating a product leader actually takes, and how the search itself should change depending on whether you're hiring a senior IC, a Head of Product, or a CPO.
A Head of Product who is six months into a role they like isn't refreshing LinkedIn on a Tuesday night. They're in the middle of a roadmap they built, managing a team they hired, arguing for a bet they believe in. Nothing about that person's week involves browsing job boards, so a posting, however well written, is invisible to exactly the person you want most.
What a job board actually collects is people who are between roles, recently made redundant, or restless enough to be scanning openly. Some of those candidates are genuinely strong. Most aren't the stage-matched operator you need, and the flood you're describing is the predictable result of a title that's broad enough to attract everyone and specific enough to fit almost no one. "Head of Product" means something different at a 15-person Series A team than it does at a 200-person Series C company, and the applicants chasing the title rarely map cleanly onto either.
Access is our Craft. The problem isn't finding people with product experience. LinkedIn can do that in ten minutes. The problem is reaching the specific handful who've operated at your stage, in your kind of product, and aren't applying anywhere. That takes a different channel: one built on who already knows this person's work, not who happens to see the ad.
A generalist recruiter can read a resume for keywords: team size, years of experience, companies worked at. What they usually can't do is read a portfolio the way another product person would, and for a Head of Product hire, that's most of the actual evaluation.
Judging a product leader means sitting with their roadmap history and asking questions a resume can't answer. Did they take a product from zero to something people actually paid for, or did they inherit a product that already worked and optimise it? Those are different skills, and a candidate who's brilliant at one is often genuinely weak at the other. Someone who scaled a mature product from $20M to $80M ARR may struggle badly with the ambiguity of a pre-product-market-fit team, and someone who thrives in that ambiguity may get bored the moment the job becomes about process and forecasting rather than discovery.
For the B2B SaaS and DeepTech companies we work with, there's a second layer most generalist recruiters miss entirely: domain credibility. A product leader for a company translating complex science and data into something a customer will actually pay for needs to understand the underlying technical constraints well enough to make real trade-off calls, not just manage a backlog written by people who do. That's a different evaluation than judging consumer product experience, and it's one you can only make if you've actually sat with technical roadmaps before, not just titles.
Off-market search for engineering leaders often runs on shipped code, technical architecture decisions, and who other engineers respect for solving hard technical problems. Product leadership signal looks different, because the job itself is different: less about a single artifact you can point to, more about judgment demonstrated in public and reputation built across a community over years.
Sophia's approach leans on exactly that community, and it's how the Talent System™ actually runs for product leadership searches. She's deeply integrated into the local product community, not as an occasional attendee but as someone who hosts the events, sits on the panels, and has become, in a very literal sense, the person other product people think to introduce when they hear about a search. That reputation compounds. When a founder needs a Head of Product, the fastest signal usually isn't a job description, it's asking the three or four people in the room who the strongest product operators actually are, and hearing the same two or three names come back independently.
Conference talks matter here too, not as a vanity metric but as a genuine data point: someone willing to stand up and explain how they made a hard product call, in front of an audience of their peers, has usually thought about that decision more rigorously than someone who's only ever explained it to their own manager. Who other product leaders respect, who gets asked to speak, who gets quietly recommended when someone's hiring, that's the signal. It takes years of being embedded in that world to read it accurately, which is exactly why a generic sourcing license can't replicate it.
The title you write in the brief should follow from what the seat actually needs to own, not from a title you liked at a company you admire. Each stage changes what "good" looks like, and it changes how the search itself has to run.
Owns a product area, not a team
Best fit: you need someone shipping and making calls inside a defined surface area, before you need someone managing other product people.
Still hands-on, now owns the roadmap
Best fit: one product line, the founder still sets vision, and the seat needs to build the first real product operating rhythm.
Owns commercial outcomes, sits with the CEO
Best fit: the board expects product to be argued at the executive table, and revenue, retention, or expansion depends on that voice.
The search changes accordingly. A senior IC search leans harder on evidence of hands-on craft: what they personally shipped, how they think about a specific kind of problem. A Head of Product search weighs 0-to-1 instinct against the team's actual stage, since someone brilliant at inventing a product can be a poor fit for a team that already knows what it's building and needs someone to make it repeatable. A CPO search is closer to a board-level hire: commercial judgment, the ability to hold their own with a CEO and investors, and a track record of owning outcomes rather than just outputs. Naming the wrong one of these at the start of a search is the single most common reason a placement doesn't work out a year later.
The intake conversation goes fastest, and the pitch we build lands hardest, when a founder has already done some of this thinking before we sit down together.
Before the First Conversation
None of this needs to be polished, just honest, since the pitch we build only works if it's built on the real shape of the role rather than the flattering version of it.
Off-market search earns its cost on a small number of high-stakes product leadership hires. It isn't built for filling a pipeline of junior product managers, and we'd rather say that plainly than stretch the model somewhere it doesn't belong. If you need five PMs hired inside a quarter, a volume recruiter or an in-house talent function will serve you better and cheaper than a search built around one hyper-customised pitch at a time.
The proof of where this model does work sits in our own placements. At ASX-listed Envirosuite, we placed their Chief Product Officer alongside their CTO and COO in the same engagement. For a NASDAQ-listed global SaaS company, we placed a Senior Director of Product. Further into the pipeline that feeds product leadership over time, Technical Product Managers in Edge AI and Senior Product Designers have gone into Blackbird-backed Series B and C hard-tech companies. Every one of those was a scarce, A-Grade hire, never a volume problem.
A CTO search evaluates technical architecture judgment and engineering leadership; a Head of Product search evaluates product judgment demonstrated through community reputation, roadmap history, and 0-to-1 versus scale-stage fit. The candidate pools barely overlap, and the signal that identifies a strong product leader (who other product people respect, what they've shipped and why) is different from the signal that identifies a strong technical leader.
Retained product leadership searches across Australia and the US commonly run 25 to 33 percent of first-year cash compensation. We ask for one hour of a founder's time to build the pitch, and price on the same basis: a fee for reaching someone who has no reason to be looking, not a fee for filtering a pile of applicants.
We deliver 2 to 3 candidates within 5 to 10 days of the initial intake call. That's time to a shortlist you can start interviewing, not time to a signed offer, since the pace of your own interview process still determines when someone actually starts.
If you're scoping a Head of Product, VP of Product, or CPO search now, Sophia leads that work end to end through our Product Leadership Search practice. Want to check our claims before taking them on faith? Read what to ask any search partner about off-market reach. Otherwise, message Sophia on LinkedIn → and we'll set up the one-hour conversation.