How do I write a product manager CV with no formal PM title?

Re-frame the work, don't invent the title. If you ran customer interviews, sized opportunities, sequenced engineering work or shipped features end-to-end, those are PM bullets even if your title was business analyst, founder, ops lead or engineer. Use a 'Product work' sub-heading inside your role and structure those bullets the way a PM would: bet, evidence, decision, outcome. Then in the summary, position yourself as transitioning into product with the clear angle (e.g. 'engineer moving into product for B2B SaaS'). UK hiring managers respect honest framing far more than retrofitted titles.

Should a PM CV include a portfolio link?

Increasingly yes, particularly for senior roles in the UK. A short Notion or personal site with two or three case studies, each running 400-600 words, gives hiring managers something to read alongside your CV and is the closest thing to a take-home test you can offer up front. Each case study should follow the same shape: context, bet, what you ran, what you learned, what you'd do differently. Don't overproduce it. A clean Notion page with real numbers beats a polished PDF with vague claims every time.

How important are metrics on a PM CV?

They are the single biggest differentiator on UK PM CVs in 2026. The shortlist signal hiring managers look for is whether you can quantify a business outcome, not just an engineering output. 'Shipped onboarding rebuild' is an output bullet. 'Lifted day-7 activation from 31% to 52%, adding £1.4m projected ARR' is an outcome bullet. If a metric is confidential, give the direction and rough scale ('roughly doubled', 'mid-six-figure annual saving'). If you genuinely don't know your numbers, that's a red flag, and the fix is to find them before you apply.

CV Example · Tech · UK 2026

Product Manager CV Example UK

Product manager CVs are the most over-written documents I see. After 12 years placing PMs into UK SaaS, fintech and marketplaces, the pattern is clear: the strong ones tell you what they decided and why. The weak ones tell you what they 'owned' or 'drove' without naming a single outcome. UK hiring managers in 2026 want commercial impact, evidence of customer research, and a clear sense of how you work with engineering. They are not impressed by 'led cross-functional team' for the fourth bullet running. The PMs who get shortlisted name the product, the bet they made, the metric they moved, and what they'd do differently.

By Alex · 12-year UK recruiter · Updated April 2026

Example header

James Okafor · Senior Product Manager · 7 years · Manchester / Hybrid

Personal statement / Professional summary

Senior PM with seven years shipping B2B SaaS into UK and EU mid-market. Background in payments and onboarding, currently leading the activation surface at a 200-person fintech. Comfortable in the messy half of product work: discovery interviews, pricing tests, sequencing trade-offs with engineering, and saying no to the loudest stakeholder in the room. Last year shipped a guided onboarding flow that lifted day-7 activation from 31% to 52% across 18,000 new accounts and added £1.4m to projected ARR.

Bullet point examples

Strong bullets follow the same shape: action verb, specific scope, quantified outcome. Use these as patterns, not as copy-paste templates — the numbers must be your own.

Led activation surface at fintech (200 staff, Series C)

Lifted day-7 activation from 31% to 52% across 18,000 new accounts in 7 months, adding £1.4m to projected ARR.
Killed two roadmap features after discovery research with 22 customers, reallocating 4 engineers to the activation work that actually moved the metric.
Ran a pricing experiment across 3 customer cohorts that increased trial-to-paid conversion by 19% with no measurable churn impact at 90 days.

Discovery and customer research

Built a continuous discovery cadence of 6 customer interviews a week, with synthesised insights shared in a 10-minute Friday read circulated to 40 staff.
Designed and ran 14 unmoderated usability tests on the new dashboard, surfacing the navigation issue that engineering had argued for two quarters wasn't real.

Cross-functional delivery

Sequenced a 6-month integrations roadmap with engineering, sales and partnerships, shipping 9 of 11 integrations on the original commit date.
Wrote PRDs and one-page bets for every quarter, with explicit kill criteria; closed 3 bets early in 2025, freeing roughly £400k of engineering cost.

Stakeholder and exec communication

Presented quarterly product reviews to the exec team and board, with a standard one-page format now used by all 5 product groups.
Mediated a long-running dispute between sales and engineering over custom features by introducing a written intake and scoring rubric, cutting ad-hoc requests by 60%.

Earlier role: associate PM at marketplace startup

Owned seller onboarding for a UK marketplace, growing weekly active sellers from 800 to 3,400 across 18 months.
Launched a referral programme that drove 22% of new seller signups in its first quarter at a CAC 70% below paid acquisition.

Skills section — what to list

Mirror the skills exactly as they appear in target job ads. The ATS reads this section literally — synonyms hurt match scores.

Product discovery (Teresa Torres method)Roadmapping and quarterly planningPRD and one-pager writingCustomer interviewsJTBD and opportunity solution treesPricing experimentsA/B testing and experiment designSQL (intermediate)Amplitude / MixpanelFigma (review and annotation)Jira and LinearOKR setting and trackingStakeholder managementGo-to-market planningCompetitive and market analysis

Product Manager-specific CV mistakes that get you binned

× Leading every bullet with 'Owned' or 'Led' without naming the outcome. UK hiring managers read 30 PM CVs in a sitting. Verbs blur; numbers don't.
× Listing the frameworks (RICE, MoSCoW, JTBD) instead of the decisions you made with them. Frameworks are table stakes; the trade-off is the story.
× Claiming credit for engineering or design work. PMs who write 'built and shipped' for things they didn't build get caught in 30 seconds at interview.
× No mention of what you killed. If everything on your roadmap shipped, you weren't prioritising hard enough, and any senior PM hiring manager knows it.
× Vague summary lines like 'customer-obsessed PM with a passion for data'. Hiring managers in 2026 want a positioning angle: which segment, which type of product, which stage of company.

Common questions

How do I write a product manager CV with no formal PM title?: Re-frame the work, don't invent the title. If you ran customer interviews, sized opportunities, sequenced engineering work or shipped features end-to-end, those are PM bullets even if your title was business analyst, founder, ops lead or engineer. Use a 'Product work' sub-heading inside your role and structure those bullets the way a PM would: bet, evidence, decision, outcome. Then in the summary, position yourself as transitioning into product with the clear angle (e.g. 'engineer moving into product for B2B SaaS'). UK hiring managers respect honest framing far more than retrofitted titles.
Should a PM CV include a portfolio link?: Increasingly yes, particularly for senior roles in the UK. A short Notion or personal site with two or three case studies, each running 400-600 words, gives hiring managers something to read alongside your CV and is the closest thing to a take-home test you can offer up front. Each case study should follow the same shape: context, bet, what you ran, what you learned, what you'd do differently. Don't overproduce it. A clean Notion page with real numbers beats a polished PDF with vague claims every time.
How important are metrics on a PM CV?: They are the single biggest differentiator on UK PM CVs in 2026. The shortlist signal hiring managers look for is whether you can quantify a business outcome, not just an engineering output. 'Shipped onboarding rebuild' is an output bullet. 'Lifted day-7 activation from 31% to 52%, adding £1.4m projected ARR' is an outcome bullet. If a metric is confidential, give the direction and rough scale ('roughly doubled', 'mid-six-figure annual saving'). If you genuinely don't know your numbers, that's a red flag, and the fix is to find them before you apply.