{{ p.category }}

{{ t }}

{{ p.title }}

{{ p.excerpt }}

U{{ author.name }} {{ p.readMins }} min read

{{ p.category }}

{{ p.title }}

{{ mo.sub }}

{{ m.tag }}

{{ m.t }}

{{ m.d }}

{{ m.left.t }}

✕{{ x.t }}

{{ m.right.t }}

✓{{ x.t }}

{{ m.big }}{{ m.label }}

{{ x.t }}

{{ m.label }}

✓{{ x.t }}

{{ x.t }}

{{ m.label }}
{{ x.t }}
{{ m.status }}

{{ m.label }}

{{ x.t }}{{ x.n }}

{{ x.t }}

{{ m.label }}{{ m.stepTxt }}

{{ x.t }}

{{ m.btn }}

{{ x.t }}

{{ m.q }}

{{ m.a }}

{{ x }}

{{ k.n }}

{{ k.v }}

{{ m.label }}

{{ m.status }}

{{ m.label }}

{{ st.n }}{{ st.t }}

{{ m.hub }}

{{ nd.t }}

AaAaAaAa

ButtonInput fieldTag

THE SHORT ANSWER

{{ p.answer }}

KEY TAKEAWAYS

✓{{ k }}

RELATED SERVICES

{{ b.t }}

{{ g.t }}{{ g.t }}

{{ g.t }}

{{ b.label }}:{{ b.t }}

{{ c.ini }}

{{ c.t }}

{{ c.d }}

{{ s.n }}

{{ s.t }}

{{ s.d }}

{{ h }}
{{ c.t }}

{{ b.alt }}

{{ g.alt }}

{{ b.title }}

{{ c.t }}

{{ c.s }}

{{ i }}

{{ c.t }}{{ c.s }}

{{ b.caption }}

{{ s.v }}

{{ s.l }}

{{ s.s }}

{{ b.caption }}

{{ b.title }}

{{ b.unit }}

{{ r.l }}{{ r.d }}

{{ b.caption }}

{{ b.title }}

A{{ b.a.t }}

{{ i }}

B{{ b.b.t }}

✓{{ i }}

{{ b.caption }}

{{ b.title }}

{{ t.d }}

{{ t.t }}

{{ b.caption }}

“

{{ b.t }}

{{ b.by }}

{{ b.title }}

{{ r.d }}

{{ r.l }}

{{ b.caption }}

{{ b.title }}

{{ m.n }}

{{ b.lo }}{{ b.hi }}

{{ m.n }}

{{ m.l }}

{{ m.d }}

{{ b.caption }}

{{ b.cs.client }} case study

Case study · {{ b.cs.client }} {{ b.cs.title }} {{ b.cs.text }}

{{ f.v }}{{ f.l }}

View case study →

SOURCES AND FURTHER READING

Frequently asked questions

{{ f.a }}

U

Written by {{ author.name }}

{{ author.role }}

Keep reading

More articles from across design, AI and marketing.

All articles

{{ r.category }} · {{ r.readMins }} min{{ r.title }}

Special Offer

25% Off Your Startup’s First Project

No Obligation
Quick Response
Exclusive for Startups

How to make a UI design portfolio that gets you hired

A UI design portfolio that gets you hired shows three to six strong, relevant projects as case studies. Each explains the problem, your role, the process, key decisions, the final design and the outcome. Keep it easy to scan, tailored to the roles you want, accessible and fast to load, and back it with a clear introduction and contact details.

Why your portfolio matters

For designers, the portfolio is often more important than the CV. It is where hiring managers see how you approach problems, how well you design and how clearly you communicate. Reviewers typically look at many portfolios for each role and may spend only a few minutes on each at first. A strong portfolio makes it easy for them to see relevant skills, understand your thinking and want to talk to you.

Many portfolios fail not because the work is weak, but because the presentation hides it: too many projects, endless screens without context, unclear roles or slow-loading pages. This guide explains how to avoid those problems. Our post on UX designer job descriptions shows what employers typically look for.

Choosing projects

Select three to six of your strongest projects
Prioritise work relevant to the roles you want
Include a mix, such as an app, a website and a design system
Use real projects where possible; label concept work clearly
Respect confidentiality: anonymise or get permission

If you are early in your career, well-documented personal or practice projects can work, especially if they show research, iteration and testing. Redesigning an existing product with a clear problem and rationale can demonstrate thinking as well as visual skill.

Structuring a case study

Section	What to include
Overview	Product, your role, team, timeline and tools
Problem	The user and business problem you set out to solve
Research	What you learned and how it shaped direction
Process	Sketches, wireframes, options and iterations
Key decisions	Why you chose one approach over others
Final design	Polished screens, flows and components
Outcome	Results, metrics or lessons learned

Keep each case study scannable, with clear headings, short paragraphs and visuals that support the story. A short summary at the top lets reviewers grasp the project in seconds before deciding to read more.

Showing process and decisions

Hiring managers want to understand how you think. Show early sketches, wireframes, alternative concepts and how feedback or testing changed your design. Explain trade-offs and why you made the choices you did. Avoid pasting every artefact; choose the few that best explain your reasoning. Our guide to wireframes, mockups and prototypes explains how these artefacts differ.

Making your role clear

Most real projects involve teams. Be specific about what you did: whether you led research, designed the interface, built the design system or collaborated on parts of the work. Reviewers value honesty, and clear descriptions of your contributions help them judge your fit for the role.

Showing results

Metrics: Conversion, task success, retention or efficiency changes.
Qualitative feedback: Quotes from users or stakeholders.
Launch outcomes: Shipped features and adoption.
Lessons learned: What you would do differently next time.

If you cannot share exact numbers, describe the direction and scale of change, or explain what you learned. Our guide to choosing the right UX metrics can help frame results.

Presentation and format

Your portfolio is itself a design project. Keep layouts clean and consistent, use readable typography, compress images so pages load quickly and make sure the site works well on mobile. Check accessibility: sufficient contrast, alternative text for images and keyboard-friendly navigation. A clear home page with a short introduction, your focus areas and links to case studies helps reviewers navigate. Our post on modern UI design covers visual foundations.

Write a clear introduction: Who you are, what you do and what roles you want.
Feature your best work first: Lead with the most relevant case study.
Keep navigation simple: Home, case studies, about and contact.
Optimise performance: Compressed images and fast loading.
Test on mobile: Many reviewers open portfolios on phones.
Make contact easy: Email, LinkedIn and CV download.

Tailoring for each application

Tailor your portfolio for each type of role. For a product design role, highlight end-to-end projects with research and outcomes. For a UI role, emphasise visual craft and design systems. For roles in the Gulf, bilingual Arabic and English work and right-to-left layouts can be a strong advantage. A short note in your application explaining which case studies are most relevant helps busy reviewers.

Keeping your portfolio current

Update your portfolio at least every few months, adding recent projects and retiring older or weaker ones. Keep notes, screenshots and metrics as you work, so writing case studies later is quick. Ask a few peers or mentors to review your portfolio and tell you what is unclear. Small refinements, such as clearer summaries or better image choices, often make a big difference in how reviewers respond.

Common mistakes

Showing too many projects without context
Only final screens with no process
Unclear roles on team projects
Slow-loading, image-heavy pages
Spelling mistakes and broken links
Sharing confidential work without permission

For case-study structure and presenting AI use, read how to build a UX portfolio that gets hired in the AI era.

Frequently asked questions

How many projects should a portfolio include?

Usually three to six strong, relevant case studies are better than many shallow ones.

Can I include concept projects?

Yes, especially early in your career, but label them clearly and show your process and reasoning.

Should I use a portfolio website or PDF?

A website is common and easy to share; a PDF version is useful for applications that request one.

How long should a case study be?

Long enough to explain the problem, process and outcome, with a short summary at the top for quick scanning.

Should my portfolio include Arabic projects?

If you are applying for roles in the Gulf, bilingual and right-to-left work can be a strong advantage; explain the challenges you solved.

Related articles