Template · Updated June 2026

The Product Manager résumé, with the trade-offs shown.

PMs face a unique résumé challenge: every meaningful outcome was a team outcome. The XYZ formula handles this well — by making your specific contribution the X and the team's measurable result the Y, you stay honest without underselling.

The full sample

Fictional candidate. Structural model — adapt the content to your real product work.

Priya Mehta

priya.mehta@example.com · 555-0199 · San Francisco, CA · linkedin.com/in/priyamehta

Summary

Senior Product Manager with 7 years shipping growth and platform features at consumer SaaS companies. Strongest at quantitative product work — A/B testing, activation funnels, retention modelling. Comfortable owning a single funnel end-to-end or partnering across 4-5 teams for cross-cutting initiatives.

Skills

Product: Roadmapping, A/B testing, user research, product analytics, prioritization frameworks (RICE, ICE)

Quantitative: SQL, Amplitude, Mixpanel, Looker, basic Python (pandas)

Cross-functional: Design partnership, engineering planning, stakeholder management, sales enablement

Experience

Senior Product Manager, Growth @ Northstar SaaS 2022 — Present
  • Led the onboarding redesign for the self-serve tier; activation rate (day-7 active) improved from 31% to 44% over Q2, validated by A/B test against a held-out 25% control.
  • Owned the pricing-page experimentation roadmap; ran 6 tests in 2024, of which 2 lifted paid conversion by >5pp and shipped, adding ~$1.4M in projected annual revenue per the finance model.
  • Drove the launch of the SSO + SCIM feature set for enterprise plans, unblocking 11 prospects worth ~$680K ARR who had named SSO as a blocker in pipeline notes.

Tools: Amplitude, Looker, SQL, Productboard, Figma

Product Manager @ Acme Collab 2019 — 2022
  • Re-architected the in-app notification surface; reduced "notification fatigue" survey score from 4.2/5 to 2.1/5 over two quarters by introducing user-controlled categories and frequency caps.
  • Partnered with the search team to launch federated search across 3 data sources; improved task completion in user-research sessions from 58% to 81% (n = 23 unmoderated).

Tools: Mixpanel, Notion, Linear, FullStory

Education

B.A. Economics — UC Berkeley, 2019

Why these bullets work: XYZ for PM work

The PM version of the XYZ formula needs one tweak: your contribution stays first-person, the team's outcome stays attributed honestly. "Led X, team shipped Y" lands better than "I shipped Y." Recruiters can tell the difference.

Bullet 1 — Activation

Led the onboarding redesign for the self-serve tier; activation rate (day-7 active) improved from 31% to 44% over Q2, validated by A/B test against a held-out 25% control.

Why it lands: "Led the redesign" is honest about your role (you didn't single-handedly code it), the activation metric is concrete with a before/after, and the validation method (held-out control) demonstrates analytical rigor without claiming you ran the stats.

Bullet 2 — Revenue impact

Owned the pricing-page experimentation roadmap; ran 6 tests in 2024, of which 2 lifted paid conversion by >5pp and shipped, adding ~$1.4M in projected annual revenue per the finance model.

Why it lands: The shipped/not-shipped ratio (2 of 6) is more credible than claiming every test won. The revenue figure is attributed to the finance model, not asserted as ground truth — interviewers don't have to take your word for it.

Bullet 3 — Sales-pipeline unlock

Drove the launch of the SSO + SCIM feature set for enterprise plans, unblocking 11 prospects worth ~$680K ARR who had named SSO as a blocker in pipeline notes.

Why it lands: Connects product to revenue via a documented mechanism ("named in pipeline notes") rather than the vaguer "drove sales." 11 prospects is small enough to be defensible in an interview — you can name the deals.

PM-specific tactics

Differentiate ownership from contribution

"Owned the pricing roadmap" implies you set strategy. "Led the onboarding redesign" implies you ran the project. "Partnered with the search team" implies you contributed but didn't drive. These three phrasings are all honest in different situations and recruiters know the difference. Get the right one for each bullet — the wrong one signals either modesty or overclaim.

A/B test details are credibility shortcuts

Naming the experimental setup (held-out control, sample size, statistical significance) signals quantitative literacy faster than any bullet about "data-driven decisions." If you ran a test, name how. If you didn't, don't claim the bullet was tested.

Don't invent metrics. Klepify won't let you.

PM is the role where AI tools most often invent metrics under JD pressure ("drove 47% engagement uplift"). Don't let them. Klepify's tailor uses a deterministic server-side fact lock to keep job titles, companies, and dates exactly what they are — and the diff highlighter surfaces invented numbers in the bullets so you catch them before exporting →

Klepify this template against your actual JD.

Add Klepify free. We'll rewrite bullets to surface the JD's must-have signals — where your real PM work supports them.

Add Klepify to Chrome