Business · Mid-career

Product Manager Resume Example

This example suits a product manager with three to seven years of experience, including people who came into product from support, design, engineering or analysis. It shows how to describe discovery and prioritisation as well as delivery, and how to define the outcome metrics you quote.

The example resume

Laid out in the Galley template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.

Zanele Dlamini

Product Manager | B2B SaaS, Payments, Product Discovery

  • zanele.dlamini@example.com
  • +1 555 0126
  • Cape Town, South Africa
  • linkedin.example.com/in/zanele-dlamini

Professional summary

Product manager with five years in product and two in customer success, currently owning invoicing and payments for a small-business accounting platform with 60,000 active customers. Combines weekly customer interviews with product analytics to decide what to build, and works in a squad with one designer and six engineers.

Work experience

Product Manager

Sandbar Invoicing, Cape Town

Jun 2022 – Present

  • Owned the roadmap and quarterly OKRs for invoicing and payments, the product area behind 40% of company revenue
  • Led discovery for card payments on invoices through 32 customer interviews and a fake-door test, then launched with design and engineering in five months
  • Raised the share of invoices paid within seven days from 38% to 52% after launching payment links and automated reminders
  • Prioritised the backlog with RICE scoring and opportunity solution trees, cutting work in progress from 14 initiatives to five per quarter
  • Ran 11 onboarding A/B tests with the growth analyst, lifting activation (first invoice sent within 14 days) from 44% to 57%

Associate Product Manager

Protea Ridge Travel, Cape Town

Mar 2021 – May 2022

  • Wrote user stories and acceptance criteria for the booking-change flow and shipped self-service date changes, cutting related support tickets by 31%
  • Analysed funnel data in Amplitude and SQL to find a 22-point drop at the payment step; a redesigned form recovered 8 points
  • Coordinated the launch of a mobile itinerary feature with marketing and support, including release notes, help articles and agent training

Customer Success Specialist

Protea Ridge Travel, Cape Town

Jan 2019 – Feb 2021

  • Handled about 45 customer conversations a day by chat and email, tagging recurring problems for the product team
  • Compiled a monthly voice-of-customer report that led to three fixes being added to the roadmap

Skills

Discovery: customer interviews, usability testing, opportunity solution trees, prototyping in Figma

Delivery: roadmapping, OKRs, RICE prioritisation, user stories, Scrum and Kanban, Jira

Data: SQL, Amplitude, A/B testing, funnel and cohort analysis

Domain: B2B SaaS, payments, onboarding and activation, pricing

Education

Bachelor of Commerce (Information Systems)

Kleinberg University, Western Cape

2015 – 2018

Certifications

Certified Scrum Product Owner (CSPO)

Scrum Alliance

2021

Open this example in the resume builder Start empty with this template

Why this resume works

  • The summary says what she owns (invoicing and payments), for whom (60,000 active customers) and how the squad is made up, which tells a reader the level of the role at once.
  • Outcome metrics are defined as well as quoted. "Activation (first invoice sent within 14 days)" shows she chose the measure and can explain it, which is a core product skill.
  • Discovery is described with method and volume: 32 customer interviews and a fake-door test before engineering time was committed to card payments.
  • The prioritisation bullet records a decision to do less, cutting 14 initiatives to five per quarter. Saying no is hard to demonstrate on paper, and this line does it.
  • The customer success role is short but stays on the page, because it explains where her customer knowledge comes from and shows a credible route into product.

What employers look for in this role

  • Own the roadmap and backlog for a product or product area, and set goals such as OKRs
  • Run discovery through customer interviews, data analysis and prototype testing to decide what is worth building
  • Prioritise opportunities against strategy, customer value and engineering effort
  • Write requirements or user stories and work daily with designers and engineers through delivery
  • Plan launches with marketing, sales and support, including pricing and positioning where relevant
  • Define success metrics, monitor them after release and iterate
  • Communicate plans, trade-offs and results to leadership and other teams

Skills to consider

List only the skills you can back up with an example. These are the ones that come up most for this kind of role.

Discovery and strategy
Customer interviews, Usability testing, Opportunity solution trees, Jobs to be done, Competitive analysis, Product vision and strategy, Pricing and packaging
Prioritisation and delivery
Roadmapping, OKRs, RICE or similar scoring, User stories and acceptance criteria, Scrum and Kanban, Release planning
Data and experimentation
Product analytics (Amplitude, Mixpanel), SQL, A/B testing, Funnel and cohort analysis, North star and input metrics
Collaboration
Working with design and engineering, Stakeholder communication, Go-to-market planning, Writing product briefs

More bullet points to adapt

Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.

  • Retired a legacy reporting module used by under 2% of accounts, with a migration path and customer notices, freeing about one engineer of maintenance each quarter
  • Introduced tiered pricing after willingness-to-pay interviews and a pricing survey, raising average revenue per account by 9% with no rise in churn
  • Wrote the product brief and success metrics for a public API and signed up 14 integration partners in the first two quarters
  • Reduced 30-day churn among new accounts from 9% to 6.5% by redesigning the setup checklist with the design lead
  • Set up a weekly customer interview rota for the squad so that every engineer joined at least one call a month
  • Defined the north star metric (invoices paid through the platform) and the input metrics that three squads now report against

Words that recur in adverts

These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.

  • Product roadmap
  • Product discovery
  • Prioritisation
  • User stories
  • OKRs
  • Go-to-market
  • A/B testing
  • Cross-functional teams
  • Product analytics
  • Customer research
  • Backlog
  • Activation and retention
  • Product strategy
  • Agile

Which sections to include

Open with a summary that names the product area you own, its scale (users, customers or revenue share) and the team you work with. Experience comes next and should take most of the page; within each role, order bullets by outcome and make sure discovery, prioritisation and delivery all appear. A short grouped skills section follows. Education and any certification sit at the end, because product hiring tends to rest on evidence of judgement more than on formal qualifications. If you came into product from another function, keep that earlier role in brief to show where your customer or technical knowledge comes from.

Mistakes to avoid

  • Listing features shipped with no outcome. A launch is an output, so say what changed for customers or the business afterwards: activation, retention, conversion or revenue.
  • Writing "managed the engineering team". Product managers rarely line-manage engineers, and the phrase can suggest a misunderstanding of the role. Say you worked with the squad or led it through influence.
  • Quoting a metric without defining it. "Increased engagement by 20%" is vague, so state what was measured and over what period.
  • Leaving out discovery. If every bullet is about delivery, the resume reads like a delivery role, so include how you decided what to build and what you chose not to build.
  • Filling the skills section with framework names. One or two that you actually use are enough, and the experience section should show the thinking behind them.

Questions and answers

How do I show product impact if I cannot share revenue figures?

Use relative or product-level measures: the change in activation, conversion, retention or support tickets, or the share of customers adopting a feature. These are usually safe to share and often more meaningful than revenue. If even those are confidential, describe the direction and scale in words and be ready to explain at interview.

I am moving into product from another role. What should I emphasise?

Emphasise the product-like parts of your current work: time spent with customers, decisions you influenced with data, problems you framed and features you helped to specify or launch. Support, design, engineering, analysis and marketing can all supply these. Keep the earlier job on the page, as this example does with customer success.

Should a product manager resume list technical skills?

List the ones you use to do the job: SQL, an analytics tool, a prototyping tool and the delivery tools your team works in. Programming languages are only needed for a technical product role where you have real experience. Pasting the advert into the keyword checker shows which terms it repeats.

How does this differ from a project manager resume?

Product managers are judged on choosing the right problems and on customer and business outcomes; project managers on delivering agreed scope to time and budget. So this resume features discovery, prioritisation and metrics, while the project manager example features budgets, schedules, risk and governance.