CV example

Product manager CV example

Product managers are hired for judgement and results. This example shows a PM whose bullets each explain the problem, the decision and the measurable outcome, which is exactly what interviewers will ask about.

Below you'll find a full example CV (also called a résumé), summaries for different experience levels, the skills and keywords employers search for, stronger bullet points, and the interview questions to prepare for.

Example CV for a fictional product manager, Grace Wanjiku. People, companies and figures are made up. View full size

Product manager CV summary examples

Your summary is the first thing a recruiter reads. Two or three sentences: who you are, your strongest evidence, and what you want next. Here is the example CV's summary, plus versions for other levels.

Example CV

Product manager with 6 years in fintech and mobile products. I run discovery with real customers, make clear prioritisation calls, and measure every launch against the metric it was meant to move.

Moving into product

Business analyst moving into product management, with 3 years working alongside product teams on requirements, user testing and launch metrics. Led the discovery for a feature now used by 10,000 customers.

Senior or group PM

Group product manager with 10 years building B2B SaaS. Grew a product line from $2M to $9M annual revenue and coach a team of 4 product managers.

Skills to put on a product manager CV

Hard skills

  • Product discovery and user research
  • Roadmapping and prioritisation frameworks
  • Writing clear requirements or product briefs
  • Analytics and experimentation
  • Basic SQL or product analytics tools
  • Agile delivery with engineering teams
  • Go-to-market planning

Soft skills

  • Decision-making with incomplete data
  • Stakeholder management
  • Clear writing
  • Saying no politely

Show soft skills through your bullet points rather than listing them on the CV itself.

Keywords recruiters and ATS look for

Many employers screen CVs with an applicant tracking system (ATS) that matches words from the job ad. These come up often in product manager postings. Use the ones that are true for you, in the same wording as the job you're applying for. To compare your CV with a specific job ad, use the free CV keyword checker, or have Litjob tailor your CV to the job description for you.

  • product manager
  • product roadmap
  • product strategy
  • user research
  • agile
  • scrum
  • stakeholder management
  • KPIs
  • A/B testing
  • product launch
  • cross-functional
  • go-to-market

For live figures, see the skills most requested in Product management job ads, updated weekly from thousands of postings.

Bullet points: before and after

Strong bullet points say what you did, how big it was and what changed. Compare:

WeakManaged the product roadmap.

StrongerRebuilt the roadmap around 3 customer outcomes, cutting low-impact work by a third.

WeakLaunched new features.

StrongerLaunched saved searches, used weekly by 40% of active users within 3 months.

WeakWorked with engineering and design.

StrongerLed a cross-functional team of 9 to ship a new onboarding flow that raised activation by 12%.

WeakDid user research.

StrongerRan 30 customer interviews that reshaped the pricing page and lifted trial-to-paid by 9%.

Only use numbers you can explain in an interview. An honest estimate (“about 30%”) is better than a made-up exact figure.

Tips for writing a product manager CV

1

Outcomes beat output

"Launched X" is output. "Launched X, which raised Y by Z%" is an outcome. Hiring managers screen for the second.

2

Show how you decide

Mention research, data or experiments behind your choices. It signals the judgement PM interviews test for.

3

Name the domain

B2B, consumer, fintech, health: domain experience matters a lot in product hiring, so make yours easy to spot.

4

Credit the team, own the result

Use "led" and "partnered with" honestly. PMs rarely build alone, and interviewers know it.

Common product manager interview questions

Your CV gets you the interview, and interviewers will ask about what's on it. Prepare for these:

Tell me about a product decision you got wrong.
Explain what you knew then, what happened, and what you changed in how you decide.
How do you prioritise competing requests?
Describe a framework you have actually used, and a real trade-off you made with it.
How would you improve our product?
Use the product beforehand. Pick one user problem, size it, and propose a small first step to test.
Which metric would you use to measure success for feature X?
Name one primary metric tied to the user’s goal and one guardrail metric.

Keep reading