Skip to main content
Career insights

How to Build a Portfolio When You Are Not a Developer

4 min read

Hiring managers for PM, UX, DA, and BA roles want evidence. Resumes describe what you did — portfolios show how you think. Non-developers who skip the portfolio step are competing against candidates who did not skip it. Here is exactly what to include and where to publish it.

Why non-developers need portfolios

The technical roles that dominate hiring advice — software engineers, data scientists — have GitHub as a default portfolio. Everyone else in tech has to build one intentionally. A PM without a portfolio is asking a hiring manager to trust that they can think clearly, without showing any thinking. That ask is much harder to fulfill than it needs to be.

What goes in a PM portfolio

One product case study structured as problem — research — decision — outcome. One sample PRD for a feature you would build for a product you use. One prioritization framework with rationale — show a feature list, apply a framework like RICE or MoSCoW, and explain your reasoning. The template matters less than the thinking. Hiring managers are not grading your document format; they are assessing whether you can identify the right problem and make a defensible decision.

What goes in a UX portfolio

Two end-to-end case studies in Figma or Notion that show your full process: research, synthesis, ideation, wireframes, prototype, and testing. Not just final screens. Final screens tell a hiring manager what you made. The process tells them how you think. Junior candidates who show their process clearly consistently outperform those with polished visuals but no documented thinking.

What goes in a data analyst portfolio

One Kaggle or Google Colab notebook with a real public dataset and a clear analytical question. One Tableau Public dashboard that tells a story someone would actually care about. One SQL analysis with written conclusions — not just the query, but what you found and what you would recommend based on it. The combination covers the three things every DA interview tests: SQL, visualization, and communication.

The no-experience move

Redesign an app you use. Analyze a public dataset you find interesting. Write a PRD for an app idea you have. Hiring managers know junior candidates lack real experience and are not expecting it. What they want to see is that you can think like someone who does the job — and that you cared enough to practice before applying.

Where to publish

Notion for PMs and BAs — clean, linkable, and signals you know the tools tech teams use. Figma Community for UX designers — putting your work where designers live shows professional self-awareness. Kaggle and GitHub for data analysts — these are the platforms where DA hiring managers actually look. Behance or Dribbble for visual design work. Pick the platform your target audience already uses, not the one that is easiest for you.

The one thing that makes a portfolio entry stand out

Outcome-first framing. Lead with the result, then explain how you got there. "Redesigned the onboarding flow, reducing drop-off by 23% in usability testing" lands harder than "I redesigned the onboarding flow." The result frames everything that follows. Even if your outcomes are from a personal project or a redesign exercise, framing them this way signals that you think like someone who measures success.

Keep learning

Ready to make the move?

Explore structured learning paths for every non-coding tech role — free to start, no signup required.

Browse all roles
← All articles