How to find a product manager.

Product management is the hardest role in technology to screen, because the outcomes everyone claims are genuinely hard to attribute. A product grew; the PM was there. So were engineering, marketing, a funding round, and a competitor's mistake.

The title compounds it. A PM at a small company may own a whole product line and its commercial result, while a Senior PM at a large one owns one feature area inside someone else's strategy. And consumer, enterprise, and platform product management reward genuinely different instincts. Scope and product type are the search; the level is noise.

Job titles worth searching

Grouped by what the person actually does, because searching all43 at once produces a result set you cannot triage. Decide which group you need first — that decision does more for the search than any string below.

Where product managers actually are

Written work is the strongest signal available for this role. Product people who write about decisions — particularly ones that failed, or features they killed — reveal reasoning and judgement that no CV conveys and that interviews extract unreliably. The 'why we built' and 'what we got wrong' genre is small, public, and rarely mined by recruiters.

The community circuit is active and accessible. Mind the Product, ProductCon, and local product meetups publish speaker lists, and people who present are willing to defend their thinking publicly — which correlates well with the stakeholder communication the job actually demands.

An underused pool is former founders. People who have built and run a company have owned outcomes end to end under genuine constraint, and after an exit or a wind-down many want a defined role for a period. They rarely appear in product searches because their title was Founder, and almost nobody approaches them for product roles.

Boolean search strings

Written to be pasted as-is. Each one is built around an intent rather than a platform, since the useful question is what you are trying to find, not which site you happen to be on.

site:linkedin.com/in/ ("product manager" OR "head of product") ("B2B" OR "SaaS" OR "platform" OR "growth") "{city}"

(site:medium.com OR site:substack.com OR "product blog") ("we shipped" OR "we learned" OR "why we built" OR "we killed") -jobs -course

("technical product manager" OR "platform product manager" OR "API product") ("architecture" OR "developer experience" OR "SDK") -jobs

("growth product manager" OR "growth PM") ("A/B test" OR "experiment" OR "activation" OR "cohort" OR "retention curve") -jobs -course

("speaker" OR "panel" OR "talk") ("Mind the Product" OR "ProductCon" OR "Product School" OR "INDUSTRY") 2024..2026 -jobs

site:linkedin.com/advice/ intext:"Product Manager" intext:"{company}"

("product manager") ("PCI" OR "PSD2" OR "HIPAA" OR "KYC" OR "FDA" OR "regulated") -jobs -consulting

("founder" OR "co-founder" OR "previously founded") ("product" OR "startup") ("acquired" OR "shut down" OR "wound down") -jobs

Mistakes that cost the most time

1. Reading the title as a level

   Product titles inflate unevenly and mean different things by company size. A PM at a small company may own an entire product line and its commercial outcome, while a Senior PM at a large one owns a single feature area within someone else's strategy. Scope, decision rights, and what the person actually owned are the questions; the title answers none of them.

2. Ignoring the B2B and consumer divide

   Consumer product management is metrics-driven with rapid experiment cycles and large user numbers. Enterprise product management is customer-driven, with long sales cycles, small numbers of high-value users, and heavy internal stakeholder management. These reward different instincts, and moving between them is a genuine transition that takes time rather than a lateral move.

3. Taking outcome claims at face value

   Every product CV claims growth that the candidate contributed to, and attribution in product work is genuinely hard. What clarifies it is asking what they decided rather than what happened — which options were considered, what was cut, what they got wrong. Candidates who owned the decision answer easily; those who were present for it do not.

4. Underestimating AI PM title inflation

   The AI wave produced a large population of AI Product Managers whose experience ranges from shipping models in production to adding a chat feature built on a hosted API. Both are legitimate, but they are not comparable, and the title does not distinguish them. Ask what the model does, who evaluates it, and what happens when it is wrong.

5. Confusing product management with adjacent roles

   Product owner, product marketing, product operations, and technical program management are separate jobs with different centres of gravity. Adverts that blend them attract candidates from all four, and hiring a delivery-focused product owner into a strategy role, or a program manager into a discovery role, disappoints everyone involved.

6. Requiring an engineering background reflexively

   Technical depth genuinely matters for platform, API, and infrastructure products, where the PM must reason about system design. For most consumer and many B2B products it matters far less than customer understanding and judgement. Requiring a computer science degree by default removes strong candidates from design, operations, and domain backgrounds for no benefit.

Common questions

What job titles should I search for when hiring a product manager?

Search by product type rather than by level, since seniority titles are unreliable in this field. Consumer Product Manager, B2B Product Manager, SaaS Product Manager, and Marketplace Product Manager describe genuinely different disciplines. For technically demanding roles, Technical Product Manager, Platform Product Manager, and API Product Manager identify people who serve developer or internal users. Growth Product Manager and Monetisation Product Manager cover the experimentation-heavy end. Also search Product Owner, since in many organisations that title covers the same work.

What is the difference between a product manager and a product owner?

In principle, a product manager owns the why and what — strategy, discovery, prioritisation, and commercial outcome — while a product owner is a Scrum role focused on the backlog and delivery within a team. In practice usage varies enormously: many organisations use Product Owner for what is fully a product management job, particularly in Europe, and others use the titles interchangeably. Because of this, searching only one term misses people doing exactly the work you need. Judge on the scope described rather than the label.

Can a B2B product manager work on consumer products?

It is a genuine transition rather than a lateral move. Consumer product management is metrics-led, with large user populations, rapid experimentation, and decisions driven by behavioural data. Enterprise product management involves smaller numbers of high-value customers, long sales cycles, extensive stakeholder management, and roadmaps shaped by contractual commitments. The instincts differ: consumer PMs may under-weight individual customer needs, and enterprise PMs may over-weight them. Strong candidates make the move, but expect a ramp period rather than immediate fluency.

Does a product manager need a technical background?

For platform, API, infrastructure, and developer-facing products, yes — the PM must reason about system design and trade-offs to be credible with engineering and useful to users who are themselves engineers. For most consumer products and many B2B ones, technical depth matters considerably less than customer understanding, prioritisation judgement, and communication. Requiring a computer science degree by default removes strong candidates who came through design, operations, customer success, or domain expertise, and there is little evidence it predicts performance outside genuinely technical products.

How do I evaluate a product manager's claimed impact?

Ask about decisions rather than outcomes. Every product CV claims growth, and attribution in product work is genuinely difficult since outcomes depend on engineering, marketing, market timing, and luck as much as on the PM. The clarifying questions concern what the person decided: which options were considered and rejected, what was deliberately cut, what they got wrong and how they found out. Someone who owned the decisions answers these fluently with specifics. Someone who was present while others decided produces generalities.