A portfolio doesn't need ten polished projects — it needs two or three that clearly show how you think, presented in a way a busy reviewer can actually absorb in a few minutes.
Process matters more than the final shot
A beautiful final screen with no context tells a reviewer almost nothing about how you got there, and "how you think" is exactly what's being evaluated for a junior role — polish is assumed to still be developing. Show the messy early explorations, the constraint that changed your direction, the version you rejected and why.
Pick projects that show range, not repetition
Three case studies that all show the same skill (a nicely styled landing page, three times) tell a reviewer less than three case studies that each demonstrate something distinct — one showing UX problem-solving, one showing visual craft, one showing collaboration with engineering or handling real constraints.
A real, small project beats a big, fake one
A genuine, complete redesign of a real small tool or a personal project — with actual constraints and real decisions — is more credible and more interesting to discuss than a large, speculative concept project with no real constraints at all. Reviewers can tell the difference, and the real project gives you much more to talk about in an interview.
Write the case study for a skimmer
Structure each case study with a clear problem statement, a few key decisions, and the outcome — visible at a glance, before someone commits to reading every paragraph. Reviewers frequently decide whether to read the full case study based on this skimmable structure alone.
Your portfolio's job isn't to prove you're finished learning. It's to earn you a conversation where you can prove you're worth teaching.
Be ready to talk about a project you'd change now
Being able to critique your own older work honestly — "here's what I'd do differently now" — signals growth and self-awareness, which matters enormously for a junior hire, arguably more than the original work being flawless.
The takeaway
Two or three projects, each showing genuine process and real constraints, structured to be skimmable, plus honest self-critique of your own past work — that combination outperforms ten polished-but-shallow shots almost every time.
Keep reading
Related articles
The Beginner's Guide to Figma: Design Your First Screen
Frames, components, auto-layout and prototyping — everything you need to go from blank canvas to a polished mockup.
UX Design Principles Every Beginner Should Know
Good UX isn't about following trends — it's a small set of durable principles that show up in almost every well-designed product.
Color Theory for People Who Aren't Designers
The three rules that make any palette look intentional — without a design degree.
Discussion
Leave a comment
Your email stays private and is never published.