Reviewed:
UI Designer resume example
A UI designer is hired to make screens that people can use without thinking about them. That means type scales, spacing, colour and states that hold up across a whole product, not one pretty mockup. Most teams also expect you to own or contribute to a component library and hand work to engineers in a form they can build from.
A hiring manager reads a UI resume next to a portfolio, so the resume has a different job: it shows scope, pace and the kind of product you have shipped. Say how many screens or flows, which platforms, how many engineers you worked beside, and what changed after release. Sign-up completion, support tickets, time to build a new screen, accessibility issues closed: these are the numbers UI work actually moves.
Name your tools plainly, including Figma and whatever handoff, prototyping and design-token setup you use. Show that you work in a system, that you can spec states and edge cases, and that you can take feedback from engineering and research without the work stalling. Put a portfolio link at the top; a UI resume without one gets skipped.
The example
Jordan Avery is a placeholder, and every employer on this page is fictional. The numbers are illustrative.