Portfolio guide

How to build a tech portfolio without writing code

You do not need to code to have an impressive portfolio. Here is how PMs, UX designers, business analysts, and data analysts build portfolios that get them hired.

Why non-developers need portfolios too

Coding portfolios are obvious. But hiring managers for non-technical roles also want evidence — not just resumes. A PM with documented case studies, a UX designer with annotated mockups, or a data analyst with a published dashboard all stand out from candidates with identical resumes.

The core principle: a resume tells hiring managers what you did. A portfolio shows them how you think. That difference is what separates shortlisted candidates from the rest.

What to put in your portfolio by role

Different roles call for different artifacts. Here is what hiring managers expect to see for each non-developer track:

Product Manager

A 1–2 page product case study (problem, research, decision, outcome)
A sample PRD or product brief
A metrics analysis (what you measured, why, what you changed)
A roadmap document with prioritization rationale

UX / UI Designer

2–3 end-to-end case studies in Figma or Notion (discovery → wireframes → prototype → outcome)
Show your process, not just your screens
Include research findings and design decisions

Data Analyst

A Kaggle notebook or Google Colab with a real dataset
A Tableau or Power BI public dashboard
A SQL analysis writeup with conclusions
A data story (chart + narrative explaining a real insight)

Business Analyst / QA / Scrum Master

Sample requirements document or user story map
A process improvement case study
QA: a test plan template with test cases

Where to publish your portfolio

The best portfolio is a live URL you can drop into any application. Pick the platform that matches your role.

Notion

PMs & BAs

Free, clean, and shareable with a single link. Perfect for PMs and BAs who want a polished written portfolio without a learning curve.

Figma Community

Designers

Public case studies visible to the entire design community. Recruiters can open your actual files and interact with your prototypes.

GitHub

Data Analysts

Data analysts can publish Jupyter notebooks, SQL files, and analysis writeups directly to a public repo.

Kaggle

Data Analysts

Public analysis notebooks with community voting and built-in exposure to data hiring communities.

Behance / Dribbble

UX / UI

Purpose-built for visual work. Strong social discovery means recruiters can find you without a direct link.

Personal site

Any role

Webflow, Framer, or Carrd give you maximum control over brand and layout. Worth it when you want to stand out beyond a shared doc.

The personal project option

If you have no relevant work experience, make something up — in the best way. Redesign an existing app. Analyze a public dataset. Write a PRD for an app idea. Document your job search as a product problem.

Hiring managers know entry-level candidates lack real experience. What they want to see is that you can think.

Good personal project starters: redesign an app you use daily, write a PRD for a feature you wish existed, analyze a public dataset from Kaggle or data.gov, or map the user journey for a frustrating experience you had recently.

What makes a portfolio entry stand out

Most portfolios are forgettable because they describe work without showing thinking. These three principles separate strong entries from weak ones:

Outcome-first framing

Start with the result, then explain how you got there. Hiring managers scan quickly — lead with the impact.

Specific, not generic

'Reduced checkout abandonment by 22%' beats 'improved the checkout flow'. Numbers and named outcomes do more than vague summaries.

Show your reasoning

The decisions and trade-offs matter more than the outputs. Explain why you chose one direction over another.

Next steps

Build your skills first

A portfolio is only as strong as the underlying skills. The learning paths will get you there.

Browse learning paths