Hiring a product analyst
"Product analyst" describes two almost unrelated jobs — one that answers the questions it is given, and one that decides which questions are worth asking. Both write SQL. Both look identical on paper. Hiring the wrong one is expensive and takes about four months to notice.
Everyone lists the tools. Almost nobody lists the decision. Product analyst CVs converge on the same shape: SQL, Python, a BI tool, a list of dashboards built. None of that separates the two versions of the job, because the tooling is identical in both. What separates them is whether the person has ever changed what a team did — and that only ever shows up as a specific story, which is exactly the thing a CV template has no field for. "Built 40 dashboards" is the classic false positive: high output, no evidence anyone used them.
From a title that means three different jobs to one guide
Selene asks the question that actually splits this role in two: who acts on the analysis, and is this person expected to bring the question or just answer it?
Who acts on it, and who frames the question
For a data role Selene goes after the tools and the volume — but for this one the decisive question is about the relationship: who receives the analysis, and whether they arrive with the question already formed. The answer determines whether you are hiring a service function or a thinking partner.
One sentence changes the guide
One sentence, and the guide inverts. Under the default weighting a prolific dashboard-builder outranks someone who ran three analyses that changed the roadmap. Under this one, the second candidate wins — which is what was wanted all along, just never written down.
Exceptional, not just good —
“Someone with the mindset of a product manager and the skill set of a data analyst.”
→ Product judgment was weighted alongside SQL, and "changed a product decision with data" became a must-have.
What the guide ends up measuring
Seven criteria, typed and weighted, all editable. The technical bar is still a must-have — this is not a role where judgment substitutes for craft — but it stops being the only thing that ranks, and three of the seven now measure how someone thinks rather than what they can run.
No qualifications to gate on — and that is the difficulty
There is no certificate that separates the two versions of this job, no licence, nothing a yes-or-no question could filter. So none of the pile can be resolved before scoring; all of it has to be read. That makes the guide's weighting the entire game, and it is why the answer above matters more here than on almost any other role.
Scored on influence, not output
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.
Low confidence becomes an interview question rather than a silent guess. On this role that usually lands on the judgment criteria, because SQL depth is easy to evidence and question-framing is not.
How the blind scoring works →What stays with you
Selene's half
- Pinning down which version of this role you're hiring for, and building the criteria to match
- Reading all 80 against the same guide, blind, with the evidence attached
- A ranked shortlist, and what she would probe in each interview
- An interview brief that targets what the CV couldn't settle — like that SQL question
Yours
- Getting analysts to apply — Selene doesn't post to job boards or source candidates
- Any SQL test or case exercise; she reads what people wrote, not what they can do live
- The interview and any live problem-solving, with her brief in hand
- The offer, and every call that matters
Try the question that reshaped this role
Service function or thinking partner — say which one you actually need and watch the guide reshape around it.