How to write a CV for a product manager role

"Led cross-functional teams" tells a hiring manager nothing

If your CV could be handed to someone applying for a programme manager job, a marketing manager job or a scrum master job with only the job title changed, it will read as generic to the person reviewing it — because it is generic. Product management has its own evidence base: metrics that move, artefacts you own, decisions you made under ambiguity, and a specific vocabulary for describing all three. A hiring manager who has done the job themselves is scanning for that vocabulary in the first ten seconds. If it isn't there, the assumption is that you don't have it, not that you forgot to write it down.

The core problem with most PM CVs is that they describe activity ("worked closely with engineering and design", "managed the product roadmap") instead of outcome and mechanism ("cut onboarding drop-off from X to Y by removing a verification step identified through funnel analysis in Amplitude"). The first sentence is true of almost every PM who has ever held the title. The second is only true of you.

What belongs at the top of the page

Put your most recent product ownership first, framed by what you were accountable for, not who you reported to. A hiring manager wants to know, within the first third of the page: what stage of product you worked on (0-to-1, growth, mature platform, sunset), what kind of product (B2B SaaS, marketplace, consumer app, internal tools, developer platform), and roughly what scale (user base, revenue band, team size). These four things tell an experienced PM more about whether you're a fit than a paragraph of adjectives.

If you owned a product area rather than a whole product, say so precisely — "owned checkout and payments for a marketplace with roughly 2 million monthly active users" is a real claim a reader can evaluate. "Responsible for key product initiatives" is not.

Name the methodology you actually used, not the one that sounds impressive. If your team ran two-week sprints with a backlog in Jira and quarterly OKRs, say that. If discovery was mostly informal customer calls rather than a formal Jobs-to-be-Done process, don't claim JTBD — a hiring manager who runs discovery properly will ask you to walk through it in the interview, and vague answers to a specific methodology question are worse than not having claimed it.

How PM experience is actually evidenced

Unlike regulated professions, there is no licence or registration body that verifies product management experience — no equivalent of a chartered status or a professional register. That means your CV has to do the verifying itself, through specifics that would be hard to fabricate convincingly:

• Metrics you moved and how you measured them. Not "improved user engagement" but the named metric (activation rate, D7 retention, NPS, churn, conversion at a specific funnel step) and roughly what it moved from and to. State whether the movement is attributed through an A/B test, a before/after comparison, or a cohort analysis — the method matters because it tells the reader how much to trust the number.
• Artefacts you owned. PRDs, roadmaps, discovery reports, pricing models, go-to-market plans. Naming the artefact ("wrote and maintained the PRD process for the platform team") is more credible than describing the general activity of "defining requirements".
• Launches, with your actual role in them. Did you own the launch end to end, or run product for one workstream inside a bigger launch owned by someone else? Say which. Overclaiming ownership of a launch is one of the easiest things for a reference check to unpick.
• Decisions under conflicting input. A short, specific example of a call you made when engineering wanted one thing, sales wanted another, and the data was ambiguous, with the reasoning and the outcome, is worth more than any adjective describing you as "strategic".
• Tools, named precisely. Jira or Linear for delivery, Amplitude, Mixpanel or Google Analytics for product analytics, Figma for reviewing (not necessarily producing) design, SQL or Looker/Metabase if you pull your own data, Productboard or Aha! if you ran roadmap prioritisation through a dedicated tool. Listing "Agile methodologies" as a skill says nothing; listing the specific stack you worked in lets a hiring manager gauge how self-sufficient you are with data.

Certifications: what carries weight and what is noise

There is no certification that functions as a licence to practise product management, the way there is in some regulated fields, and hiring managers in this field generally know it. Certified Scrum Product Owner (CSPO), the Pragmatic Institute's certifications, and AIPMM's Certified Product Manager are the ones you'll see most often on PM CVs. Whether they carry weight varies a lot by hiring manager and by company — some treat them as a neutral signal of basic vocabulary, particularly useful if you're moving into product management from an adjacent role like business analysis or engineering. Others give them no weight at all and will judge you entirely on the evidence above. Because the view is genuinely split and there's no independent study settling it, the safe approach is: include a certification if you have one, keep it brief, and never let it substitute for the evidence a hiring manager actually trusts — real product outcomes.

A relevant degree (computer science, business, a numerate subject) is worth stating plainly if you have one, but a degree in an unrelated field is not something you need to explain away. Plenty of experienced PMs come from law, teaching, or the sciences, and hiring managers in this field are generally used to that.

What PM candidates routinely leave off

The commercial number. Many PMs can state a revenue, cost-saving or retention figure they influenced but don't, either because they don't think of their work in those terms or because they assume it's implicit in the job title. It isn't. If you can trace your work to a number the business cared about, state it, even approximately, and say how you know it.

Which parts of the roadmap were yours versus inherited. CVs often read as if the candidate built the whole product strategy from nothing. Most PMs inherit a partially built roadmap and a set of existing constraints. Saying which parts you originated and which you executed against is more credible, not less impressive — it shows you can distinguish the two, which is itself a skill hiring managers look for.

Failed experiments. A launch that didn't work, or a feature you killed after a test showed it wasn't moving the metric, is often the strongest evidence you have of doing real product work rather than following instructions. Candidates leave these off because they feel like admissions. To an experienced PM reading your CV, an A/B test that failed and was acted on quickly is a better signal than three launches with no stated result at all.

Stakeholder management, specified. "Worked with stakeholders" could mean anything. Managing an engineering lead who disagrees with your prioritisation, a sales director pushing for a custom feature for one account, and a CEO who wants a pet feature shipped are three different skills. If you handled one of these, describe the actual situation in one line rather than the generic phrase.

Team size and reporting structure, precisely. "Managed a team" is ambiguous for a PM, since most PMs don't have direct reports in the traditional sense — they work through influence with engineers and designers who report elsewhere. Say what was actually true: "worked with a squad of four engineers and one designer" is a real, checkable claim; "led a team" invites the reader to assume a management structure you may not have had.

What to do next

Go through your last two roles and, for each one, write down three numbers you can defend if asked how you know them, one artefact you personally wrote or owned, and one decision you made where the answer wasn't obvious. That's the material the rest of the CV should be built around — everything else is framing. If you're short of that material for a role, that's worth noticing before you apply, not after an interviewer asks and you're improvising.

If what's actually stopping you is time rather than substance — you have the evidence but three hours per tailored application isn't sustainable alongside a full-time job — jobmarket.pro reads each advert in full and builds the application from a single profile of your real experience, rather than reusing a generic version.