What should UX designer resume bullets prove?
UX designer resume bullets should prove that a design you made changed what users could do. Each line names the problem, the research or test behind your decision and what happened after release. Screens and tools describe the work. A finding, a decision and a measured change show the work mattered to users and to the business.
A portfolio holds the full case study. The resume bullet is the one-line version a reader sees first, and it should point toward a case you can walk through in the interview. Keep the same project names in both places so the reader can match them.
Which O*NET profile matches a UX designer?
O*NET OnLine has no profile titled UX designer. The nearest is web and digital interface designers (15-1255.00), whose sample of reported job titles includes UX Developer and UX Engineer. The tasks in that profile cover research, prototypes, testing, style guides and accessibility, which is most of a UX designer's working week.
The O*NET profile for web and digital interface designers (15-1255.00) sums up the job: "Design digital user interfaces or websites". One task names the research side directly: "Conduct user research to determine design requirements and analyze user feedback to improve design quality". Another covers the hand-off to engineering: "Collaborate with web development professionals, such as front-end or back-end developers, to complete the full scope of Web development projects".
The Bureau of Labor Statistics covers the same work on its page for web developers and digital designers. BLS says "Digital designers develop, create, and test website or interface layout, functions, and navigation for usability". Its duties list includes "Create prototypes and mockups of websites or applications".
Which UX design duties turn into strong bullets?
UX design duties turn into strong bullets when the line follows the work past the mockup. The table takes six O*NET tasks and pairs each with a weak bullet, a fixed bullet and the facts you replace. Every fixed bullet is a made-up example. The brackets mark facts from your own projects.
Read each row left to right. Keep a row only if the work was yours.
| O*NET task | Weak bullet | Fixed bullet (made up) | Facts you swap in |
|---|---|---|---|
| Conduct user research to determine design requirements | Did user research. | Interviewed [N] [user type] and ran [N] diary studies, turning the findings into [N] requirements for [feature]. | Method, sample size, what it fed |
| Create prototypes | Made prototypes in [tool]. | Built a clickable prototype of [flow] and tested it with [N] users before any code was written. | Flow, test count, timing |
| Identify problems uncovered by testing or customer feedback | Fixed usability issues. | Found [N] task failures in usability tests of [flow]; the redesign raised task completion from [X] to [Y] of [N] participants. | Issues found, completion before and after |
| Develop visual design concepts and modify them from stakeholder feedback | Created designs. | Took [N] concepts for [page] through [N] review rounds with [stakeholders] and shipped the one that met [goal]. | Concepts, reviewers, the goal |
| Develop and document style guidelines | Maintained the design system. | Documented [N] components in [design system], adopted by [N] product teams within [N] months. | Components, teams, adoption window |
| Incorporate technical considerations, including accessibility | Made designs accessible. | Audited [flow] against WCAG [version] level [AA] and fixed [N] issues before launch. | Standard, level, issues fixed |
What do example UX designer bullets look like?
Example UX designer bullets below are grouped by the part of the design process they prove. Every line is made up. Replace each bracket with a fact you can show in a case study, a research report or product analytics. If a researcher or product manager led a stage, say which part was yours.
Research and discovery
- Ran [N] contextual interviews with [user type] and mapped [N] pain points that set the [quarter] roadmap for [product].
- Combined [N] support tickets and [N] survey answers into [N] themes, presented to [team] with a recommendation for each.
Design and prototyping
- Redesigned the [checkout or sign-up] flow from [N] steps to [N], tested in [N] rounds before hand-off.
- Built page templates for [N] [page types], cutting design time per new page from [X] to [Y] days.
Testing and iteration
- Ran [N] moderated usability sessions on [feature] and fixed the [N] issues that blocked task completion.
- Ran an A/B test of [variant] against [control]; [metric] moved from [X] to [Y] over [N] weeks.
Working with engineering
- Wrote specs and annotated [N] screens for [N] engineers, cutting design questions during the build from [X] to [Y] a sprint.
- Reviewed [N] builds against the design before release and logged [N] fixes the team shipped.
Nielsen Norman Group explains why testing lines carry weight in its guide to usability testing. NN/g writes that "The only way to get UX design right is to test it". A bullet that names a test and its result shows that habit.
What should a UX designer cut from resume bullets?
A UX designer resume often spends bullets on tools and deliverables. Figma files, wireframes and personas are inputs, and a hiring manager assumes you made them. Cut or rewrite these lines first so the space goes to findings and results. Keep each deliverable only where it led to a decision someone acted on.
- "Created wireframes and high-fidelity mockups" with no project named.
- A list of design tools inside a bullet; put them in a skills section.
- Results that belong to the whole squad, unless you can say which part was your design.
- Words like "delightful" or "intuitive" with no test behind them.
How do you check a UX designer bullet before you send it?
A UX designer bullet is ready when the case study behind it shows the same numbers. Read each line and check that the research count, the test result and the release date match your files. Ask whether the product manager would describe your part the same way. Then check that the line answers something in the posting.
Accessibility lines need the same care. The W3C's WCAG 2 overview says "WCAG documents explain how to make web content more accessible to people with disabilities". Name the version and level you tested against only if you tested against it.
The resume bullet points guide covers the base formula, and the XYZ resume formula helps when a result needs a baseline. The free resume optimizer rewrites the lines that matter for a posting and keeps your facts. For the interview that follows, see UX designer interview questions.
Other pages in this set cover bullets for a product manager, whose work overlaps with yours on specs, a business analyst, a marketing manager, a customer success manager and a data engineer.