A first design portfolio should hold three or four projects, not ten, and each one should show how you thought as well as what you made. That's the whole case. Juniors who pad their sites with every piece of coursework are asking a hiring manager to do a job the junior should have done: deciding what's good.
I come at this from the PR side, where I spent twelve years building media lists and pitching journalists. It's a strange angle for a design topic, but the parallel is exact. A pitch that lands has one story, led with the strongest angle, and the journalist can repeat it back in a sentence. A pitch with eleven angles gets deleted. Your portfolio is a pitch.
Why your first design portfolio structure should be edited, not archived
You're not building a museum. You're building an argument for one thing: hire me for this kind of work.
Pick the role first. If you want UX, a branding project that was really a logo exercise dilutes the case, however pretty it is. Pick projects that point the same direction, and cut the ones that don't, even when you're fond of them. (I always was. It never helped.)
The lead project matters most, because it's the one most people will open and some will open only. Put your strongest, most complete piece first, not your most recent. A recruiter skimming a pile of portfolios in an afternoon gives you the first screen and not much more.
Beyond Tick Boxes: Diversity Recruitment Strategies That Actually Transform UK Workplaces
Master the Virtual Hot Seat: 7 Video Interview Techniques Recruiters Don't Tell You
AI Governance Careers Surge in 2026: Why This Role Will Define the Next Decade
Show the mess: how to present process work
Here's where juniors go wrong in the opposite direction. They've been told employers want process, so they dump forty screenshots of sticky notes onto a page and call it a case study.
Process work isn't volume. It's decisions. Show the brief, the thing you got wrong first, what changed your mind, and what you shipped or would ship. One abandoned wireframe with two sentences on why you killed it tells a hiring manager more than a whole Figma board of tidy final screens.
Write it like a short story with a problem in it. What was the constraint? Who was the user, or the client, or the tutor pretending to be the client? Say so plainly. If a project was a university brief, label it as one. Nobody is fooled by a student project dressed up as live work, and the attempt costs you trust you'd otherwise have had.
For formats that suit different roles, I've written separately on creative portfolio formats that get design candidates hired, so I won't repeat that here.
The objection: surely more work shows more range?
It's the best argument against me, and part of it is fair. Early in a career, nobody knows what you're good at, and a wider spread might catch an employer's eye on something you didn't expect. Some studios do hire for potential and versatility, particularly smaller ones that need a designer to cover print, social and a bit of web.
But range is shown by how you solve different problems, not by how many files you upload. Two projects with clearly different challenges, say a mobile flow and a brand identity, show range just fine. Seven near-identical poster designs show you can export. And the risk of the big portfolio is that the weakest piece sets the average in the reader's head. People tend to remember the worst thing on the page more readily than the best.
Where to host it, and what to do next
A simple site on a platform like Behance or your own domain is enough. Nobody is marking you on the build. Make sure it loads quickly, works on a phone, and that your contact details are findable without hunting, because plenty of portfolios fail at that last step.
Then send it somewhere real. A portfolio nobody sees is a private hobby. Use it in applications, and if you want live roles to aim it at, browse creative jobs and tailor your top project to what the advert actually asks for. Swapping the lead case study per application takes ten minutes and is the single best edit you'll make.
The junior who wins the interview is rarely the one with the biggest folder. It's the one whose three projects made the reader want to ask a question. What would yours make them ask?