In this guide
Role-specific resume and interview guides
UX designer resume: research, decisions and usability evidence
How UX designers can show research, problem framing, design decisions, usability results and accessibility work on a resume and in linked case studies.
What separates UX evidence from visual design evidence
Visual polish matters, but UX roles are judged on process and outcomes: who you talked to, what you learned, which options you rejected and how you measured whether users could complete the task. A resume full of tool names and adjectives leaves out exactly the parts interviewers will ask about.
| Stage | Evidence to include |
|---|---|
| Research | Methods used, number of participants, what changed as a result |
| Framing | The problem statement or user need you defined |
| Design | Options explored, the decision and the reason |
| Testing | Usability tests run, task success or error changes |
| Delivery | Hand-off to engineering, design system contributions |
| Accessibility | Standards applied, audits or fixes you led |
Rewritten UX bullets
Illustrative example
Product designer in a software company
Before
Designed new features for the mobile app.
After
Redesigned the mobile bill-payment flow after eight usability sessions showed people could not find saved payees; the new flow raised task completion in follow-up tests and cut related support contacts.
Illustrative example
Designer working on accessibility
Before
Made the website accessible.
After
Audited the checkout against WCAG success criteria with the front-end team, fixing focus order, contrast and form error messages, and added accessibility checks to the design review template.
Illustrative example
Researcher moving into design
Before
Did user research.
After
Ran 15 interviews with care coordinators, mapped their weekly scheduling process and prototyped a shared calendar view that the product team took into development.
Case studies the resume should point to
A UX case study should show
- The problem and why it mattered to users and the business.
- Your role, and who else worked on it.
- Research or data that shaped the work.
- At least one rejected option and why.
- How the result was tested or measured.
- What you would change next time.
Confidential and unreleased work
Much UX work sits behind logins or agreements. You can describe the problem, method and outcome without showing screens, recreate a simplified flow with invented content, or present the work in an interview by permission. Say clearly when a case study is anonymised.
Common questions
Do UX designers need a portfolio?
Almost always. Two or three thorough case studies that show process and outcome usually serve better than many polished screens.
How do I show research skills if a dedicated researcher did the research?
Describe your part honestly: observing sessions, synthesising findings, running smaller tests yourself, or turning insights into design decisions.
Put it into practice
See how Luceria helps with thisDrafted with AI assistance and checked against Luceria’s editorial standards. Examples are illustrative, not real people’s results. Spotted something out of date? Tell us.