Hiring Profiles by Product Ops Pillar
Match each product ops pillar to a distinct candidate background and skillset
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
The three pillars require fundamentally different people, so you hire against the pillar, not a generic 'product ops' spec. Business and data insights wants a data-storytelling analyst (often ex-consultant), not a database engineer. Process and practices wants a high-EQ systems-thinker who introduces methods as suggestions, not mandates. Customer and market insights wants a user-research/research-ops person who compulsively operationalizes. A shared trait across all three: the drive to build a system to fix a recurring problem.
Origin
Melissa Perri and Denise Tilles, from their hiring experience at Product Labs and the case studies (e.g. Jen Cardello's research ops at Fidelity) in their Product Operations book.
Core principles
- 01Hire to the pillar's specific skillset, not a generic title
- 02A universal signal: candidates who instinctively build systems to automate work they hated
- 03The data-insights hire needn't know product; the process/governance hire must have product background
How to run it
- 1
For business & data insights, hire a data storyteller
Look for someone excellent at interpreting data, telling stories with it, and communicating to many stakeholder types. Consultant backgrounds (ex-McKinsey, ex-Deloitte) work well because they churn out these reports. Bonus if they also know a BI tool like Looker or Tableau.
Pro tip Someone strong at BI tools AND at Excel/PowerPoint storytelling is a home run; the two together are rare.
Watch out Do NOT hire a database engineer for this — you want insight extraction, not building SQL tables. They don't need to be a product expert.
- 2
For process & practices, hire a high-EQ systems thinker
Look for high EQ, a sense of how much method a team can absorb, and the instinct to introduce practices as suggestions rather than mandates. They must understand board-meeting and QBR inputs and continuously re-evaluate whether processes still work.
Pro tip They should treat the operating model as never 'set it and forget it' — constantly asking 'are these tools and processes still working for us?'
Watch out Avoid an Agile coach with no PM background — they default to Scrum optimization instead of product-management process.
- 3
For customer & market insights, hire a research-ops operator
Look for a user-research/UX background plus a process orientation — someone who knows what good interviewing looks like AND compulsively builds systems (participant databases, toolkits, tool governance, research certification/training).
Pro tip A research-ops specialist like Fidelity's Jen Cardello is ideal; if unavailable, find a user-researcher who wants to operationalize research.
- 4
Screen all candidates for the system-building instinct
Ask every product ops candidate to describe a process they hated in a past job and automated or systematized away.
Pro tip Perri calls this a great interview question for anyone in these roles: 'tell me about some kind of process you really hated and ended up trying to automate away or build a system around.'
In the wild
Cardello runs user insights and a research ops team that built a participant database, created research toolkits, governs research tools, and certifies employees to talk to customers up to compliance-defined levels — routing complex studies back to trained researchers.
→ Research was democratized safely within a regulated financial firm, putting good research within reach of more people.
Common mistakes
Hiring a database engineer for the data pillar
The role is extracting meaning from data, not engineering SQL tables — the wrong profile produces plumbing, not insight.
Throwing an Agile coach at the process pillar
Without PM experience they revert to optimizing stand-ups and Scrum rather than product-management processes.
Is it for you?
Best for
A leader writing the job spec and interview loop for a specific product ops pillar hire
Not ideal for
Very early one-person functions where the single hire must span pillars and profiles blur
From the transcript
“With the business data and insights, like you're looking for somebody who's really good at interpreting data, telling stories with data”
“What I wouldn't hire for that role as a first person is like a data It's not a database engineer.”
“this person really needs a super high EQ”
“tell me about some kind of process or some kind of thing that you had to do in your job that you really hated and…”
From the episode
The ultimate guide to product operations
Melissa Perri and Denise Tilles