building a pm portfolio
If any aspiring product manager has put in the effort to build some portfolios, build some products — they would have definitely used real tools while doing discoveries, while doing designs. I would expect them to have gone beyond their calling.
Why most PM portfolios fail
I have reviewed hundreds of PM portfolios. From students in our cohorts, from people applying cold, from engineers and MBAs and designers trying to break in. The vast majority of them fail — and they fail for the same reason.
They look like homework assignments.
A typical failing portfolio contains: a Netflix teardown, a Swiggy redesign, a generic “improve this product” case study, and maybe some wireframes. Every aspiring PM in India has some version of this. Hiring managers have seen it a thousand times. It tells them nothing except that you can follow a template.
Here is what hiring managers actually look for when they open a portfolio — and I say this as someone who has hired PMs:
1. Can this person identify a real problem? Not a theoretical one. Not “improve engagement.” A specific problem that a specific set of users faces, grounded in evidence.
2. Can this person think through a solution without jumping to wireframes? The solution space is where PM thinking lives. Most portfolios skip straight to the screen — which tells me you think PM is about drawing boxes, not making decisions.
3. Does this person have a point of view? A portfolio that says “here are three options, each has pros and cons” is a consulting deliverable, not a PM portfolio. I want to see you pick one and argue for it.
4. Is this relevant to me? If you are applying to a fintech company and your portfolio is full of food delivery teardowns, you have not done your homework. The best portfolios are targeted.
The reason Rohan got a callback with one page is that he did exactly these four things. He looked at the hiring manager’s actual product, found a real issue, proposed a solution, and showed how he would measure success. That one page demonstrated more PM capability than twenty pages of generic teardowns.
The five portfolio pieces that matter
You do not need twenty case studies. You need five pieces, each demonstrating a different PM muscle. Here is the stack that works:
1. A product teardown (the “I understand how products work” piece)
Pick a product you use daily. Not Netflix. Not Spotify. Pick something specific to your target domain. If you want to work in fintech, tear down Razorpay Checkout or PhonePe’s merchant flow. If you want to work in edtech, tear down Unacademy’s live class experience.
What to include:
- Who is the user? Be specific. “Small merchants doing under 50 transactions a day” — not “users.”
- What job is the product doing for them? Use the Jobs-to-Be-Done frame.
- Where does the experience break down? Find the friction. Every product has it.
- What is the business model, and how does the product experience serve it?
What to skip:
- Do not redesign the UI. You are not a designer.
- Do not list 15 features. Pick the three that matter most and go deep.
- Do not use screenshots with red circles and arrows. This is not a bug report.
A good teardown is 800-1200 words. It reads like an insightful product review, not a homework submission.
2. A product improvement proposal (the “I can identify and solve problems” piece)
Take the same product or a different one. Identify a real, specific problem. Propose a solution. This is the closest thing to actual PM work that you can demonstrate without being employed as a PM.
Structure it as:
- Problem: What is happening, who is affected, and how do you know? (Data, user reviews, your own experience — cite your sources.)
- Hypothesis: Why you believe this is happening.
- Proposed solution: What you would build. Not wireframes — a clear description of the experience change.
- What you would NOT build: This is where PMs differentiate from everyone else. Show that you can scope.
- Success metrics: How you would know it worked. Be specific. “Improve retention” is not a metric. “Reduce 7-day churn for new merchants from 35% to 25%” is.
- Risks and trade-offs: What could go wrong. What you are giving up.
3. A metrics analysis (the “I can think in numbers” piece)
Take a public product and build a metrics framework for it. Not vanity metrics — a connected set of metrics that tells the story of the product’s health.
For example: Zepto. What are the input metrics (order frequency, basket size, delivery radius coverage), the output metrics (GMV, contribution margin per order), and the health metrics (delivery time, NPS, rider churn)? How do they connect? If basket size drops, what downstream effects would you expect?
This piece demonstrates analytical thinking. Most aspiring PMs avoid it because it requires you to think hard about numbers. That is exactly why it stands out.
4. A strategy memo (the “I can think beyond features” piece)
Pick a company. Write a one-page memo on a strategic question they face. Not “how to improve the app” — something bigger.
Examples:
- “Should Zerodha launch a credit product?”
- “Why Swiggy’s Instamart is a better business than Swiggy Food — and what it means for their next three years.”
- “Meesho’s path to profitability: which bets are working and which are not.”
This piece shows you can zoom out from features to business. It is the rarest skill in aspiring PM portfolios, and the one that impresses senior hiring managers the most.
5. A side project or stretch project (the “I can ship” piece)
This is the hardest piece to create, and the most valuable. It is evidence that you have actually done something — not just analysed other people’s products.
Options:
- A tool you built. Does not need to be complex. A Chrome extension, a Telegram bot, a simple web app. The point is that you went through the cycle: identified a need, scoped a solution, built (or got someone to build) it, and put it in front of users.
- A stretch project at work. Did you volunteer to lead a feature? Did you run a user research study? Did you write a product spec that actually got built? Document it.
- A community contribution. Did you organize a PM meetup? Did you write a series of product analyses that got traction? Did you contribute to an open-source product’s roadmap?
As one of our mentors from Booking.com put it: people have been offered jobs purely based on the portfolio work they put out there. When someone doubts your skill set because you do not have the experience, put out content that proves it otherwise.
A hiring manager at a Series C fintech in Bangalore is reviewing portfolios for a PM role. She has 45 applications and 30 minutes before her next meeting.
Hiring Manager (Internal monologue): “Okay, first stack. Netflix teardown... Swiggy redesign... generic JTBD analysis... Skip. Next. Another Netflix teardown. Skip.”
Hiring Manager (Internal monologue): “Wait — this one wrote a spec for our reconciliation flow. She found a real bug in our merchant dashboard, proposed a fix, and estimated the revenue impact. How did she even find this?”
She found it by being a user. She ran a small online store and processed payments through the company's gateway. The friction was her own. The data was from her own dashboard.
Hiring Manager: “Get me a call with this person tomorrow.”
Forty-four other candidates had better credentials. One had a better portfolio — because it was about the hiring manager's product, not about Netflix.
A targeted one-pager about the company's own product outperforms twenty pages of generic case studies.
How to target your portfolio
The biggest mistake: building one portfolio and sending it everywhere. That is the resume approach, and it does not work for PM.
Rule: your portfolio should look different for every company you apply to.
I do not mean rewrite everything. I mean reorder, replace one or two pieces, and write a cover piece that connects your portfolio to the company’s problems.
Here is the targeting playbook:
Step 1: Research the company’s product. Use it. Not for five minutes — for a week. Find the friction, the gaps, the things that annoy you. Read their app store reviews (sort by recent, filter by 2-3 stars — that is where the real feedback is).
Step 2: Write a one-page improvement proposal for their product. This is your lead piece. It goes at the top of every application to that company. It demonstrates that you have done your homework and that you think like a PM.
Step 3: Select 2-3 pieces from your portfolio that are relevant to their domain. Applying to a B2B SaaS company? Lead with your metrics analysis and your strategy memo. Applying to a consumer app? Lead with your teardown and your side project.
Step 4: Write a 200-word cover note. Not a cover letter. A note that says: “Here is what I noticed about your product, here is what I think, and here are three pieces of work that show how I think about product problems.”
If you are applying to a ride-sharing company, your product portfolio should contain examples or case study breakdowns of Uber, Ola, or Rapido. If you are applying to a payments company, tear down Razorpay or Paytm. Bring familiarity. Show the hiring manager you already live in their world.
What format to use
People agonize over this. Notion vs personal site vs PDF vs Google Docs.
It does not matter. What matters is:
- It loads fast. A Notion page with 40 embedded images will make the hiring manager wait 10 seconds and close the tab.
- It is skimmable. Bold headings, short paragraphs, clear structure. A hiring manager will spend 90 seconds on your portfolio in the first pass. If they cannot find the substance in 90 seconds, you are out.
- It has no friction. No login walls. No “request access.” No broken links. Test it on your phone and on someone else’s laptop before sending it.
A simple personal site works. A well-structured Notion page works. A clean PDF works. A Google Doc with good formatting works. The format is not the point. The thinking is the point.
One practical recommendation: include wireframes and images where they help. When you are writing about a product improvement, a simple wireframe shows that you understand how users interact with products. Low fidelity is fine — you are not demonstrating design skill, you are demonstrating product thinking through visual communication. But do not use wireframes as a substitute for written analysis. The words carry the argument. The wireframes support it.
The LinkedIn portfolio strategy
Your LinkedIn profile is a portfolio whether you intend it to be or not. Every recruiter and hiring manager will look at it before they open your actual portfolio.
Here is how to turn it into a passive portfolio:
- Headline: Not “Aspiring PM” — that signals you have nothing to show. Use “Product Analyst” or “Building [specific thing]” or “[Current role] | Product thinker” — something that implies you are already doing the work.
- Featured section: Pin your two best portfolio pieces here. A teardown, a product spec, a strategy analysis. LinkedIn shows three featured items above the fold. Use all three.
- Posts: Write one product analysis per week. It does not need to be long. 300 words on why a recent product update was smart or misguided. Over 8 weeks, you have built a body of evidence that you think about products constantly. When a recruiter searches for you, they find a trail.
Do not write “I am excited to share that I completed a PM certification.” Nobody cares. Write about the products themselves. The best PM LinkedIn profiles read like product commentary, not career updates.
The common traps
Trap 1: The portfolio that proves you can follow a template. If your teardown uses the same headings as every YouTube tutorial on “how to do a product teardown,” it is invisible. Hiring managers have seen that template 500 times. Have a point of view. Disagree with something. Predict something. Make the reader think.
Trap 2: The portfolio that redesigns everything. “I redesigned Swiggy’s home screen.” Great — are you applying for a PM role or a design role? Redesigns demonstrate visual thinking, not product thinking. A PM portfolio should demonstrate problem identification, trade-off analysis, and decision-making. If your portfolio is mostly screenshots and wireframes, it reads like a UX portfolio with PM labels.
Trap 3: The portfolio that avoids numbers. If none of your case studies mention a metric, a conversion rate, a revenue estimate, or a sizing exercise, you are signalling that you do not think quantitatively. Every piece in your portfolio should have at least one number that you estimated or calculated. Even a rough estimate shows analytical instinct.
Trap 4: The portfolio you never finish. Perfectionism kills more PM portfolios than bad writing. A portfolio with three solid pieces published today is infinitely more valuable than a portfolio with seven perfect pieces that you are still polishing next month. Ship it. Iterate later.
Trap 5: The portfolio nobody sees. You wrote the portfolio, put it on a Notion page, and then applied through job boards with a link in your resume. Most applicant tracking systems strip links. Most recruiters do not click them. You need to actively send your portfolio to people — in DMs, in emails, in LinkedIn messages. The portfolio is not a passive asset. It is ammunition for a conversation.
You are applying for a PM role at a mid-stage B2B SaaS company in Bangalore that sells an HR tech platform to Indian enterprises. You have three days before the application deadline. You have a generic teardown of Slack and a redesign of Zomato in your portfolio. What do you lead with?
You have found the job posting. The company has 200 employees, raised a Series B, and their product is used by HR teams at mid-size Indian companies. Your portfolio currently has nothing related to B2B, HR, or enterprise software.
your path
This is a forcing function. Do not spend four weeks on this. Spend one weekend.
Saturday morning (2 hours): Write your targeted product teardown.
- Pick a product in the domain you want to work in. Something you actually use.
- Answer these questions in writing: Who is the user? What job does this product do for them? Where does it break down? What is the business model?
- Keep it under 1200 words. No screenshots. Just clear, sharp analysis.
Saturday afternoon (2 hours): Write your product improvement proposal.
- Take the friction you found in your teardown. Pick the most impactful one.
- Write: Problem (with evidence), hypothesis, proposed solution, what you would NOT build, success metrics, risks.
- Keep it under 1000 words. Include one rough wireframe if it helps — draw it on paper and photograph it.
Sunday morning (1 hour): Write your metrics framework.
- Pick a public product. Map input metrics, output metrics, health metrics.
- Show how they connect. What happens downstream when one moves?
- Keep it under 600 words.
Sunday afternoon (1 hour): Publish and distribute.
- Put it on Notion, a personal site, or a Google Doc. Whatever you can publish in 30 minutes.
- Share your teardown as a LinkedIn post (the first 200 words, with a link to the full thing).
- Identify three companies you want to apply to. For each, find the hiring manager or a PM at the company. Send them a message with your improvement proposal.
You now have three portfolio pieces and three targeted outreach messages. That is more than 90% of aspiring PMs ever produce. The strategy memo and side project can come later — these three are enough to start getting conversations.
The real test: if writing this took you under 4 hours, you probably went too shallow. If it took you more than 8, you are overthinking it. The sweet spot is that uncomfortable middle where you are making real analytical decisions, not just formatting.
You are a 2-year QA engineer at a Series B edtech startup trying to break into PM. You have written a detailed 1,200-word teardown of BYJU's onboarding flow, identifying five UX failures and proposing specific fixes with mockup sketches. A senior PM from Unacademy who reviewed it gave you candid feedback: 'The analysis is solid but the writing is too formal — it reads like a test report, not a PM doc.' You have three PM interviews scheduled in the next two weeks.
The call: Do you rewrite the teardown before using it in interviews, or submit it as-is while preparing your pitch?
You are a 2-year QA engineer at a Series B edtech startup trying to break into PM. You have written a detailed 1,200-word teardown of BYJU's onboarding flow, identifying five UX failures and proposing specific fixes with mockup sketches. A senior PM from Unacademy who reviewed it gave you candid feedback: 'The analysis is solid but the writing is too formal — it reads like a test report, not a PM doc.' You have three PM interviews scheduled in the next two weeks.
The call: Do you rewrite the teardown before using it in interviews, or submit it as-is while preparing your pitch?
Where to go next
- Not sure how to break in? The Realistic Path to PM
- Coming from engineering? From Engineering to PM — your engineering projects are portfolio pieces waiting to be rewritten
- Need to nail the interview once you get one: PM Interview Types
- Want to sharpen your product teardown skills? How to Approach Case Studies
- Need to think more strategically? Product Vision and Strategy