UX designer resume examples & writing guide for 2026

Audience size in the headline

Two hundred and ten thousand people on the portal. Design work is judged by what it touches, and a junior page that names the audience stops being read as a portfolio of exercises.

Drop-off with a before and after

Forty-one percent to twenty-four. A redesign claim means nothing without the number it moved, and this one can be checked by anyone with access to the analytics.

Sessions turned into a fix list

Thirty-four moderated sessions and a nineteen-item list the team actually shipped. Research that ends in a slide deck is a cost. Research that ends in shipped fixes is the job.

The form change, said plainly

One fourteen-field form split into three steps. Naming the intervention lets a hiring manager judge the craft, where redesigned the experience would tell them nothing at all.

Accessibility with an audit result

Twenty-two screens to WCAG 2.1 AA and no blocking issues left at handoff. Accessibility is now a legal baseline for a lot of buyers, and the audit outcome is the proof it was met.

The support job found the problem

Two thousand four hundred tickets and a tag scheme showing a third came from one screen. Support is where evidence lives, and using it is a better origin story than a bootcamp project.

Surfaces owned, business named

Checkout and search on a hundred and forty million dollar business. Naming the surfaces says what this designer is responsible for, and the revenue says how much rides on getting it right.

Two measures, opposite directions

Completion up, support contacts down. One of those could be a seasonal fluke. Both moving the right way across the same work is much harder to explain away.

Experiments behind the lift

Four experiments, and the revenue they were worth. Attributing a conversion change to a redesign is where most design resumes quietly overclaim, and naming the tests is what keeps it honest.

Interviews that explained a metric

Twenty-two interviews showing people could not find shipment status, then a thirty-eight percent drop in those contacts. Research and outcome in one line, in the order they happened.

A project stopped by research

Six weeks, forty-eight participants, and a personalization build that never happened. Stopping work saves more money than shipping it, and almost nobody puts it on a design resume.

Health years kept to two

The earlier portal keeps the drop-off number and the accessibility audit, and nothing else. Retail is where this reader is deciding, so retail is where the lines went.

Designers led and teams covered

Three designers across six service teams. Lead roles are bought on span and review load, and both are in the first line rather than implied by a job title.

A deadline met, not described

A hundred and forty screens to WCAG 2.1 AA before the date. Compliance programs are usually written as effort. Written as a count delivered ahead of a deadline, it becomes evidence.

Time on task across four services

Forty-four percent, measured with two hundred and sixty participants before and after. A measurement design that survives scrutiny is rarer on these resumes than the result it produced.

A repository other teams use

Three hundred and ten sessions, searched by four product teams before they scope. It is the difference between doing research and leaving research behind for people who were not there.

A redesign stopped at discovery

Twenty-six interviews finding the problem was policy rather than the screen. Saying so to a client and canceling the work is the most senior thing on the page.

Retail years, a single line

Seven years on checkout keep the business size and the completion number, and nothing else. Eleven years fit one page because the earlier work keeps two numbers and loses the description.