| 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 |
|---|