A design portfolio is the one thing standing between you and a first interview. That is also why the blank version feels impossible to start.
Most people stall in the same spot: they start building the portfolio website before they have any real projects to put in it, so there is nothing to design around.
The fix is to flip the order. Get a few real projects first and write them up honestly, then treat the website itself as the last and easiest step.
What a portfolio is actually for
A hiring manager spends about a minute on a portfolio before deciding whether to keep reading. They are not counting your screens, they are trying to work out how you think.
So the portfolio has one narrow job: show that you can take a vague problem and turn it into a decision you can defend to a stranger.
Get projects before you build the site
You cannot write a case study about work you have not done. Before anything else, you need two or three projects with a real problem attached to each.
The strongest projects come from real people with a real need. A few places to find them:
- A local business with a broken website. Offer to redesign one page and talk to their customers while you do it.
- A nonprofit with a clunky donation flow. They rarely have a designer and they will let you ship something live.
- An open-source app with rough screens. Propose a change in public, then do the work where people can watch.
- The job you already have. Redesign the internal tool your team complains about and measure what got faster.
Each of these gives you something an invented project cannot fake, which is a real constraint and a real person who wanted the result. Reviewers can tell the difference in seconds.
Make your own project when you have nothing
Sometimes you have no client and no job to pull from yet. In that case, build something you actually want to exist and design it for real use.
Skip the unsolicited Spotify redesign. A made-up project only works when it solves a problem you can describe, for someone specific, with a constraint you did not get to choose.
You do not have to draw every screen from a blank canvas either. You can vibe code a working front end and start from a ready-made design system like SaaS Design, which your AI coding agent installs into the project from a single prompt.
Then restyle it and make your own calls, and write up which defaults you kept and which you overrode. Shipping something real with AI is the exact fluency hiring teams have started screening for, so the project pulls double weight.
Write three case studies, not a gallery
Three deep case studies beat ten pretty screenshots. A wall of Dribbble shots shows you can push pixels, but it says nothing about how you got there.
Reviewers hire on depth, not volume. Pick your three strongest projects and tell the full story of each, including the parts that did not go cleanly.
What goes in a case study
Every strong case study answers the same handful of questions in order. Keep it concrete and keep yourself in it:
- The problem. What was broken, and who actually felt it.
- The constraints. A deadline, no budget, a legacy codebase, a stakeholder who wanted it louder.
- Your role. What you did, kept clearly separate from what your team did.
- The process. A couple of real turning points, not every frame you ever drew.
- The outcome. A number is best. A quote from a real user is a close second.
The outcome line is where most junior portfolios go quiet, because measuring is harder than designing. Even a rough number helps, like "cut the checkout from five steps to three" or "support tickets about the form dropped by half."
Where to put it online
The platform matters far less than people think: a reviewer cares whether your work is clear and loads fast, not which tool built the page.
A few options that work, from least to most effort:
- Notion or a simple doc. Free, fast, and good enough to start. A clean page with three case studies is a real portfolio.
- A builder like Framer or Webflow. More control over layout and a custom domain, without writing code.
- Your own coded site. The most flexible, and a quiet proof that you understand the medium you design for. You can vibe code this one too.
Whatever you choose, put it on a custom domain you own and make sure it works on a phone. Recruiters open links on their phones constantly, and a portfolio that breaks on mobile reads as careless.
Mistakes that get portfolios skipped
Most rejected portfolios share a few habits, and none of them are about talent:
- Leading with a gallery of shots and no context.
- Ten thin projects instead of three deep ones.
- No outcomes, so every project ends at "and here is the final screen."
- Hiding your role on team projects, so a reviewer cannot tell what you did.
- A password wall or a slow load that makes a busy reviewer give up.
Fixing any one of these moves you ahead of a large share of the pile. They are effort problems rather than skill problems, which is good news when you are starting out.
Get it in front of people
A finished portfolio that nobody sees does not get you hired. Once it is live, put it where designers and hiring managers already are.
Post one case study publicly and write a few hundred words on a single decision you made and why. Share it on LinkedIn and in a design community or two, and add the link to your Wellfound profile and anywhere else you apply.
Referrals fill a lot of design roles before the public posting does much. The more your work is visible and easy to link, the more often your name comes up when someone asks around.
Common questions
How do I start a design portfolio with no experience?
Build a real project instead of waiting for one. Pick a small product you want to exist, design and ship it (you can vibe code the front end and start from a ready-made design system like SaaS Design), then write it up as a case study that shows the problem, your decisions, and the outcome.
How many projects should a design portfolio have?
Three strong case studies is the sweet spot for a first portfolio. Depth beats volume, so a reviewer would rather read three complete stories than skim ten thin galleries.
What should each portfolio project include?
The problem and who had it, the constraints you worked under, what you personally did, a couple of real turning points in the process, and the outcome. An outcome with a number, like a faster checkout or fewer support tickets, carries the most weight.
Where should I host my design portfolio?
Anywhere clear and fast works, from a simple Notion page to Framer, Webflow, or your own coded site. Put it on a custom domain you own and make sure it loads well on a phone, because the platform matters far less than the clarity of the work.
Do I need a fancy website for my portfolio?
No. A clean page with three well-written case studies beats an elaborate site with thin work, and plenty of hires come from a plain Notion or single-page portfolio.
How long does it take to build a design portfolio?
If you focus on shipping real projects rather than collecting courses, a hireable portfolio usually comes together in a few weeks to a couple of months. The slow part is doing the projects and writing them up, not designing the website.
What to do this week (choose at least two)
- Email one local business or nonprofit and offer to redesign a single page for free.
- If you have no client yet, start your own product project and vibe code a real first screen.
- Write one full case study with a problem, your role, and an outcome line.
- Put a three-project portfolio on a free Notion page and a custom domain, then test it on your phone.
Doing even two of these this week puts you ahead of most people who have studied design for a year without shipping a single case study.