How to build a UI/UX portfolio with no experience

Employers want to see how you think, not just how things look. Each project should show the problem, your process, the decisions you made, and the result.

A hiring manager may spend only a few minutes on your portfolio before deciding whether to interview you. Make those minutes count: lead with your strongest project, keep each case study scannable, and make your role and the outcome obvious.

Three to five strong, well-explained projects. Fewer than three looks thin; more than five usually means some are weak and dilute the rest. Aim for variety: at least one app or product flow, one website, and one project that shows research or problem-solving depth.

• Redesign an app or site you use daily, and explain why
• Design and ship a real site for a local business or friend
• Add one missing feature to a popular app, such as a clearer way to split a bill or track an order
• Improve the accessibility of an existing product: contrast, text size, and screen-reader labels
• Solve a specific user problem end to end, from interviews to a tested prototype
• A small design system to show consistency

1. Context: the product, the users, and your role
2. The problem: what was wrong and how you know
3. Research: interviews, competitor review, or usability tests, kept short
4. Ideas and trade-offs: the options you considered and why you chose one
5. The design: key screens, with notes on the decisions behind them
6. The outcome: what you tested or shipped, what changed, and what you learned

Keep it honest. If a project is a self-initiated concept, say so. Employers respect clear thinking on a concept far more than inflated claims about a fake client.

Self-initiated projects rarely come with sales figures, and that is fine. Show evidence of a different kind instead.

• Usability tests: "four of five testers completed checkout without help, up from two"
• Before and after comparisons of a confusing screen
• Feedback from the business owner or real users, quoted with permission
• For live sites: what the owner can now do, such as take bookings online
• What you would measure next if the product launched at scale

• One line on who you are and the kind of design you do
• Your three strongest projects first, each with a clear title and one-line summary
• A short about section with your background and the tools you use
• Easy contact details and a link to LinkedIn
• Nothing that slows it down: fast loading matters on mobile

Your own website is the strongest option, because it is itself a piece of work. Building it in Framer lets you publish a fast, responsive portfolio without code, and it doubles as proof that you can ship. Behance and Dribbble are useful for being discovered, and a short PDF version helps when an application form asks for an attachment.

• Only showing final screens with no process
• Too many shallow projects instead of a few strong ones
• Copying trends with no reasoning
• No live, shipped work at all
• Walls of text that bury the key decisions
• Spelling mistakes and broken links, which suggest a lack of care

Ship at least one real, live project (Framer makes this realistic), write a short case study for each, and keep the whole thing clean and easy to scan. One shipped product with a clear story beats ten static mockups.

If you are deciding which tools to learn for this, our comparison of Figma vs Framer explains how they fit together.

• Ask working designers for a 15-minute review; free mentorship platforms such as ADPList make this easier
• Share work in progress in design communities and ask specific questions
• Watch someone unfamiliar with your project try to understand it in two minutes
• Fix the top three issues, then ask again
• Then put the portfolio to work: our guide on getting a high-quality internship shows how to use it to land a first role