Growth Product Manager Portfolio: What to Include (and What to Cut)

A growth PM portfolio gets read differently than a generalist one. The hiring manager isn't asking "did you ship things" — every candidate in the pipeline shipped things. They're asking "can you find a lever, run a real experiment against it, and read the result honestly." A portfolio full of feature launches and roadmap slides doesn't answer that question, no matter how polished the case studies look.

1. Lead with the experiment, not just the win

Most PM portfolios describe an outcome: shipped X, grew Y by Z%. A growth portfolio needs the layer underneath that — what hypothesis you started with, what you tested against it, and why you expected it to move the number it moved. "Redesigned onboarding, activation up 14%" is a launch note. "Hypothesized that a 5-step signup was the drop-off point, tested a 2-step version against a control, activation up 14% at 95% confidence" is a growth case study. The second one is the one that gets you hired for a growth seat.

2. Show the funnel you owned, not just the metric you moved

Name the actual funnel stage — top-of-funnel acquisition, activation, retention, or monetization — and be specific about where your lever sat inside it. A reviewer scanning for a retention specialist versus an acquisition specialist needs to find that in the first sentence of the case study, not infer it from the metric name. If you owned more than one stage across your career, pick the strongest one or two case studies per stage rather than a shallow pass across all four.

3. Include at least one failed or flat experiment

A portfolio where every experiment won reads as curated, not honest — and experienced growth hiring panels know that most experiments don't win. Include one that flattened or lost, and spend more words on what you learned and what you tested next than on the loss itself. This is the single fastest way to signal that you actually run a disciplined test process instead of cherry-picking the two quarters that went well.

4. Quantify with rates and deltas, not vanity totals

"10,000 new signups" says nothing without a baseline. "Signup-to-activation rate up from 22% to 31% over one quarter, holding CAC flat" says everything: the lever, the size of the move, and the constraint you respected while moving it. Growth panels are trained to discount raw totals and weight rates, deltas, and statistical confidence — write the case study in the language they're already grading it in.

5. Show channel or lever diversity if you have it

If your experience spans more than one lever — paid acquisition, lifecycle email, in-product prompts, pricing and packaging, referral loops — show that range across two or three case studies rather than five variations on the same lever. Range signals you can be dropped into whichever growth problem the team has next quarter, not just the one you happened to work on last.

6. Keep one non-growth case study

Don't strip the portfolio down to experiments alone. One case study that shows product judgment outside of a growth loop — a prioritization call, a scope cut, a customer-discovery-driven pivot — proves you're a product manager who specializes in growth, not a growth hacker without product instincts. The mix is what gets you through a panel that includes a non-growth product lead.

Bottom line

A growth PM portfolio needs to prove a different muscle than a generalist one: that you can form a real hypothesis, test it against a baseline, and report the result — win or lose — without spin. Lead with the experiment design, name the funnel stage, include a loss, and quantify with rates instead of totals. For the general structure every case study should follow, see how to write a PM case study, and for how to talk about work you shipped with AI tooling, see how to show shipped AI work without it looking like vibes.

Product Leader builds this structure — case studies, metrics, and a video intro — from your CV or LinkedIn in under a minute. Start your portfolio here, free, no credit card.