PM resumes fail in a specific way: they list ceremonies ("ran standups, wrote PRDs, managed backlog") that every PM everywhere does. What differentiates is outcomes you drove, decisions you got right (including the ones where you said no), and the size of ambiguity you handled.

Structure

1. Header + optional link to a product-thinking artifact (a teardown, a public roadmap talk, a case writeup).
2. Two-line summary: "PM, {{years}}, {{domain — B2B SaaS / marketplace / fintech}}. I own {{kind of problems}}; recently {{one outcome with a number}}."
3. Experience: outcome bullets (below); name the product and its scale ({{users, revenue, team size}}) in the first line of each role.
4. Skills row, brief: discovery methods, experimentation, analytics tools, technical fluency level. One line — the bullets are the real evidence.

Impact bullets — before and after

The formula: scope owned + decision made + measurable consequence. Include one honest "decided NOT to build" bullet — kill decisions are the strongest senior signal there is.

Seniority signals

• APM/PM: execution quality and learning velocity — shipped things, instrumented them, iterated on real data.
• Senior PM: problem selection — bullets start from an ambiguous business goal, not a handed-down feature.
• GPM/Lead: portfolio and people — strategy across products, PMs coached, cross-org conflicts resolved with outcomes attached.

Common traps

• Claiming the team's metric without your mechanism — pair every number with what YOU changed.
• Feature-count bullets ("shipped 14 features") — throughput without outcomes reads junior at every level.
• Vague verbs: "drove", "supported", "helped" — replace with decided, scoped, killed, negotiated, re-prioritized.