The most common objection to portfolio projects is a circular one: you need experience to build a portfolio, but you need a portfolio to get experience. This is not actually true. Portfolio projects work precisely because they prove you can do the job before you have the title. Hiring managers do not care whether the work was commissioned or self-initiated — they care whether it demonstrates the thinking they need on their team.
For Product Managers: write a real PRD
Pick an app you use every day and identify one feature you would add or one problem you would fix. Write a full Product Requirements Document: who the user is and what they need, what you are building and why, what success looks like in metrics, and what is explicitly out of scope. Include your prioritization rationale. A one-page PRD that shows clear thinking beats a ten-page PRD that covers everything without making a single decision. Put it on Notion and share the link.
For Data Analysts: a public dataset project
Download a public dataset from Kaggle, data.gov, or any government open data portal. Clean it, find a question worth answering, analyze it, and build a dashboard in Tableau Public or Looker Studio. The project should tell a story — not just show charts. What did you find? What surprised you? What would you recommend based on the data? Publish the dashboard publicly and link to it in your resume.
For UX Designers: a teardown case study
Choose an app with a known usability problem. Identify three specific issues, propose three solutions, and create wireframes to show what the improved experience would look like. Write up your reasoning — why is this a problem, who is affected, and why is your solution better? The written analysis is as important as the wireframes. Publish it as a Notion page or PDF case study.
For QA Engineers: a structured test suite
Pick any app — web or mobile — and test it systematically. Write ten real bug reports with full detail: steps to reproduce, expected behavior, actual behavior, environment, and severity rating. Include screenshots. This demonstrates exactly the skill companies are hiring for, and it takes a weekend.
For Business Analysts: a requirements document
Document the requirements for a fictional feature of a product you know well. Include the stakeholder list, the business problem being solved, use cases with success and failure scenarios, and a process flow diagram. This shows you can translate business needs into structured requirements — the core BA skill.
The format that works
Use a clean Notion page or a well-formatted PDF. Skip slide decks — they hide your reasoning behind bullet points. The goal is to show your thinking process, not just your output. Include what you would do differently next time.
How to present it in interviews
Lead with the problem you chose to solve and why you chose it. Walk through your process, not just your output. Show the decision points where you had options and explain why you chose what you chose. End with what you would do differently. This structure — problem, process, decisions, reflection — is exactly how experienced professionals present their work.