Building the Ideal PMM Portfolio

Jonathan opened by taking a quick read of the room: 90% of attendees were actively looking for a job, and most already had a portfolio of some kind. He adjusted accordingly. This was not going to be a theoretical session. It was going to be practical, direct, and interactive, and it was.

Jonathan and his co-founder Yi Lin Pei built 3AM Recruiting as PMM leaders who recruit, not recruiters who hire PMMs. Between them, over 20 years of product marketing experience, including hiring dozens of PMMs themselves. Everything in the session came from that direct experience, reviewing hundreds of portfolios, running candidates through interviews, and watching them succeed or fail in real time.

Start by defining what type of PMM you are

Before building a portfolio, you need to be able to answer one question: how do you boil down all of your experience into one phrase that needs no explanation? Cybersecurity PMM. Enterprise PMM. Storytelling-led product marketer. Someone who builds from scratch. Whatever it is, a recruiter or hiring manager scanning 600 resumes needs to see it immediately. If you leave it up to them to figure out, they might get it wrong, and you never get the interview.

Knowing your type also makes it obvious what goes in your portfolio. If you are a cybersecurity PMM, you include cybersecurity examples. If you specialise in dual-sided marketplaces, you show both the B2B and B2C components. The portfolio follows the positioning.

Know who is reviewing it

A startup founder and a Fortune 500 VP of Marketing are both technically evaluating product marketing. They are using completely different yardsticks. The founder wants scrappy, opinionated, zero-to-one thinking. The enterprise leader wants structured processes, rigorous frameworks, and large-scale launches. Send the wrong example to the wrong audience and you are out before you had a chance to make the case.

When to send it

The ideal time to share a portfolio is after the hiring manager round, not before. After that conversation, you know their priorities. At the end of the hiring manager interview, use the last few minutes to ask what their number one priority is for the role. Then send the portfolio with a note highlighting the piece that speaks directly to that priority. Generic portfolios sent to every application are a missed opportunity.

Three things a portfolio must do

If you take one thing from the entire session, this is it. Every portfolio needs to show three things:

• How you think. Your reasoning, your framework, your point of view. This is the hardest thing to fake with AI, and it is the most valuable signal a hiring manager can get. It shows how you will act in the role.
• How you work with others. Product marketing is cross-functional by definition. Hiring managers need to see that you can align teams without formal authority.
• That you can deliver. In this market, no one is hiring pure strategy PMMs. Thinking without execution is theory. It belongs in the classroom, not the real world.

Quality over quantity, and tailor to career stage

Three strong pieces beat ten average ones. And if you are reviewing 600 portfolios, you are not reading every piece in every one. Focus on one strong example for each of the three categories: thinking, cross-functional, execution. Then tailor the selection to the specific role.

Career stage also matters. Early career: show raw materials, prove you have done the work. Mid-career: show a mix of strategy and tactics. Senior: show leadership thinking, 30-60-90 day plans, team strategy, market expansion, not just execution. Sending early-stage work as a senior candidate is a fast way to lose the room.

Tell a story around every piece

Showing a work sample without context forces the hiring manager to guess. A one-pager used by four sales reps and a one-pager used by 400 are completely different things. Every piece in the portfolio needs five elements: what your specific role was, what challenge you were solving, what your approach was, the actual work sample, and the business impact. Stakeholder quotes are legitimate evidence if you do not have metrics. If you left the company, go back and ask for one.

Use I, not we

This was one of the most direct moments in the session. If you say "we launched the product," a hiring manager does not know whether you led it or assisted. For junior candidates, "we" reads as "my manager did the work." For senior candidates, "we" reads as "my team did the work and I took credit." Be specific about what you owned. Jonathan made a specific point to underrepresented candidates: the person who uses "we" and is more humble is often the more qualified candidate, and they lose the role for it. This is a real pattern. Use "I" intentionally, and use "we" only when the cross-functional collaboration is the point you are making.

Portfolio format: three levels

Not all portfolios are built the same. Jonathan laid out three levels, with Level 2 being the minimum to aim for:

• Level 1: A Google Drive folder with PDFs. Shows the work but provides no story. The hiring manager has to fill in all the context themselves.
• Level 2: A single PDF that combines all pieces and includes context for each one. One page of context, one page of sample. Clean, readable, hirable.
• Level 3: A website built using AI. It does three things at once: answers the AI capability question every hiring manager is asking, demonstrates storytelling, and shows technical creativity. Jonathan showed Naveen Watumul's portfolio as a live example, an entire product marketing portfolio built in the Spotify UI using Claude Code, with company summaries, key achievements, and embedded work samples. Naveen also wrote a step-by-step guide on how he built it — worth reading if Level 3 is your target. The creativity and the story are the point, not the specific format.

What not to do

• Do not share raw internal documents without context. They will be misread.
• Do not include work you cannot speak to in depth. If a follow-up question stumps you, the piece should not be there.
• Do not lead with purely executional pieces. Thinking and storytelling have to be present.
• Always check sharing settings. Around 30% of portfolios are inaccessible when reviewed.
• Never share anything under NDA. Not worth it.

What if you do not have real work examples?

Build a hypothetical one, and be completely upfront about it. The goal is to show how you think and what your work could look like. That is exactly what PMM Jam work qualifies as. If you built something during the jam, include it and explain it was created for a PMM sprint. The context is the point, not whether it was live in market.