What if I don't have access to post-launch metrics?

More metrics exist than most UX designers realise. Check with your PM or data analyst — activation rates, feature adoption, and support ticket volumes are usually tracked even if designers aren't shown them routinely. If you ran usability testing, your task success rates and time-on-task are metrics. SUS scores take 10 minutes to collect. If genuinely nothing is available, focus on scope (how many users, sessions, screens, or stakeholders) and process specificity — these still outperform deliverable-only bullets.

How should I write bullets for agency or contract work?

The same structure applies — context, action, outcome — but you may need to anonymise the client. 'Led UX for a Series B fintech (undisclosed client, NDA) — redesigning the loan application flow and improving completion rates by 34%' is perfectly acceptable. The industry, scale, and outcome still carry weight even without the company name. If the client is publicly known and you have permission to name them, do so — it adds credibility.

How many bullet points should I include per UX role?

Three to five bullets per role is the target. Your most recent role can run to six if your scope was broad. Prioritise: research-led outcomes first, shipped product outcomes second, design system or collaboration evidence third. Earlier roles from more than five years ago should have two to three bullets at most, focused on the most impressive and relevant outcomes. Volume doesn't compensate for quality — five strong bullets beat eight weak ones every time.

Should I include bullets about process (e.g. running design critiques) or only outcomes?

Process bullets are valid if they show systemic thinking rather than individual task execution. 'Facilitated weekly design critiques' is weak. 'Established a weekly design critique structure for a 5-person team that reduced revision cycles by 2 per sprint' is strong — the same process, reframed around outcome. Ask yourself: what changed because this process existed? If you can answer that question, the bullet works.

UX Designer Resume Bullet Examples

The most common problem on UX designer CVs isn't weak design — it's weak documentation of strong design. Deliverable lists ("designed wireframes, prototypes, and user flows") describe what you produced, not what changed as a result. Recruiters and hiring managers want to see the problem, the process, and the outcome — in that order. These 12 bullet examples cover four areas of UX work, using the metrics that actually matter in this discipline: task success rates, conversion improvements, adoption figures, usability scores, and time-on-task reductions.

The UX Bullet Formula

Every high-scoring UX bullet follows the same structure, even when it doesn't look formulaic. The components are:

Problem or context. What situation did you start from? A low task completion rate, an undefined design system, a research gap, a product area nobody had redesigned in four years. This is the "why it mattered."
Your action and method. What did you do, and how? Not just "designed a solution" — which research methods, which design approaches, which collaboration model. This is the "how you solved it."
Outcome with a metric. What changed after you shipped? Task success rate, conversion, adoption, satisfaction, SUS score, error rate, time-on-task, NPS — any specific measure that shows the work made a difference. This is the "why it was worth reading."

Not every bullet needs all three components. A bullet with context + action scores significantly higher than one with action alone. Adding an outcome elevates it further. Aim for all three in your most recent two roles.

12 UX Designer Resume Bullet Examples

User Research

Planned and ran 22 moderated usability sessions across two rounds of testing for a prescription management feature, identifying 7 critical failure points in the original prototype; the redesign achieved a 91% task success rate post-launch, up from 54% in baseline testing

Task success rate: 54% → 91%Research scope, two-round rigour, failure-point count, and before/after measurement all present — extremely rare combination on a UX CV.

Led a generative research programme with 16 small business owners across three countries, combining diary studies and contextual interviews, to identify unmet needs in financial reporting tools; findings directly reshaped the Q3 roadmap and eliminated two features from development

Roadmap impact (features cut)Multi-method research, international scope, and upstream product influence (features removed, not just features improved) — signals research maturity.

Introduced unmoderated remote testing via Maze into the team's design process, running fortnightly usability checks across new feature releases; average time from design to validated prototype dropped from 3 weeks to 5 days

Validation cycle: 3 weeks → 5 daysProcess improvement framed as impact, not just tool adoption. The 'fortnightly' cadence signals systemic thinking, not a one-off effort.

Product Design

Redesigned the B2B SaaS onboarding flow across web and mobile, reducing time-to-first-value from 9 days to 2 days through progressive disclosure and contextual in-app guidance — validated across 4 rounds of moderated testing and a 5-week A/B experiment with 3,200 participants

Time-to-first-value: 9 days → 2 daysScope (web + mobile), mechanism (progressive disclosure), validation rigour (4 rounds + A/B with participant count) — covers every hiring manager question in one bullet.

Owned the information architecture overhaul for a 300-screen enterprise platform, conducting card sorting with 48 participants and tree testing with 120; the new navigation structure reduced time-on-task for the five most common workflows by an average of 38%

Time-on-task: −38% across 5 workflowsIA scope (300 screens), named methods, participant counts for both, and a meaningful outcome that directly connects research to result.

Led UX for a patient-facing appointment scheduling feature used by 400,000 NHS patients monthly, achieving a System Usability Scale score of 84 (above the industry benchmark of 68) and reducing scheduling support calls by 29% in the 60 days following launch

SUS: 84 vs 68 benchmark; support calls −29%Scale (400K users), a named benchmark comparison for SUS, and a downstream operational metric (support calls) that proves usability beyond the lab.

Design Systems

Built and maintained the core component library for a fintech design system from scratch, covering 72 components with accessibility annotations, Figma variables, and Storybook integration — adopted by 18 designers and 35 engineers across 5 product squads within 3 months of launch

Adoption: 18 designers, 35 engineers in 3 monthsScope (72 components), named outputs (Figma variables, Storybook), and adoption data with a timeframe — the three things design system interviewers always ask about.

Audited and consolidated a legacy design system of 240+ inconsistent components into a governed token-based library of 80 canonical components, reducing design-to-development handoff friction and cutting average implementation time per component by approximately 40%

Handoff time: −40%; components: 240+ → 80Before/after component count shows decisiveness (removing complexity is harder than adding), and the approximate qualifier on handoff time is honest and credible.

Created the design system accessibility documentation framework adopted across the organisation, covering colour contrast ratios, focus state specifications, ARIA guidance, and screen reader testing protocols for 60+ components; all new feature releases now pass accessibility QA before handoff

100% of releases pass accessibility QASystemic output (a framework, not just compliant screens), named accessibility dimensions, and a policy-level outcome that extends beyond the immediate project.

Collaboration

Partnered with engineering, product, and content design to ship an end-to-end accessibility overhaul across 14 core product surfaces, achieving WCAG 2.1 AA compliance; jointly developed a screen reader testing protocol with QA that is now embedded in the standard release process

WCAG 2.1 AA across 14 surfacesThree-team collaboration named, scope of work (14 surfaces), compliance milestone, and a durable process output — all in one bullet.

Embedded within a cross-functional squad of 9 (PM, 3 engineers, data analyst, content designer) to redesign the subscription upgrade flow; facilitated 6 design critique sessions and 2 assumption-mapping workshops, and the shipped design improved upgrade conversion by 23%

Upgrade conversion: +23%Team composition, facilitation evidence (not just attending), and a commercial outcome — signals that the collaboration produced something, not just meetings.

Co-ran a 3-day design sprint with a client team of 12 stakeholders across product, marketing, legal, and operations to validate two competing product directions; the sprint output replaced a planned 6-week discovery phase and accelerated the roadmap by one quarter

6-week discovery phase replaced; roadmap +1 quarterStakeholder breadth (4 named functions), decision quality (two competing directions tested), and a business-level outcome (time saved) rather than just a design artefact.

Common UX Bullet Mistakes (and the Fix)

The patterns below appear on the majority of UX CVs and consistently lower scores — both with human reviewers and ATS systems. Recognising them in your own document is the fastest route to improvement.

"Designed wireframes, prototypes, and user flows for the checkout experience"

Name the problem and outcome: 'Redesigned the checkout flow after research identified 3 primary drop-off points, reducing cart abandonment by 19% in post-launch analytics'

"Conducted user research to inform the design"

Name the method, participant count, and what the research changed: 'Ran 12 user interviews and 2 rounds of usability testing; findings led to removing a feature entirely and adding a new information hierarchy'

"Collaborated with stakeholders to deliver the project on time"

Name the stakeholders and what the collaboration produced: 'Partnered with the PM and three engineers to define acceptance criteria for the accessibility overhaul, reducing post-launch defects by 60%'

"Used Figma to create high-fidelity designs"

Frame around output, not the tool: 'Built a Figma component library adopted by a 6-person design team, cutting new screen production time by approximately 35%'

"Improved the user experience of the onboarding flow"

Quantify the improvement: 'Redesigned the onboarding flow, improving 7-day activation from 31% to 54% and reducing time-to-first-action from 4 minutes to under 90 seconds'

Which Metrics to Use on a UX CV

UX designers often believe they don't have access to metrics — but most roles produce more measurable outcomes than candidates realise. Here are the metrics that land well on UX CVs, and where to find them:

Task success rate. The percentage of users who complete a defined task without assistance. Available from usability testing (even with 5–8 participants), analytics tools, or post-launch instrumentation. The most credible UX metric because it directly reflects design quality.
Time-on-task. How long it takes users to complete a workflow. Before/after comparisons (especially across two rounds of usability testing) are compelling evidence of meaningful improvement.
SUS score. System Usability Scale is a standardised 10-question survey that produces a 0–100 score. The average score across all products is around 68. Scoring above 80 is considered excellent. If you've run a SUS study, include the score and compare it to the benchmark.
Conversion and activation. Checkout conversion, trial-to-paid conversion, feature adoption, 7-day or 30-day activation rates. These are often tracked by the data team and accessible via analytics dashboards — ask your PM or data analyst if you're not sure whether they exist.
Error rate and support volume. The percentage of users making errors in a flow, or the volume of support contacts attributed to a specific UI problem. Post-launch reductions in support tickets or error rates are legitimate design outcomes.
Adoption. How many users, designers, or engineers adopted a design system, component library, or pattern within a given timeframe. Especially relevant for design systems work where traditional usability metrics don't apply.

See How Your UX Bullets Score

Upload your CV and get instant feedback on impact framing, research evidence, and keyword coverage — with specific rewrites ranked by priority.

Run My CV Score

Free · No signup · 30 seconds

Plus: see how automation could impact your role

Frequently Asked Questions

UX Designer Resume Checklist

15-item checklist covering portfolio visibility, research evidence, outcome metrics, and ATS formatting.

UX Designer Resume Summary Examples

Four annotated summary examples for Product UX, UX Research, Design Systems, and Generalist designers.

Resume Score Checker

Get an instant score across your CV's formatting, keywords, and impact — with UX-relevant fixes ranked by priority.

Resume Bullet Examples

The formula for high-scoring bullets with before/after rewrites across all functions.

More Role Guides

Product Manager Resume Checklist

15-item PM CV checklist covering ownership language, metrics, cross-functional breadth, and keyword coverage.

Marketing Manager Resume Checklist

Marketing CV checklist covering channel ownership, budget scale, ROAS, CAC, and performance metrics.

HR Manager Resume Checklist

HR CV checklist covering people metrics, policy scope, employment law knowledge, and stakeholder evidence.