What this role’s resume is actually judged on — the language postings use, what a reviewer looks for in the first ten seconds, and the specific way UX Designer resumes go wrong.
A first pass takes seconds and is looking for three things. If they are not near the top, the rest of the page rarely gets read.
Most resumes fail one bullet at a time. The difference is almost always specificity — a number, a constraint, or a consequence.
Conducted user research and created wireframes for new features.
Rebuilt the appointment flow after testing showed six of eight users missed the timezone selector; support tickets about wrong-time bookings dropped by two thirds.
Terms that recur in real postings for this role. They belong in the bullet that proves them, not in a list at the bottom — our own checker weights requirement coverage at 40% and raw keyword matching at 20%, and most serious systems make a similar trade.
A keyword you cannot defend in an interview is worse than a missing one. How the format checks work.
Wireframes, personas, journey maps and flows are artefacts, not outcomes. A resume that lists what you produced rather than what changed reads as process for its own sake — name the behaviour that shifted.
Expect to defend interaction decisions against a plausible-sounding alternative the interviewer invents on the spot. Holding a position with user evidence, or updating cleanly, both score.
No portfolio link, or one behind a password with no note
Research that never changed anything
Listing technologies you have touched once
A resume that reads identically to a mid-level one
Abstraction with no anchor
Framework nouns instead of outcomes
Generic resume advice only goes so far — what matters is whether this resume covers this posting. Paste both and get requirement-by-requirement coverage, the keywords you are missing, and the format problems a parser will hit. The first check is free.