UI Designer Resume Examples & Writing Guide

This sample is for a UI designer with about nine years across a B2B software company, a fintech app and an agency. The name and employers are invented. Notice that the portfolio link sits in the contact line, not buried at the bottom, and every role has a shipped outcome attached.

Design hiring is unusual: the resume is the second thing read, not the first. A design manager or recruiter opens the portfolio, spends two minutes there, and only reads the resume if the work holds up. So the resume has one job, which is to answer the questions the portfolio does not.

• Does the portfolio work and is it yours? Three or four deep case studies beat twenty screenshots. Say clearly what you did versus what the team did.
• What shipped? A designer who has shipped to production reads differently from one with concept work only. Name the product, the platform and the scale (users, screens, releases).
• Design system depth. Component counts, tokens, variants, adoption across teams. This is the most requested UI skill in 2026 postings and the easiest to prove with a number.
• Do you work with engineers? Handoff quality, annotated specs, Storybook or component review, and whether you can read the front-end code. Managers are tired of files that cannot be built.
• Craft plus outcome. Conversion, drop-off, task success, support tickets, accessibility conformance. Two numbers on the resume is enough to show you think past the pixels.

“I open the portfolio first. If it holds up, I read the resume to find out what you actually owned and whether you have shipped with engineers. What I never want is a resume that lists twelve tools and does not tell me one thing you built.”

Three or four lines. Say what you design, at what scale, and one result. Do not open with "creative problem solver with a passion for design."

Design resumes fail in the same way: bullets that describe a process instead of an outcome. Here are the rewrites.

Ten to fourteen lines. Keep the tools honest and the craft skills specific. A wall of 30 logos reads as padding.

Tools you work in daily:

• Figma, and say what you can do in it: components, variants, auto layout, variables and tokens, branching
• Prototyping: Figma prototypes, ProtoPie or Framer if you use them, and what fidelity you build to
• Adobe Illustrator and Photoshop, plus After Effects if you do motion
• Handoff and documentation: Storybook, Zeroheight, Notion, annotated redlines
• Testing and research tools: Maze, UserTesting, Hotjar, Optimal Workshop
• Project tools: Jira, Linear, Asana, Slack async review

Craft and technical skills, which is where you separate yourself:

• Design systems: token architecture, component API thinking, versioning and deprecation
• Typography and type scales, color systems and contrast ratios
• Layout: grids, responsive and adaptive breakpoints, density modes
• Interaction and state design: empty, loading, error, disabled, focus, success
• Accessibility: WCAG 2.2 AA criteria, keyboard order, focus visibility, target sizes, screen reader labeling
• Platform conventions: iOS Human Interface Guidelines, Material Design, web patterns
• Data-heavy interfaces: tables, filters, charts, dashboards (say if this is your strength, it is in demand)
• Enough HTML, CSS and component-framework literacy to read the built version and spot the drift

The working skills managers ask about in interviews:

• Giving and taking critique without defending every pixel
• Writing: interface copy, spec notes, and a case study someone can follow
• Scoping under deadline: what ships this sprint versus what waits
• Working with product managers on requirements and with engineers on feasibility

For this job the portfolio is the application and the resume is the supporting document. Get them to point at each other.

1. 1Put the portfolio URL in the contact line, written out plainly (yourname.design), not hidden behind the word "Portfolio".
2. 2Keep three or four case studies. Each one needs the problem, your role, what you actually did, the constraints and what happened after launch.
3. 3Say what was yours. "Led interface design; research by a partner researcher, illustrations by a contractor" builds trust. Claiming a whole team's work is the fastest way to fail a portfolio review.
4. 4Mirror the resume numbers in the case study, with the measurement method. If the resume says conversion moved 3.7 points, the case study should say over what period and on how many users.
5. 5Show one design system artifact. Component structure, token naming, or a before-and-after of inconsistency cleaned up. Managers look for it specifically.
6. 6If your work is under NDA, show process artifacts and describe outcomes in ranges. Do not upload screens you are not allowed to publish.
7. 7Include one piece of unglamorous work: a settings page, a table, an error state. It proves you can do the job, not just the hero screen.

The market for junior interface designers is crowded, so the goal is to look like someone who has already worked on a real product with real constraints. Three good projects will do that; ten dribbble-style concept redesigns will not.

1. 1Put "UI Designer" (or the posting's title) under your name, with your portfolio URL in the contact line.
2. 2Replace the experience section with a Projects section, and treat each project like a job: what it was, your role, tools, constraints, and what changed.
3. 3Get at least one project with a real user or client: a small business, a nonprofit, a student organization, an open-source tool. Real constraints show in the work.
4. 4Include one design system exercise. Build a small token set and 15 to 20 components with variants and states. It maps directly onto what junior UI designers are hired to do.
5. 5Add a redesign only if you research it. "I redesigned an app I like" is common; "I interviewed 5 users of this app, found the top complaint and redesigned that one flow" is not.
6. 6List certificates honestly and briefly: the Google UX Design Certificate and the Interaction Design Foundation courses are common and fine, but they do not substitute for work.
7. 7One page, plain layout, PDF. Name it Firstname-Lastname-UI-Designer-Resume.pdf and check the file opens on a phone.

• One page up to about eight years, two pages beyond that. Recruiters spend most of their time in your portfolio, so a long resume is wasted effort.
• Order: name and contact line with portfolio URL, summary, skills and tools, experience, education, certifications. Some managers prefer selected projects above experience for juniors.
• Single column, real text, no photo, no icon grid, no skill percentage bars. Percentage bars are the most disliked convention in design resumes and they carry no information.
• Keep one accent color and one type family if you want it to look designed. Restraint reads as craft; a four-color layout does not.
• Send a PDF with selectable text and a plain file name. If a company asks for a link only, send the portfolio and keep the resume ready.
• Contract and freelance work counts. Group it as one entry, "Freelance UI Designer," with a client count and the two or three projects worth naming.
• If you have a gap, one plain line is enough. Design teams went through wide layoffs in 2023 and 2024 and nobody is surprised by it.

Posting words worth mirroring when they are true of you: UI design, user interface, product design, design system, component library, design tokens, Figma, prototyping, responsive design, mobile and web, accessibility, WCAG, usability testing, developer handoff, information architecture, interaction design, visual design, design critique, cross-functional, A/B test.