Keywords for a UX Designer resume
A UX designer is hired to reduce the cost of confusion. Someone inside the company has a product that people abandon, a signup flow that leaks, or a tool that support staff hate, and they want a person who can find out why and change it. So a screener reading your resume is looking for two things at once: evidence you talk to users and evidence you ship screens that engineers can build. A portfolio of pretty mockups with no research and no shipped outcome reads as junior, no matter how many years you have.
Most UX roles are filtered in two passes. First an applicant tracking system or a recruiter scans for the vocabulary of the craft: usability testing, wireframes, prototypes, design systems, Figma, accessibility, journey mapping. If those words are missing, the resume stops there, even if the work behind it was strong. The second pass is a hiring manager, usually a design lead or a product director, who reads your bullets to work out what you actually decided and what happened after. They also open your portfolio link within seconds, so the link belongs in the header, live, and not behind a password you forgot to mention.
Place terms where they can be believed. Tools belong in a short skills block. Methods belong inside bullets, attached to a product and a result, because 'ran moderated usability tests with 12 participants' carries weight that a bare skills-list entry never will. Name the platform you designed for, the kind of user you designed for, and how you worked with engineering. Specialist titles matter too: if the posting says product designer, UX researcher, or design systems designer, mirror that language in your headline rather than making the recruiter translate.
Weak bullets, rewritten
Keywords only count when they sit inside a bullet that says what you did. The same ux designer bullets, before and after.
Before
Responsible for designing user interfaces for web and mobile applications.
After
Designed the mobile web checkout for a grocery ordering app, cutting abandoned carts from 38% to 29% over two quarters.
The duty statement names no product and no outcome. The rewrite picks one flow and gives a before and after number.
Before
Conducted user research to inform design decisions.
After
Ran 14 moderated usability sessions on the claims form and rewrote three error messages that had caused most drop-offs.
Method, volume and the specific change are all missing in the first version. The second shows what the research actually bought.
Before
Created and maintained the company design system.
After
Built 30 Figma components with design tokens for colour and spacing, which let two squads ship new screens without new design files.
Adds the substance of the system and the reason anyone funded it, rather than claiming ownership alone.
Before
Worked closely with product managers and engineers in an agile environment.
After
Paired with two front-end engineers during sprint planning to split a large settings redesign into four releases, none of which slipped.
Collaboration becomes visible when you say who, on what, and what it prevented.
Before
Improved accessibility across the product.
After
Audited 22 screens against WCAG 2.1 AA, fixed contrast and focus order, and cleared 41 of 47 logged issues before release.
Names the standard and the volume of work, which is what an accessibility-conscious employer checks for.
Before
Presented designs to stakeholders and gathered feedback.
After
Facilitated a two-hour prioritisation workshop with support, sales and engineering that settled the roadmap for the reporting rebuild.
Replaces a passive meeting with a decision you helped produce.
The 36 keywords
| Keyword | Why it matters | Where to put it |
|---|---|---|
| user research | The single term most UX postings share. Without it your resume reads as visual design only. | Summary and at least two bullets naming the method and the number of participants |
| usability testing | Hiring managers want proof you have watched real people struggle with your work and changed it. | A bullet under your most recent role, with sample size and what you changed |
| wireframes | Signals you work at low fidelity before committing, which is what product teams need early. | Skills list and a bullet about an early concept phase |
| prototyping | Interactive prototypes are how designs get tested and approved. Named on nearly every posting. | Skills list plus a bullet where a prototype settled a decision |
| Figma | The default tool in most design teams. Its absence raises questions about how current you are. | Tools group at the top of the skills block |
| design system | Companies past a certain size hire for consistency and reuse, not one-off screens. | Skills list and a bullet on components you built or maintained |
| interaction design | Distinguishes you from a static-visual designer and covers states, transitions and error handling. | Summary and a bullet on a complex flow |
| information architecture | Comes up for content-heavy products, dashboards and navigation rework. | A bullet about restructuring navigation or taxonomy |
| WCAG 2.1 AA | Accessibility is a legal requirement for many employers, especially public sector and finance. | Skills list and a bullet about an audit or remediation |
| accessibility | The plain-language version recruiters search for alongside the standard. | Summary or skills list |
| journey mapping | Shows you can zoom out past one screen to the whole experience, including offline steps. | A bullet under a role where you worked across teams |
| user flows | The everyday deliverable that proves you think in decisions and paths, not pages. | Skills list and a bullet on a flow you simplified |
| personas | Common in postings even where the practice is debated. Screeners look for the word. | A research bullet, tied to how the personas were used |
| A/B testing | Indicates you can defend a design with data, which product and growth teams expect. | A bullet with the metric that moved |
| design critique | Teams want someone who can give and take feedback in the open. | A bullet about team rituals or mentoring |
| stakeholder interviews | Much UX work starts with internal constraints. This shows you gather them deliberately. | A bullet in a role with many business partners |
| heuristic evaluation | A cheap, fast method hiring managers like because it fits short timelines. | A bullet where you assessed an existing product |
| design tokens | Signals real design system work rather than a shared component file. | Skills list, next to design system |
| responsive design | Most products run on phone and desktop. Recruiters check you have handled both. | Skills list or a bullet naming breakpoints or mobile web |
| mobile app design | Filters for iOS and Android experience, which is a separate craft from web. | Summary if it is your focus, otherwise a bullet |
| design handoff | Engineers are the internal customer. Clean handoff is a top complaint when it is missing. | A bullet about working with developers |
| cross-functional collaboration | Named in almost every posting, usually meaning product managers and engineers. | Summary, then shown in a bullet rather than repeated |
| agile | Tells the reader you can work in sprints and split design across iterations. | Skills list or a bullet on sprint cadence |
| Jira | Where design work is tracked at most companies. Cheap to include, often searched. | Tools group |
| user interviews | Distinct from usability testing and specifically listed on research-heavy roles. | A bullet with the number of interviews and what you learned |
| survey design | Shows you can gather evidence at scale when interviews are not enough. | A research bullet |
| analytics | Designers who read behavioural data get trusted with bigger problems. | Skills list, with the platform named if you used one |
| conversion rate | The outcome commercial teams care about most. Gives your bullets a business edge. | A bullet result on a signup, checkout or lead flow |
| task success rate | The standard usability metric. Proof you measure your own work. | A testing bullet, before and after |
| service design | Appears in government, health and enterprise postings where the experience spans channels. | Summary if relevant, or a journey bullet |
| content design | Microcopy often fixes what layout cannot. Some teams hire for the overlap. | A bullet about error messages, labels or empty states |
| design ops | Signals you have improved how the design team itself works. | A bullet about file structure, libraries or onboarding |
| HTML and CSS | Not required everywhere, but it reassures engineering-heavy teams about feasibility. | Skills list, stated at your honest level |
| portfolio | No UX resume is read without one. The link is the most clicked item on the page. | Header, next to email and location |
| mentoring | Mid-level and senior roles expect you to raise other designers. | A bullet naming how many designers and what they got better at |
| workshop facilitation | Shows you can run a room of stakeholders and get a decision out of it. | A bullet with the workshop type and outcome |
Common mistakes
- Leaving the portfolio link out of the header, or linking to a case study that opens with mockups and never explains the problem.
- Listing 20 tools and no methods, which makes you look like a screen producer rather than a designer.
- Describing visual polish only, with no mention of research, testing or accessibility.
- Writing bullets that stop at the deliverable, so the reader never learns whether the design shipped or worked.
- Using team results as your own without saying what you personally decided or designed.
- Padding with process nouns like discovery, ideation and iteration while naming no actual study, flow or metric.
- Hiding the platform and domain, so a healthcare or enterprise hiring manager cannot tell if your experience transfers.
- Claiming senior design system ownership when the evidence is one shared component library.
Questions people ask
- How many UX keywords should I put on the resume before it looks stuffed?
- Aim for the terms that appear in the posting and that you can back up, usually 15 to 20 across the whole page. Tools can sit in a list because nobody expects a story for each one. Methods should appear inside bullets with a product and an outcome attached, and any method you cannot describe in an interview should come off.
- Do UX resumes still get read by applicant tracking systems?
- Yes, at larger companies. The system does not judge your taste, it just checks whether your words overlap the requisition, so mirror the job title and the named methods in your summary and skills block. Keep the layout single-column with real text, not a two-column PDF where the parser mixes your columns together.
- Should I say product designer or UX designer?
- Use whichever title the posting uses, in your headline. The two overlap heavily in practice, with product designer usually implying more ownership of scope and metrics. If your last title was different from both, put the official title on the role line and the posting's language in your headline.
- How do I show research experience when my company never let me talk to users?
- Name the evidence you did have. Support ticket analysis, session recordings, analytics funnels, heuristic evaluations and interviews with internal experts are all legitimate, and saying so is better than inventing a study. Then add one bullet about a small guerrilla test you ran, even with five participants, because it shows you push for contact with users.
- What numbers can a UX designer honestly put on a resume?
- Task success rate, time on task, drop-off or abandonment rate, conversion on a specific flow, support ticket volume for a feature, and number of participants or screens. Keep the movement modest and attach it to one flow rather than the whole product. If the data was never measured, use scale instead: screens shipped, components built, teams served.
- Where do accessibility keywords belong?
- Put WCAG 2.1 AA in your skills block and accessibility in your summary if it is part of how you work. Then back it with one bullet that names what you audited and what you fixed, such as contrast, focus order, labels or keyboard navigation. Public sector, health and finance employers often treat this as a hard requirement.
- Do I need HTML and CSS on a UX resume?
- Not usually required, but it helps with engineering-heavy teams and reassures them your designs are buildable. List it at your honest level, for example reading and editing HTML and CSS rather than front-end development. Never list a framework you have only watched a tutorial about.
- How long should a mid-level UX designer resume be?
- One page is fine up to about eight years, two pages once you have several substantial roles and a design system or research programme to describe. Cut internships and unrelated retail jobs first. The portfolio carries the depth, so the resume only has to make a reader want to click it.
Keywords for related jobs
Get these keywords into your resume without stuffing
Paste a job description and your resume. It rewrites your own lines for the job, never invents a fact, and asks you when something is missing.
Tailor my resume