Hiring a product manager
Two hundred and thirty applications written in the same voice, claiming the same verbs, attached to the same outcomes. No role on this site has a wider gap between how CVs read and how candidates differ.
Product is the most CV-inflated discipline in tech, and it is not close. The role has no craft artefact — no repository, no portfolio, no ledger — so the CV is the whole evidence base, and the CV is written in a vocabulary designed to be unfalsifiable. Everyone led a cross-functional team. Everyone drove a roadmap. Everyone owned a product that grew, in a period when the company was growing anyway, alongside forty other people who also claim it. The genuinely strong PM and the person who attended the meetings describe the same quarters in the same words, and seniority inflation makes it worse: the title moves faster than the capability, so years and level are close to useless as sorting signals.
What this PM actually decides
Selene goes after the decision rights, because “product manager” describes anything from a delivery coordinator to someone who sets strategy.
Authority, stakeholders, and who says no
The single most useful thing to establish on a product role is what this person is allowed to decide alone. A PM with real authority and a PM who writes tickets for someone else’s decisions attract the same applicants and need opposite guides.
One sentence changes the guide
It works precisely because it asks for the one thing the inflation cannot supply. A candidate who never held the decision has nothing to describe here; a candidate who did will have an example ready, and it will come with a reason, a cost and usually somebody who was annoyed about it.
Exceptional, not just good —
“I want to know what they said no to. Anyone can list what shipped.”
→ A defended “no” became the top-weighted criterion; roadmap size and team headcount stopped being scored.
What the guide ends up measuring
Six criteria written to be hard to claim without evidence. Note that none of them counts anything — no team sizes, no roadmap items, no growth percentages — because every countable thing on a product CV is a property of the company rather than the person.
No gates — and seniority is the false one
There is no fact to ask on an application page. The filter people apply instead is title seniority, and on this role it is actively misleading: the title inflates faster than any other in technology, so a "Senior PM" from a company that promoted after eighteen months and a "PM" from one that promoted after five years are sorted precisely the wrong way round by any level-based filter.
Scored on the decisions, not the vocabulary
Selene never receives the candidate’s name or the raw CV. She scores a blind, structured profile, with any stated age, sex, nationality and religion stripped out before scoring runs.
She also gets no company logo — which on a discipline where pedigree does most of the informal sorting is a larger intervention than it sounds.
How the blind scoring works →What stays with you
Selene's half
- Pinning down what this PM decides alone, and building the criteria to that scope
- Reading all 230 against the same guide, blind, with the evidence attached
- A ranked shortlist that is not sorted by who writes the most confident prose
- An interview brief that asks each candidate for the “no” they only gestured at
Yours
- Getting product people to apply — Selene doesn’t post to job boards or source candidates
- Any case exercise or product critique, with her brief in hand
- The interview, where the vocabulary either holds up or does not
- The offer, and every call that matters
Ask what they said no to
Describe the decisions this role really owns, and watch the guide stop rewarding the confident summary line.