Product manager CV example built on outcomes and discovery
A product manager CV shows outcomes rather than features: which user or business metric moved, what discovery found before the team built anything, and which ideas you stopped. Each role needs the product, the team and one measured result.1
Written 13 October 2026. CitedCV. How we write our guides
Before writing: list outcomes, not launches
Product managers tend to remember their careers as a release calendar. A hiring manager reads for something else: whether the things you chose to build changed what users did. Rebuild your history around that question before you touch a template.
- Write down each product or area you owned, with users (internal or external), team size and the period.
- Under each, note the two or three metrics the team was asked to move, and their values before and after your time.
- List the bets: features shipped, experiments run, ideas dropped after research. Mark which metric each was meant to move.
- Match bets to metric changes. Where the link is honest, you have a CV line; where it is a guess, you have an interview story at most.
- Note the discovery behind your strongest bet: how many users you spoke to, what you tested, what surprised you.
What hiring managers read for
Prospects says no formal qualification is needed to become a product manager, that employers usually prefer a business or marketing degree or a technical background for technical products, and that they rarely hire without at least two years of relevant experience. Its list of duties runs from collecting and analysing user feedback to set priorities, through roadmaps, to reporting on product performance. O*NET has no occupation titled product manager; its search for the phrase returns related ones such as Marketing Managers.
| What is read for | Where an official source names it | How it shows on a CV |
|---|---|---|
| Outcomes, not output | UK DDaT framework: managing product outcomes, defining measures of success | A metric with before and after in each role |
| Evidence from users | DDaT: applying user-centred insights; Prospects: analysing user feedback | A discovery line with method and finding |
| Prioritisation | DDaT: prioritised roadmaps, managing scope and risk | What you chose not to build and why |
| Value for money | DDaT: estimating benefits, weighing effort against value, business cases | A cost or revenue figure tied to a decision |
| Working across functions | Prospects: coordinating designers, developers and analysts | Team composition and who you aligned |
Product manager, product owner or project manager
The 2020 Scrum Guide makes the Product Owner accountable for maximising the value of the product and says it is one person, not a committee. A project manager is judged on scope, time and budget. If your title was Product Owner, keep it, and let the lines show the outcome work; if it was project manager and you want product roles, show the decisions about what to build, not only delivery dates.
Output lines versus outcome lines
| Output line | What it hides | Outcome line |
|---|---|---|
| Launched a new onboarding flow | Whether anyone completed it | Redesigned onboarding after 18 user interviews; activation within 7 days rose from 31% to 39% over one quarter |
| Managed the product roadmap | What was on it and what changed | Cut the Q3 roadmap from 11 items to 4 tied to retention; 90-day retention up 3 points |
| Worked with engineering and design | Your role | Led a team of 6 engineers and 1 designer on self-serve billing; support tickets about invoices fell by about 40% |
| Ran A/B tests | Results and decisions | Ran 9 pricing-page tests in a year; shipped 2, dropped 7, conversion to paid up from 2.1% to 2.6% |
Metrics that suit a product CV
- Acquisition and activation: sign-up conversion, first key action within a set number of days.
- Engagement and retention: weekly active use, cohort retention at 30 or 90 days.
- Revenue: conversion to paid, average revenue per account, expansion revenue.
- Cost and efficiency: support contacts per order, manual steps removed, cost to serve.
- Task success for internal or public services: completion rate, time to complete.
Your share of a team result
Product results are team results. Say what you did inside them: framed the problem, chose the metric, ran the research, made the prioritisation call. "Led" without that detail reads as a claim to the whole team’s work.
Showing discovery work on a CV
The GOV.UK Service Manual describes discovery as the phase for understanding the problem, users, constraints and how success will be measured, before committing to build. It says not to start building in discovery, that around 4 to 8 weeks is typical, and that deciding to stop is not a failure if the research supports it. Those three points translate into CV evidence.
- Method and scale: "Interviewed 22 small-business owners and reviewed 400 support tickets."
- Reframing: "Reframed a request for a reporting dashboard as a reconciliation problem; built a matching tool instead."
- Measurement: "Agreed the success metric with finance before the build: hours spent on month-end reconciliation."
- Speed: "Ran discovery in 5 weeks with a designer and an engineer before committing a quarter of team time."
Ideas you stopped are evidence too
One line about a bet you killed after research shows judgement better than a fourth launch. "Stopped a planned marketplace feature after a fake-door test reached 0.4% of target users; team moved to retention work" tells a reader you protect engineering time.
Example: product manager CV section
Example only. Tom Ellis is invented, and so are his employers and every figure. The shape is what matters: each role opens with the product and team, and every line names a metric or a decision.
Senior Product Manager, a B2B accounting software company, 2023 to present
- Own bank reconciliation for 38,000 small-business accounts; team of 7 engineers, 1 designer, 1 analyst.
- Discovery with 22 customers and 400 support tickets showed matching, not reporting, was the pain; shipped auto-matching, and average month-end reconciliation time fell from 3.5 to 1.2 hours.
- Stopped a planned multi-currency dashboard after a fake-door test; moved the quarter to retention, and 90-day retention of new accounts rose from 71% to 76%.
- Set the quarterly product goal and metric with sales and finance leads; wrote the business case that funded the second team.
Product Manager, a food delivery app, 2020 to 2023
- Owned restaurant onboarding: activation within 14 days rose from 48% to 61% after removing 5 of 12 sign-up steps.
- Ran 14 experiments on the restaurant dashboard; shipped 4, documented 10 that failed and why.
- Tools: Jira, Amplitude, SQL for own queries, Figma for reviewing prototypes.
Skills table mapped to the government framework
The UK government’s DDaT framework lists nine product manager skills across five levels, from associate product manager to head of product. Use its wording as a checklist, not as phrases to paste.
| Framework skill | Proof on a CV |
|---|---|
| Managing product outcomes | A metric you defined and moved |
| Applying user-centred insights | Research method, sample size and the decision it changed |
| Product management | A roadmap choice and what was cut |
| Creating value for money | A business case or cost figure |
| Agile and Lean practices | How the team’s delivery changed, measured |
| Stakeholder relationship management | Who you aligned and on what |
| Strategic ownership | A product goal or vision others adopted |
Certificates and qualifications
There is no licence for product managers in the UK, US or Türkiye sources we read. Prospects names bodies and qualifications that may help early on, including the Association of International Product Marketing and Management, the International Software Product Management Association, the Product Development and Management Association, the Market Research Society and PRINCE2, and says certification is usually not necessary in UK organisations. List one only if the posting asks for it or it fills a gap your experience leaves.
Tools such as Jira and Amplitude
Tools say little on their own for this role. One short tools line under a role is enough; an analytics tool earns a mention when you ran your own queries, because that saves an analyst’s time and shows you read data first-hand.
Proof: sources read on 13 October 2026
| Statement | Source |
|---|---|
| No formal qualification needed; two years’ experience; duties; professional bodies; certification usually not necessary | Prospects, Product manager (May 2026) |
| Nine skills, five levels, managing product outcomes | UK DDaT capability framework, Product manager (updated 28 February 2025) |
| Discovery: do not build, 4 to 8 weeks typical, stopping is not failure | GOV.UK Service Manual, How the discovery phase works |
| Product Owner accountable for value; one person, not a committee | The 2020 Scrum Guide |
| No O*NET occupation titled product manager | O*NET OnLine occupation search |
Who this example does not fit, and abroad
- Analysts moving towards product: start from the data analyst guide and add one discovery line.
- Technical product managers for ML products: the data scientist guide covers how to write model metrics.
- Software engineers moving into product: keep one stack line from the software developer guide and lead with outcomes.
For residence rules, see the Netherlands highly skilled migrant guide for IND salary bands and the UK guide for international applicants for sponsorship. The Germany CV format guide covers German conventions for a CV sent there.
Next steps
- Build the outcomes list and match each bet to a metric change you can defend.
- Rewrite every output line as an outcome line using the table above.
- Add one discovery line and one stopped-idea line to your current role.
- Check each line against the posting’s first three requirements and reorder.
CitedCV can write these lines from the products, metrics and dates you enter, in English, Turkish or German, and keeps each line linked to the fact behind it, so a retention figure on the page is one you supplied.
Questions people ask
How do I write a product manager resume with no PM experience?
Pull out the product decisions you already made in your current role, such as research you ran or features you prioritised, and write them as outcome lines with a metric.
What metrics should a product manager put on a CV?
The ones your product was judged on: activation, retention, conversion, revenue per account or cost to serve, each with a before and after value and the period.
Should I write product owner or product manager on my CV?
Write the title from your contract. The 2020 Scrum Guide defines the Product Owner as accountable for product value, so show that outcome work in the lines.
How do I show product discovery on a resume?
Give the method and scale, the reframed problem, the success metric agreed before building, and the decision that followed, including ideas you stopped.
Do product managers need a certification?
Usually not. Prospects says no formal qualification is needed and that certification is usually not necessary in UK organisations; experience carries the weight.
How do I describe a failed launch on a PM CV?
State what you tested, what the data showed and what the team did next. A clear stop decision with its reason reads as judgement, not failure.
Sources
- Prospects, Product manager job profilewww.prospects.ac.uk/job-profiles/product-manager
- UK Government Digital and Data Profession Capability Framework, Product managerunderstand-digital-data-roles-skills.service.gov.uk/role/product-manager
- GOV.UK Service Manual, How the discovery phase workswww.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works
- The 2020 Scrum Guidescrumguides.org/scrum-guide.html
- O*NET OnLine, occupation search for product managerwww.onetonline.org/find/quick?s=product+manager