Most PM resumes lead with the tools and the ceremony. The postings mostly do not mention either.
Corpus: 62 company job boards, read on 2026-09-09. Every decision behind the numbers is written out further down.
Every open role on 62 company job boards was read; 421 of them carry a product manager or product management title. Each was checked against a fixed list of 44 terms.
What is reported is how many postings use a term, not how often. Nine mentions of “roadmap” in one posting counts once, exactly like a single mention in a bullet nobody reads. The ± is a 95% interval — where two rows sit closer together than that, treat them as tied.
Out of 421. The top twenty; the rest are tabulated further down.
01roadmap
85.5% ±3.4
02cross-functional
68.4% ±4.4
03prioritization
59.6% ±4.7
04stakeholder management
57% ±4.7
05enterprise
40.1% ±4.7
06product strategy
38.2% ±4.6
07go-to-market
33.7% ±4.5
08AI / machine learning
28.3% ±4.3
09experimentation
24.2% ±4.1
10API
23.5% ±4.1
11SaaS
21.6% ±3.9
12B2B
19.7% ±3.8
13engagement
19% ±3.7
14SQL
16.4% ±3.5
15retention
15% ±3.4
16requirements / PRD
13.1% ±3.2
17conversion
9.5% ±2.8
18user research
9.3% ±2.8
19KPIs
9.3% ±2.8
20Agile
8.6% ±2.7
The top four are not tools, methods or metrics. roadmap, cross-functional, prioritization, stakeholder management — in that order, 85.5% down to 57%. Every one of them describes how a product manager works with other people, and none of them is something you install.
The tool stack is nearly invisible. The most-named tool is SQL at 16.4%, and it is a query language rather than a product tool. Jira appears in 1.7% of postings, Figma 2.4%, Amplitude 1.7%, Confluence 0.7%, Looker 0.7%, Mixpanel 0.2%, Tableau 0.2%. Productboard appears in 0.
So is the Agile vocabulary. Agile is named in 8.6% of these postings, sprint in 3.1%, Scrum in 2.1%, Kanban in 0.5%. “Lean startup” or “lean product” appears in 0. A resume built around ceremonies and certifications is answering a question these postings mostly did not ask.
The generic word beats the specific one. Experimentation is named in 24.2% against 2.1% for A/B testing — roughly 12 times as many. The same pattern holds for metrics: engagement 19% and retention 15% against OKRs 3.3%, north star metric 4.5% and NPS 1.4%. Carry both forms.
An MBA is named in 5.5% of postings. Fewer than mention AI or machine learning (28.3%), and far fewer than mention prioritization (59.6%).
Want the version of this for one specific role rather than the aggregate? Run the posting and your resume through the free checker and it will name the terms that posting uses and yours does not.
The counting stops here; this part is judgement. Each row takes a term the postings actually use and shows the difference between claiming it and evidencing it.
roadmap
85.5% of postings
Claim: Owned the roadmap for X
Evidence: Owned a 3-quarter roadmap across 2 squads; cut committed scope 40% after a prioritization review and still shipped the top 5 bets
prioritization
59.6% of postings
Claim: Prioritized the backlog
Evidence: Replaced first-in-first-out intake with a scored model (reach, confidence, effort); 60+ requests a quarter now resolve without escalation
cross-functional
68.4% of postings
Claim: Worked cross-functionally
Evidence: Ran weekly design-engineering-data triage for a 14-person group; cut average decision latency from 9 days to 2
stakeholder management
57% of postings
Claim: Managed stakeholders
Evidence: Held the quarterly review with sales, support and finance; turned three competing feature asks into one sequenced plan the exec team signed off
experimentation
24.2% of postings
Claim: Ran experiments
Evidence: Stood up the experiment pipeline for onboarding; 22 tests in 2 quarters, 6 shipped, 1 reverted on a guardrail metric
Illustrative, not drawn from the corpus — the postings say which words matter, not how any individual should evidence them.
The Agile finding is real for this corpus and narrow beyond it. These are 62 technology companies hiring through one ATS vendor, most with established product organisations where a delivery method is assumed rather than advertised. A posting that does not say “Scrum” is not a company that does not run Scrum.
Whole categories of product employer are absent from this sample. Agencies and consultancies, systems integrators, government and defence contractors, and regulated industries are not represented — and those are exactly the employers that ask for CSPO, CSM or SAFe by name, sometimes as a hard requirement. This study measured no certification terms at all, so it says nothing about them either way.
The safe reading is the narrow one: if you are applying to product roles at technology companies, the words these postings use most are about roadmap ownership, prioritization and working across functions. Lead with those. Keep your methods and tools on the page, lower down, where they cost you nothing.
| Term | Postings | Share | ±95% |
|---|---|---|---|
| roadmap | 360 | 85.5% | ±3.4 |
| cross-functional | 288 | 68.4% | ±4.4 |
| prioritization | 251 | 59.6% | ±4.7 |
| stakeholder management | 240 | 57% | ±4.7 |
| product strategy | 161 | 38.2% | ±4.6 |
| go-to-market | 142 | 33.7% | ±4.5 |
| requirements / PRD | 55 | 13.1% | ±3.2 |
| user research | 39 | 9.3% | ±2.8 |
| product discovery | 17 | 4% | ±1.9 |
| user stories | 14 | 3.3% | ±1.7 |
| customer interviews | 7 | 1.7% | ±1.2 |
| Term | Postings | Share | ±95% |
|---|---|---|---|
| experimentation | 102 | 24.2% | ±4.1 |
| engagement | 80 | 19% | ±3.7 |
| retention | 63 | 15% | ±3.4 |
| conversion | 40 | 9.5% | ±2.8 |
| KPIs | 39 | 9.3% | ±2.8 |
| funnel | 24 | 5.7% | ±2.2 |
| north star metric | 19 | 4.5% | ±2 |
| OKRs | 14 | 3.3% | ±1.7 |
| churn | 10 | 2.4% | ±1.5 |
| A/B testing | 9 | 2.1% | ±1.4 |
| NPS | 6 | 1.4% | ±1.1 |
| cohort analysis | 5 | 1.2% | ±1 |
| Term | Postings | Share | ±95% |
|---|---|---|---|
| Agile | 36 | 8.6% | ±2.7 |
| sprint | 13 | 3.1% | ±1.7 |
| Scrum | 9 | 2.1% | ±1.4 |
| Kanban | 2 | 0.5% | ±0.7 |
| lean | 0 | 0% | ±0 |
| Term | Postings | Share | ±95% |
|---|---|---|---|
| SQL | 69 | 16.4% | ±3.5 |
| Figma | 10 | 2.4% | ±1.5 |
| Jira | 7 | 1.7% | ±1.2 |
| Amplitude | 7 | 1.7% | ±1.2 |
| Looker | 3 | 0.7% | ±0.8 |
| Confluence | 3 | 0.7% | ±0.8 |
| Mixpanel | 1 | 0.2% | ±0.4 |
| Tableau | 1 | 0.2% | ±0.4 |
| Productboard | 0 | 0% | ±0 |
| Term | Postings | Share | ±95% |
|---|---|---|---|
| enterprise | 169 | 40.1% | ±4.7 |
| AI / machine learning | 119 | 28.3% | ±4.3 |
| API | 99 | 23.5% | ±4.1 |
| SaaS | 91 | 21.6% | ±3.9 |
| B2B | 83 | 19.7% | ±3.8 |
| MBA | 23 | 5.5% | ±2.2 |
| B2C | 5 | 1.2% | ±1 |
Source. The Greenhouse job board API, published by companies so their own careers pages can render their listings. Nothing here was scraped and nothing is private. Point the collector at the same endpoint and you will get these numbers back; both it and the analyzer are in the repository.
Selection. Matched on the title alone, requiring “product manager” or “product management”. Internships are excluded. Nothing else is: because the title already pins the profession, a word like “developer” or “engineer” in one of these titles names the product domain rather than the job, and “Staff Product Manager, Developer Experience” is a product manager. A wider exclusion list was tried first and dropped 14 genuine PM postings for that reason.
Duplicates. One req advertised in four cities comes back as four records. Company, normalized title and content length together decide whether two records are the same posting — the rule is shared with the other studies here so their sample sizes stay comparable.
Counting. Document frequency: the share of postings mentioning a term at least once. “Discovery” is counted only in its qualified forms — product, customer, user or continuous discovery, or discovery process, work or phase. The bare word appears in roughly four times as many postings, but nearly all of that is ordinary English rather than the practice, so counting it would overstate the finding.
Three terms were dropped rather than reported. Linear reaches 0.7% loosely and 0.2% once “linear regression” and “linear algebra” are excluded — too rare to report and dirty at that size. Aha! appears in one posting, and its trailing exclamation mark makes a word-boundary match unreliable. “Platform” appears in 85% of postings but is ordinary English in a technology job description rather than something a candidate can act on, so reporting it would pad the table without informing anyone.
Limits worth stating. These are 62 mostly US technology companies hiring through one ATS vendor. They are not a random sample of product management jobs, and the mix skews to well-funded product companies. Terms outside the 44-term list are not counted, so absence here is not evidence of absence in the market — no certification terms were measured at all. It is a snapshot of open roles on 2026-09-09, not a trend.
adyen · affirm · anaplan · anthropic · asana · billtrust · bitgo · braze · brex · carta · checkr · chime · cloudflare · coinbase · databricks · datadog · discord · doximity · duolingo · elastic · faire · figma · fivetran · flexport · gitlab · gusto · gympass · hellofresh · instacart · intercom · justworks · klaviyo · lattice · launchdarkly · lyft · melio · mongodb · monzo · newrelic · okta · oscar · pagerduty · peloton · pinterest · pushpay · reddit · ridgeline · ripple · robinhood · sagesure · samsara · smartsheet · sofi · stripe · tide · twilio · upwork · vercel · verkada · webflow · zocdoc · zscaler
One posting will weight these terms differently from all 421. Paste yours against it and see which of its words your resume never uses.
Check My Resume →Or read the product manager keyword guide · the same method for software engineers · account executive postings, counted · the marketing corpus · what security postings name · accounting postings, counted · where SRE postings put their tools