Creative and design · Mid level · UK and US conventions noted

UX designer: resume example, explained

This fictional example shows a UX designer with four years in a software company applying for a mid-level product designer role: research methods and participant numbers stated, usability-test results given as task-success changes, and design-system contributions and work with engineers described as evidence rather than adjectives. Each decision is explained, three weak bullets are rewritten from the facts behind them, and the editable download lets you replace every detail with your own. Nothing here describes a real person, product or employer.

Illustrative example. An illustrative, invented UX designer with four years at a fictional payroll-software company, applying for a mid-level product designer post at a fictional online pharmacy. Every employer, product, participant count and figure is fictional.

Editable version of this example (.docx)

Tomasz Adeyemi-Lund

UX Designer · Research, prototyping and usability testing

Manchester, UK (hybrid) · 07700 900 418 · tomasz.adeyemi-lund@example.com · Case studies: example.com/tomasz-adeyemi-lund

Profile

UX designer with four years on a payroll product used by small-business owners, in a squad of two designers, six engineers and a product manager. Runs discovery interviews and usability tests, prototypes in industry-standard design and prototyping tools and contributes documented components to the company design system. Three written case studies cover the pay-run redesign, the onboarding flow and an accessibility audit; seeking a mid-level product designer role with more ownership of research.

Experience

UX Designer — Fictional Ledgerline Software (payroll software for small businesses)

January 2023 – present · Squad of two designers, six engineers and a product manager; product used by around 9,000 small businesses.

Redesigned the monthly pay-run flow after 12 discovery interviews and two rounds of usability testing with 6 participants each showed owners could not find how to correct a payslip; task success for the correction task rose from 58% to 83% between the first and final rounds, and support tickets tagged 'payslip correction' fell by about a third in the quarter after release.
Plan and run usability tests roughly every six weeks, recruiting 5 to 6 participants a round from customers and writing a one-page findings summary that the squad reviews within a week of the sessions.
Contributed 9 components to the company design system, including form validation and date-picker patterns, each with usage guidance and accessibility notes agreed with the front-end lead.
Audited the onboarding flow against WCAG 2.2 AA criteria with two engineers, fixing focus order, error messaging and contrast across 14 screens, and added an accessibility checklist to the design review template.
Hand over through annotated prototypes and a weekly design-engineering review; fewer than one in ten tickets in the past year came back with a design question.

Junior UX Designer — Fictional Northgate Digital (web agency)

September 2021 – December 2022 · Twelve-person agency building websites for charities and local councils.

Produced user flows, wireframes and clickable prototypes for 7 client websites, running at least one round of usability testing with 5 participants on each before build.
Ran content-mapping workshops with client teams and turned the output into sitemaps and page templates the developers built from.

Education

BSc (Hons) Psychology, Fictional University, 2020
Postgraduate certificate in human-computer interaction, Fictional Institute, 2021
Course: Accessibility for designers (WCAG 2.2), 2024

Case studies

example.com/tomasz-adeyemi-lund: pay-run redesign, onboarding flow, accessibility audit. Each states the problem, my role, what the research showed, one rejected option and how the result was measured.

Skills

User research: discovery interviews, usability testing, survey design · Prototyping and interaction design (industry-standard design and prototyping tools) · Design systems and component documentation · Accessibility: WCAG 2.2 AA audits, inclusive patterns · Information architecture and user flows · Working with engineers: annotated handover, design review, QA of built screens

Why it is written this way

Research is shown with methods and numbers, not the word 'research'

A UX designer resume that says 'conducted user research' leaves the reader guessing whether that meant one survey or a programme of interviews. Here each research claim carries the method and the count (12 discovery interviews, two rounds with 6 participants each), which is modest and plausible for a squad-level designer and tells an interviewer exactly what to probe.

Usability results are given as task success, the measure UX teams use

The pay-run bullet reports the change in task success between the first and final test rounds and the support-ticket change after release. Both are figures a UX designer genuinely has access to, unlike revenue, and they show the designer checked whether the design worked instead of stopping at handover.

Design-system and engineering collaboration get their own bullets

Mid-level product designer adverts almost always ask for design-system experience and comfort working with engineers. The resume states the number of components contributed, what the documentation covered and how handover works week to week, so 'collaborative' is never claimed; it is shown, with a measure (how few tickets come back with design questions) that an engineering lead would recognise.

Case studies are named on the resume, with a sentence on what each contains

The reader should know before clicking that there are three written case studies and that each states the problem, the role, the research, a rejected option and the measurement. That sentence does more than a bare link, and it signals that the designer understands what a UX case study is for. Screens stay in the portfolio; the resume carries the reasoning.

Bullet rewrites, and the evidence behind them

Each rewrite was produced by asking an evidence question and using only the (fictional) answer. No number appears in a rewrite that is not in its evidence.

Before
Conducted user research and designed new features.
Evidence question
Which feature, which methods, how many people, and what did the research change?
Evidence (fictional)
The pay-run flow; 12 discovery interviews; two rounds of usability testing with 6 participants each; owners could not find how to correct a payslip; the redesign moved the correction into the pay-run summary.
After
Redesigned the monthly pay-run flow after 12 discovery interviews and two rounds of usability testing with 6 participants each showed owners could not find how to correct a payslip.
Before
Improved the user experience, leading to better results.
Evidence question
What was measured, before and after, and over what period?
Evidence (fictional)
Task success for the payslip-correction task was 58% in the first round and 83% in the final round; support tickets tagged 'payslip correction' fell by about a third in the quarter after release.
After
Raised task success for the payslip-correction task from 58% to 83% between the first and final test rounds; related support tickets fell by about a third in the quarter after release.
Before
Worked closely with developers.
Evidence question
What does the collaboration look like in practice, and is there a measure of how well it works?
Evidence (fictional)
Annotated prototypes; a weekly design-engineering review; 9 components contributed to the design system with usage and accessibility notes agreed with the front-end lead; fewer than one in ten tickets came back with a design question in the past year.
After
Hand over through annotated prototypes and a weekly design-engineering review, and contributed 9 design-system components with usage and accessibility notes agreed with the front-end lead; fewer than one in ten tickets in the past year came back with a design question.

Try it on your own bullets with the bullet workbench, which asks the same questions and never adds a figure you did not supply.

Transferable skills in this example

Structured interviewing and synthesis
Evidence: 12 discovery interviews turned into a one-page findings summary the squad acted on within a week.
Where it helps: User research, service design, product management and any role that gathers requirements from people.
Testing an idea before committing to it
Evidence: Usability rounds every six weeks with 5 to 6 participants, with the design changed between rounds.
Where it helps: Product, marketing experimentation, content design and operations-improvement roles.
Documenting reusable patterns
Evidence: Nine design-system components with usage guidance and accessibility notes.
Where it helps: Technical writing, design operations, front-end roles and any team building shared standards.
Accessibility auditing
Evidence: WCAG 2.2 AA audit across 14 screens with engineers, and a checklist added to design review.
Where it helps: Digital accessibility, QA, public-sector digital teams and content roles.

Occupation notes

Hard requirements

A portfolio of case studies is the de facto hard requirement for UX designer roles: adverts say 'portfolio required' and hiring teams commonly review it before the resume. Link to it in the header and name the case studies so the reader knows what to expect.
UX design is not a licensed or registered occupation; the hard requirements come from the advert: named methods such as usability testing, design-system experience and sometimes a sector (regulated finance or health products) or a research specialism. Show each in the work, not only in the skills list.
Right to work in the country of hire is checked through the verified employer process at the stage required in that country and is not resume content; answer any sponsorship question on the application form.

Vocabulary that belongs on the page

Discovery research, user interviews, contextual inquiry
Usability testing, task success, think-aloud sessions, findings synthesis
User flows, wireframes, information architecture
Prototyping (low and high fidelity), clickable prototype, interaction design
Design system, component library, design tokens, usage guidance
Handover (handoff), annotated designs, design-engineering review, design QA
Accessibility: WCAG, success criteria, focus order, contrast, screen-reader testing

Pitfalls specific to this occupation

A resume built as a designed artefact: two columns, icon-only contact details, skill bars for tools and text inside exported images. Applicant tracking systems often read columns out of order and cannot see text in images, so job titles or the case-study link can vanish; check the plain-text reading with /tools/parser-preview and keep the visual craft for the case studies.
Claiming outcomes the designer cannot have measured ('increased revenue by 40%') while leaving out the measures UX teams do own, such as task success, error rates and time on task.
Listing design tools as the lead skill. Tools change and most applicants use the same ones; the method and the decision are what a UX designer is hired for.
Describing team outcomes as solo work. Say 'with two engineers' or 'in a squad of nine' so the portfolio, the resume and the interview answers agree.

UK and US differences

UK: 'UX designer', 'product designer' and 'interaction designer' are used for overlapping roles by UK employers; mirror the advert's title in the headline where the work genuinely matches.

US: US product teams frequently title the role 'product designer' and expect a one-page resume; the case-study link carries the depth. Use US spelling (color, organize) in a US application.

Common questions

How do I show usability-testing results on a UX designer resume?

Give the measure UX teams use: task success, error rate or time on task, before and after, with the number of participants and rounds. Modest, honest figures from six-person rounds are more credible than large percentages with no method behind them.

What if my UX work is confidential and I cannot show screens?

Describe the problem, method and outcome without the screens, recreate a simplified flow with invented content, or offer to walk through the work in interview by permission. Say plainly on the resume that a case study is anonymised.

Published 6 November 2026 · Every person, employer and figure in this example is fictional. Drafted with AI assistance and checked against Luceria’s editorial standards.