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.
What makes it work
The same bullets as people usually write them, and what changed.
Before
Responsible for designing user interfaces for web and mobile products.
After
Designed 40-plus screens for a web scheduling tool and its companion Android app across three breakpoints.
Replaces a duty statement with the count, surface and platform range a reviewer can picture.
Before
Created a design system that improved consistency across the product.
After
Built a 60-component Figma library with tokens for colour, type and spacing; new screens went from about three days to one.
Names the size of the system and the build-time change instead of asserting consistency.
Before
Worked closely with developers to hand off designs.
After
Wrote state and edge-case specs for each component, which cut design QA comments on release builds by roughly half.
Shows what handoff actually meant and the effect on the engineering loop.
Before
Helped improve the sign-up experience.
After
Redrew the three-step sign-up flow after five moderated tests; completion rose from 61% to 74% over two months.
Adds the method, the sample and a believable before-and-after figure.
Before
Made the product more accessible.
After
Audited 120 screens against WCAG 2.1 AA and closed 38 contrast and focus-state issues before the compliance review.
Turns a vague claim into an audit scope, a standard and a number of fixes.
Before
Participated in weekly design critiques and gave feedback to the team.
After
Ran weekly critique for four designers and kept a shared checklist that caught spacing drift before files reached engineering.
Moves from attending to owning, and ties the ritual to a concrete result.
Keywords a ui designer resume needs
| Keyword | Why it matters | Where to put it |
|---|---|---|
| Figma | It is the default working file format for almost every product team, and screeners check for it first. | skills list and at least one bullet showing what you built in it |
| design system | Mid-level UI roles are usually hired to maintain or extend a system, not to draw one-off screens. | summary and a bullet under your most recent role |
| component library | Shows you think in reusable parts and can keep a product visually consistent. | a bullet describing what you built and how many components |
| design tokens | Signals you can connect design decisions to code variables for colour, type and spacing. | skills list or a bullet about handoff |
| responsive design | Most products ship on several breakpoints and hiring managers want proof you spec all of them. | a bullet naming breakpoints or platforms |
| WCAG 2.1 AA | Accessibility compliance is now a procurement requirement in many companies. | skills list and a bullet with a concrete fix count |
| prototyping | Teams use clickable prototypes to settle arguments before engineering starts. | skills list and a bullet tied to a test or review |
| developer handoff | A UI designer who specs states and redlines well saves engineering days per feature. | a bullet under your most recent role |
| interaction design | Separates screen decoration from behaviour: states, transitions, error handling. | headline or summary |
| usability testing | Shows your visual choices are checked against real users rather than taste. | a bullet with participant count and what changed |
| visual hierarchy | The core craft skill a design lead will judge in your portfolio review. | summary or a bullet about a redesign |
| design QA | Checking built screens against the spec is a named duty in many UI job posts. | a bullet about release process |
| iOS and Android patterns | Native platform conventions matter if the role touches mobile apps. | skills list if the product has apps |
| cross-functional collaboration | Job posts name it because UI work dies when engineering and product are not in the room. | a bullet naming who you worked with and how often |
Common mistakes
- Leaving off a portfolio link, or linking a site that needs a password with no note about it.
- Listing every tool you have ever opened instead of the three or four you work in daily.
- Describing visual work in adjectives like clean and modern with no screens, flows or platforms counted.
- Claiming a design system without saying what you built in it, how many components, or who used it.
- Hiding the engineering relationship, so a reader cannot tell whether your designs ever shipped.
- Using UX research language for a role that is judged on craft, and never mentioning type, grid or states.
- Padding with a skills bar chart or star ratings that tell a hiring manager nothing.
- Writing the same opening word on six bullets, which makes the whole page read as one paragraph.
Questions people ask
- Do I need a portfolio if my resume is strong?
- Yes. For UI roles the portfolio is the main evidence and the resume is the index to it. Put the link in the header, make sure it loads without a password, and lead with two or three case studies that show final screens plus the system behind them.
- How many pages should a UI designer resume be?
- One page at five to nine years. Keep two or three roles, three to five bullets each, and let the portfolio carry project detail. A second page is only worth it if you have significant system ownership or lead work that will not fit.
- Should I list Sketch and Adobe XD if I now work in Figma?
- List them only if a job post asks or if a past role genuinely ran on them. A short, current tool list reads as confidence. A long list of legacy tools makes a reviewer wonder when you last shipped.
- What numbers can a UI designer actually claim?
- Screens and flows designed, components in a library, breakpoints or platforms supported, accessibility issues closed, usability test participants, and any conversion or task-completion change your team measured. Keep the figures modest and say who measured them. Never invent revenue impact for a screen redesign.
- How do I show design system work if I did not start the system?
- Say what you owned inside it: the components you added, the tokens you defined, the documentation you wrote, the teams you onboarded. Contributing to a mature system is often harder than starting one, and hiring managers know it.
- Is HTML and CSS knowledge worth listing?
- Yes, if you can read and inspect code rather than only write it. Say so plainly, for example that you review built screens in the browser and file precise fixes. Do not imply you can ship front-end code unless you can.
- How should I handle a jump from graphic design into UI?
- Keep the graphic design role but write its bullets in product terms: systems, templates, constraints, handoff. Then let the two most recent UI roles hold the screen counts and shipped features. The summary should state the UI focus in the first sentence.
- What do I write if my best work is under NDA?
- Describe the problem, your role, the scope and the outcome without naming the client or showing the screens. Many portfolios carry one password-protected case study with a note to request access. Recruiters see this often and it does not count against you.
More resume examples
Now do it with your own resume
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.
Start from this example