UX/UI Designer Resume Projects: 12 Case Study Ideas
Nobody Hires a Designer for a Pretty Dribbble Shot#
A pile of polished screens tells a recruiter that you can use Figma. It does not tell them whether you can decide what to build, talk to a real person or defend a choice in a meeting.
A good junior portfolio has two or three case studies that show how you think. The twelve ideas below are organised along the design process itself, from research to handoff, so you can pick one idea per stage and end up with a portfolio that covers the whole job.
Tools used: Figma (free starter plan) or Penpot (open source), plus free survey and note tools. Hour estimates assume you already know the basics of your design tool.
Get the next guide by email
New guides and fresh jobs in one short email. Free.
Stage 1: Research (prove you can listen)#
1. Fix the booking flow at a real local business. Walk into a barber, physio clinic or yoga studio and ask if you can watch how clients book. Record the friction points, then redesign the flow. The artifact is a three-page case study with a before and after prototype. You need the owner's permission to show their name, so ask early. Around 30 hours.
Resume bullet: "Observed 6 customers booking at a local clinic, identified 3 drop-off points and prototyped a flow that removed two steps."
2. Run a tiny usability test on an app you did not make. Pick a public government form, a council parking page or a bank sign-up. Recruit five friends of friends, give each one a task and record where they stall. The artifact is a findings deck with severity ratings and short clip timestamps. Be honest that five people is a small sample. 15 hours.
Resume bullet: "Moderated usability sessions with 5 participants and ranked 9 issues by severity."
3. Interview people who switched from a competitor. Choose two note-taking or budgeting apps. Talk to four people who moved from one to the other and ask why. Turn the stories into a jobs-to-be-done map. This one needs no screens at all, which makes it stand out. 14 hours.
Resume bullet: "Conducted 4 switching interviews and synthesised motivations into a jobs-to-be-done framework."
Stage 2: Structure (prove you can organise)#
4. Reorganise a bloated help centre. Take any software company's public support site and run an open card sort with friends using a free tool or index cards. Propose a new navigation tree. The artifact is a before and after sitemap and a tree test result. 18 hours.
Resume bullet: "Restructured a 120-article help centre sitemap using card sorting and validated it with a tree test."
5. Map one stressful day as a service blueprint. Choose something like renewing a passport or a driving licence in your country. Draw the user steps, the paperwork, the waiting and the back-office actions underneath. The artifact is one large Figma or FigJam board plus a two-page summary. 20 hours.
Resume bullet: "Mapped a 9-step government renewal journey as a service blueprint and highlighted 4 pain points."
6. Design for a bad connection. Redesign a ride or food order screen for a user on a slow mobile network with a cracked screen and one hand free. Show your loading, offline and error states. The artifact is a state matrix and a clickable prototype. Few juniors design the ugly states. 22 hours.
Resume bullet: "Designed offline, loading and error states for a delivery flow and documented 14 edge cases."
Stage 3: Interface (prove you have taste and rules)#
7. Build a small design system, not a UI kit. Do ten components in Figma with variables for colour and spacing, plus a short page on when not to use each one. Publish it as a Figma file with a one-page rationale. 35 hours.
Resume bullet: "Created a 10-component system using Figma variables and documented usage rules."
8. Redesign a screen to pass WCAG 2.2 AA. Take one popular but cluttered page and audit it with the WebAIM contrast checker and a screen reader on your own laptop. Fix colour contrast, focus order and target sizes. The artifact is an annotated before and after with the specific criteria cited. 16 hours.
Resume bullet: "Audited a checkout page against WCAG 2.2 AA and resolved 11 failures."
9. Design a dashboard for someone who hates dashboards. Choose a user like a nurse, a warehouse supervisor or a farmer, and design a one-screen view that answers a single question. Cut everything else. Hours: 20.
Resume bullet: "Designed a single-question operations view, cutting 12 metrics to 3 after interviews."
Stage 4: Words and motion (prove you sweat details)#
10. Rewrite the microcopy of a confusing app. Collect twenty error messages, button labels and empty states from a real product. Rewrite them in plain language and show both versions side by side. The artifact is a spreadsheet and a short article. 10 hours. This is the cheapest idea on the list and a favourite with content designers.
Resume bullet: "Rewrote 20 interface strings to plain language and tested comprehension with 8 people."
11. Prototype one animation that explains something. A password strength meter, a money transfer confirmation or a map pin drop. Use Figma Smart Animate or a free tool like Rive, then write down why the motion exists. 12 hours.
Resume bullet: "Prototyped a confirmation animation and documented timing and purpose in a motion spec."
Advertisement
Stage 5: Handoff (prove you can work with engineers)#
12. Take your own design all the way to code. Pick your favourite case study screen, write a simple spec, then build it in plain HTML and CSS or a free no-code tool. Compare the build to the design and log every difference. The artifact is a live page and a spec document. 25 hours.
Resume bullet: "Specified and built a responsive screen from my own Figma design and reconciled 8 differences."
Anatomy of a Case Study That Gets Read#
Hiring managers skim. Most spend a minute or two on a case study before deciding whether to read on, and that is a guess from how designers describe the process, not a measured figure. Build for the skim.
Open with a three line summary: the problem, your role and the outcome. Then use short sections with one image each. A typical order that works:
- Context. Who is this for and what was going wrong? Two sentences.
- What you learned. Two or three real quotes or observations from the people you talked to. Only quote what was actually said.
- What you tried. Show one rejected option. It proves you made a decision rather than drawing the first thing that came to mind.
- What you shipped. The final screens or flow, annotated with the reason for each choice.
- What happened. Even a small result counts: "four of five testers finished the task unaided, up from two".
- What you would change. One honest paragraph.
Common Portfolio Mistakes#
- Redesigning a famous app with no research. It is the most repeated case study in junior portfolios. If you do it, add real interviews and a clear reason.
- Hiding behind process diagrams. A glossy double diamond with no evidence behind it reads as decoration.
- Mobile only. Show at least one responsive state, because many employers build for desktop as well.
- Fake metrics. If you did not measure a lift, do not claim one. A small test result you can explain beats a made up percentage.
- No accessibility thought. Even a short note about contrast, text size and keyboard use signals maturity.
A Realistic Schedule#
If you can give ten hours a week, the whole set of three case studies takes about two months. A pattern that works: weeks one and two for research, week three for structure, weeks four to six for interface work, and the last two weeks for writing and a friendly review from another designer. Writing takes longer than people expect, so budget for it from the start.
How to Pick#
- Zero experience: ideas 2, 10 and 8.
- Applying to a startup: ideas 1, 6 and 12.
- Applying to a large company or agency: ideas 4, 7 and 5.
Aim for three case studies, not twelve. Each one should answer: what was the problem, who did you talk to, what did you try, what did you drop and what happened.
Putting It on the Resume#
Keep one line per case study with a link, then run the whole document through the free ATS checker against a posting that interests you. Design job posts often name tools like Figma, FigJam and usability testing, and a keyword match matters more than most designers expect. Pair this with the UI/UX designer cover letter examples and, if you want the general principles of writing about projects, the project descriptions guide.
Choose one idea, set a deadline and tell a friend. Then go and talk to a real person.
Advertisement
Send this to whoever has the interview this week.