Product manager roles are unusually competitive. Companies like Google, Meta, and Amazon reject 95% of PM applicants at the CV stage alone. Your CV has to prove strategic thinking, technical understanding, and proven impact in a very short space.
This guide walks through exactly what strong PM CVs include, with a full example and section-by-section breakdown. It covers entry-level, mid-level, and senior product manager CVs, with specific guidance on how to frame achievements.
What Recruiters Look For in a PM CV
Hiring managers for PM roles evaluate 4 things:
- Impact. What metrics did you move, and by how much?
- Ownership. What did you drive end-to-end, not just contribute to?
- Craft. Do you understand the PM discipline (roadmapping, research, prioritisation)?
- Stakeholder management. Have you led cross-functional teams to ship things?
PM CVs that fail tend to describe activities without outcomes. CVs that win tell stories of shipped products with measurable results.
Product Manager CV Structure
A strong PM CV follows this structure:
- Contact details (with LinkedIn and portfolio)
- CV summary (3-4 sentences highlighting scope and impact)
- Skills section (PM craft + technical + soft)
- Work experience (with metric-driven achievements)
- Education (degree and relevant coursework)
- Certifications and extras (PMP, CSPO, Product Led)
Full Product Manager CV Example
Aisha Khan
London, UK | 07700 900456 | [email protected]
LinkedIn: linkedin.com/in/aishakhan | Portfolio: aishakhan.co
Word Count Target: 2,000-2,500
---
Senior Product Manager | 6 Years Building B2B SaaS Products
---
Summary
Product manager with 6 years of experience in B2B SaaS, currently owning the enterprise tier at TechFlow. Launched 3 major products including an enterprise analytics module that now generates £1.2M in annual recurring revenue. Proficient in user research, A/B testing, SQL, and mixpanel. Specialises in 0-to-1 product launches and translating customer problems into shipped products.
---
Skills
- Product craft: Roadmapping, OKR setting, user research, A/B testing, product discovery, pricing, positioning
- Technical: SQL (intermediate), Python (basic), Mixpanel, Amplitude, Figma, JIRA, Confluence
- Cross-functional: Stakeholder management, technical writing, launch management
---
Work Experience
Senior Product Manager | TechFlow | Jan 2023 - Present
- Launched the enterprise analytics module, now generating £1.2M in ARR (16% of total revenue) within 9 months of launch
- Conducted 40+ customer interviews to shape the product requirements, and ran 3 concept tests with target accounts before building
- Led a cross-functional team of 8 (engineering, design, marketing, sales) through a 6-month build and launch cycle
- Defined and tracked 4 product north-star metrics; activation rate improved from 38% to 61% over the past year
Product Manager | Fintech Co | Sep 2020 - Dec 2022
- Owned the end-to-end onboarding experience, running 12 A/B tests over 18 months that increased activation from 29% to 54%
- Redesigned the pricing page based on 200+ customer interviews and competitive analysis, lifting free-to-paid conversion by 22%
- Managed a £150K quarterly product budget, prioritising roadmap items based on impact estimates and engineering effort
Associate Product Manager | Startup Co | Jul 2019 - Aug 2020
- Launched the first paid subscription tier from concept to release in 4 months, acquiring 400 paying customers within 60 days
- Managed the weekly release process across 2 product teams, publishing changelogs and coordinating cross-functional communications
---
Education
BA Philosophy, Politics and Economics | Oxford University | 2015-2018
- First-class honours
- Dissertation: "Behavioural Economics in Digital Product Design" (86%)
---
Certifications
- Certified Scrum Product Owner (CSPO) | 2022
- Product Led Certified | 2023
- SQL for Data Analysis (Udacity) | 2021
How to Write a PM CV Summary
Your CV summary should cover:
- Your PM title and years ("Product manager with 6 years...")
- Your domain (B2B SaaS, consumer, fintech, healthtech)
- A signature achievement (a launch, a metric shift, a product you led)
- Core capabilities (user research, A/B testing, specific tools)
- Your specialisation (0-to-1 launches, growth PM, platform PM, etc.)
Example:
"Product manager with 6 years of experience in B2B SaaS, currently owning the enterprise tier at TechFlow. Launched 3 major products including an enterprise analytics module generating £1.2M in ARR. Specialises in 0-to-1 launches and translating customer problems into shipped products."
The PM Skills Section
Group your skills by category to show breadth:
Product craft
- Roadmapping
- User research (interviews, surveys, usability testing)
- Product discovery
- A/B testing
- OKR setting
- Prioritisation frameworks (RICE, ICE, MoSCoW)
- Product analytics
- Pricing and packaging
- Go-to-market planning
Technical
- SQL (at a level you can discuss confidently)
- Basic Python or scripting (if you use it)
- Analytics tools (Mixpanel, Amplitude, Heap, Looker)
- Design tools (Figma, Sketch)
- Ticketing (JIRA, Linear, Asana)
- Docs (Confluence, Notion)
Soft skills (relevant to PM)
- Stakeholder management
- Technical writing
- Cross-functional leadership
- Executive communication
- Negotiation
For a breakdown of hard and soft skills for any CV, see our skills guide.
How to Write PM Achievement Bullet Points
The single most important thing in a PM CV is the achievements section. Follow these rules.
Rule 1: Lead with outcomes, not activities
Weak: "Led the redesign of the onboarding flow"
Strong: "Redesigned the onboarding flow, lifting activation from 29% to 54% over 6 months through 12 A/B tests"
Rule 2: Include the metric, the baseline, and the timeframe
Numbers without context mean little. "Improved conversion by 20%" is better as "Improved signup-to-paid conversion from 2.3% to 2.8% (20% lift) over a 12-week experimentation cycle."
Rule 3: Show ownership
"Contributed to" is weak. "Led," "Owned," "Delivered," and "Launched" are strong. Only use ownership verbs for work you genuinely owned.
Rule 4: Reference the scope
Scope signals seniority. Mention team size, budget, number of users affected, or revenue impact.
Rule 5: Use PM language
Specific PM phrases like "north-star metric," "jobs-to-be-done," "discovery work," "GTM launch," and "stakeholder alignment" signal that you understand the craft.
15 Strong PM Bullet Point Examples
Launch-focused
- Launched enterprise analytics module from concept to GA in 9 months, generating £1.2M in ARR
- Led the 0-to-1 launch of a new product line, acquiring 500 paying customers in the first 90 days
- Delivered the first cross-platform feature for our mobile app, used by 40% of DAUs within 30 days
Growth and metrics
- Increased free-to-paid conversion from 2.3% to 3.1% (35% lift) through 12 A/B tests over 18 months
- Grew north-star metric (weekly active teams) from 12K to 31K over 4 quarters
- Reduced customer time-to-value from 14 days to 4 days, contributing to a 12% churn reduction
Discovery and research
- Conducted 60+ customer interviews across 4 segments to shape the enterprise roadmap, producing a segmented insights deck used by sales, marketing, and engineering
- Ran 4 usability studies on the new dashboard, uncovering 12 major usability issues that shaped the final design
Team and leadership
- Managed a cross-functional team of 10 (4 engineers, 2 designers, 1 researcher, 2 GTM, 1 data) through a 9-month launch cycle
- Mentored 2 associate product managers, both of whom were promoted within 18 months
Strategic
- Defined and rolled out the company's first pricing framework, adopted across 4 product lines
- Rebuilt the quarterly roadmap planning process, reducing re-prioritisation time from 3 weeks to 3 days
- Ran the company's entry into the US market, generating £400K in pipeline within the first 6 months
Technical
- Shipped a self-serve API onboarding experience that cut integration time from 3 weeks to 2 days
- Defined the data schema and event taxonomy for product analytics, adopted across 3 product teams
PM CV Differences by Career Stage
Entry-level PM or APM (0-2 years)
Use a resume objective rather than a summary. Emphasise:
- Any adjacent experience (engineering, consulting, data, UX, operations)
- Internships, side projects, or product-related coursework
- Technical skills (SQL, analytics tools, design tools)
- Certifications (CSPO, product school, Reforge)
See our student CV guide for more on how to structure when you have limited direct PM experience.
Mid-level PM (2-5 years)
- Lead with your most impactful product launches
- Emphasise metrics (conversion, retention, revenue, DAUs)
- Show progression in scope (bigger teams, bigger roadmaps)
- Include PM-specific tools and frameworks
Senior PM / Group PM (5+ years)
- Lead with business impact and strategic contribution
- Emphasise cross-functional leadership and influence
- Include evidence of mentoring or managing PMs
- Show strategic work: pricing decisions, market entry, portfolio prioritisation
- Consider adding a strong resume headline at the top
PM CV Example Variations
For an APM (fresher or career changer)
Summary
Aspiring associate product manager with 2 years of engineering experience and hands-on exposure to product work through 3 cross-functional projects. Built and shipped 2 internal tools that reduced team reporting time by 40%. Completed the Reforge Product Strategy programme. Proficient in SQL, Figma, and Mixpanel.
For a Senior PM
Summary
Senior product manager with 8 years of experience leading B2B SaaS platforms through hypergrowth. Most recently led the launch of TechFlow's enterprise tier, scaling from 0 to £1.2M ARR in 9 months. 3x people manager with a track record of mentoring junior PMs to promotion. Specialises in 0-to-1 launches and international expansion.
For a PM Transitioning from a Technical Role
Summary
Product manager with 3 years of PM experience and 4 prior years as a senior engineer. Unusual depth in technical feasibility assessment and engineering collaboration. Led the launch of our core API product, adopted by 40+ enterprise customers in the first year. Proficient in SQL, Python, and system design review.
Common PM CV Mistakes
1. Describing activities instead of outcomes
"Worked on the onboarding flow" tells the reader nothing. "Increased activation from 38% to 61% through onboarding redesign" is memorable.
2. Overusing PM jargon without specifics
"Drove customer-centric innovation" is hollow. PM recruiters see through this immediately.
3. Missing technical skills
PMs are expected to be technical in 2026. Even if you are not an engineer, list SQL, analytics tools, and any coding you use.
4. No evidence of craft
Mention specific frameworks you have used (JTBD, RICE, OKRs, discovery sprints). Craft references signal that you understand the discipline.
5. Generic career progression
Show the scope increases. "PM at Startup (5-person team) → PM at Scale-up (50-person team) → Senior PM at Enterprise (500-person team)" tells a story.
6. Forgetting about mobile scanning
Best font for CV and clean formatting matter because recruiters often review on mobile.
ATS Optimisation for PM CVs
PM CVs often fail ATS screening because they are loaded with PM jargon that may not match the posting exactly. To fix this:
- Mirror the exact language from the posting. "Product-led growth" and "user research" should appear verbatim if the posting uses them.
- Include specific tools by name. "Mixpanel," "Amplitude," "Figma."
- Use clean formatting. Single column, standard headings. See our ATS guide.
- Quantify skills carefully. "5 years" triggers experience filters better than "several years."
Frequently Asked Questions
How long should a PM CV be?
One page for under 5 years of experience, two pages for senior roles. See our CV length guide for full guidance.
Should I include a portfolio link?
If you have one, yes. Product portfolios are unusual (unlike design or engineering), but a simple personal website summarising your case studies is valuable, especially for senior roles.
Do I need to be technical to be a PM?
Increasingly yes. Most PM roles in 2026 expect at least intermediate SQL, basic scripting, and comfort reading code. You do not need to be an engineer, but you do need to understand what engineers are talking about.
Should I list certifications like CSPO?
Yes, if you have them. They are not essential, but they signal investment in craft, especially early in your PM career.
What if my PM role does not have clear metric outcomes?
You likely have more metrics than you think. Think about revenue, adoption, engagement, retention, and efficiency. If you genuinely do not have metrics, describe the scope and scale instead (team size, customer count, roadmap breadth).
Key Takeaways
- Structure your CV around shipped products and business impact, not activities
- Quantify every bullet point (metric, baseline, timeframe)
- Group skills into product craft, technical, and soft skills
- Use specific PM frameworks and tools in your language
- Show progression in scope across your career
- Mirror job description language for ATS compatibility
- Include SQL and analytics tool proficiency (even at a basic level)