Resume example

UI/UX Designer resume example

A complete, ATS-parseable ui/ux designer resume — then a breakdown of why it is written this way, so you can apply the reasoning to your own instead of copying the words. Build yours in Resume Studio.

📄 Build my ui/ux designer resume free →

Why this works

• ✓Your portfolio IS the resume — link it at the top and lead with outcomes.
• ✓Show process, not just pretty screens: problem → research → decision → result.
• ✓Quantify impact where you can (conversion, tickets, task success).
• ✓Name Figma and design-systems work explicitly.

The strongest bullet here, taken apart

The first line of the experience section reads:

Led a 4-month checkout redesign; conversion 5.8% → 7.2%, support tickets -22%, and mobile conversion -8% gap eliminated

Three things are doing the work. It opens with the outcome rather than the activity, so the first few words already contain the point — a recruiter scanning quickly reads the start of each line and little else. It carries a number, which converts a claim into evidence and is the difference between "improved performance" and something a hiring manager can picture. And it names the mechanism, so the reader can tell you understood why it worked rather than having been nearby when it did.

The usual failure is the mirror image: opening with "Responsible for" or "Worked on", describing the remit instead of the result, and leaving the outcome unmeasured at the end of the sentence — or absent. That version describes a job description. This one describes what changed because you were there. When you rewrite your own, start each line with the outcome and work backwards to the method; if a bullet has no number in it after that, it is usually a task rather than an achievement.

What a ui/ux designer is screened on

Design interviews center on your portfolio, your process, and a whiteboard/app-critique exercise. Expect to walk through one case study end-to-end.

The ui/ux designer template, to copy

Plain text on purpose. Columns, tables and text boxes are what break parsing, so this is the shape that survives being pasted into a document and read by an ATS. Section order below is the one that works for this role specifically — a ui/ux designer does not lead with the same section a project manager does.

Order: Contact → Portfolio link → Experience → Skills → Education

YOUR NAME
City · email · phone · linkedin.com/in/you · github.com/you

SKILLS
Figma · Interaction design · User research · Design systems · Prototyping · Usability testing

EXPERIENCE
Job Title — Company                                   City · 20XX–present
  • The user problem + what you designed + the measured change in behaviour
  • [Same shape. A number in at least three of your bullets.]
  • [Scope: how many users, how much money, how big the team.]

SKILLS
Figma · Interaction design · User research · Design systems · Prototyping · Usability testing

EDUCATION
Degree, Institution — 20XX

The bullet formula for this role

The user problem + what you designed + the measured change in behaviour.

The numbers a ui/ux designer is measured on

Recruiters for this role look for these specifically. A resume with three of them beats one with none, however well written.

• ›task success rate
• ›time on task
• ›conversion or drop-off %
• ›support tickets removed
• ›design-system adoption across teams

What to cut

Most weak resumes fail by including things, not by leaving them out.

• ›A long tool list — Figma is assumed
• ›"Passionate about user-centred design"
• ›Dribbble shots with no problem statement

Score this against a real ui/ux designer posting → · Live ui/ux designer openings

Tailoring this to a specific posting

Do not rewrite it per application — reorder it. Move the experience closest to the posting to the top of its section, make sure the exact phrasing the posting uses appears somewhere it is true, and check the knockouts before anything else. Years of experience, degree, work authorisation and location end more applications than weak bullets ever do. Run the posting and your resume through TrueFit to see the real overlap and the knockouts before spending an hour on wording.

Not in this role yet?

This resume assumes the experience already exists. If you are still moving into the role, how to become a ui/ux designer covers the realistic routes in, what to learn in what order, what it pays measured from live postings, and the one piece of work that changes the conversation.

Then prepare for the interview it gets you

Everything here is something you can be asked to defend, and the bullets with numbers attract the most follow-up — that is what they are for, and it is also the risk. Before you send it, make sure you can explain how each number was measured. The questions ui/ux designers actually get are on the ui/ux designer interview questions page.

Your portfolio is the resume; everything else is context

Unlike most professions, design hiring is portfolio-first. Hiring managers will spend more time looking at your case studies and visual work than reading your resume bullets. This means the most important thing on your resume is a clean, direct link to your portfolio—preferably public and requiring no password. If a recruiter has to ask for access or wait for you to grant permission, half of them won't bother. Your resume bullets should then point to specific work in the portfolio and explain the process, not the pixels. "Led checkout redesign" is a headline; the portfolio is where you show the before-and-after, the research you did, the iterations, and the metric that moved.

The weakest portfolio signal is beautiful work with no context. "Built a fintech mobile app" with only the final screens says nothing about whether you designed it end-to-end, how long it took, or whether it actually solved a user problem. The strongest portfolio cases tell a story: problem, research, decision-making, execution, outcome. Why was checkout broken? What data or user interviews told you so? How many variations did you test? Which won? What happened after launch? A case study that answers these questions is far more credible than five polished mockups.

On your resume, your portfolio link should be at the top, styled as clearly as your name. Keep it simple: "Portfolio: [domain].com" or "Work: [domain].com." Then use your resume bullets to direct readers to the right case studies. "Led checkout redesign (case study in portfolio) that lifted conversion 18% and reduced support tickets 22%" tells a reviewer exactly where to look and what to look for. The portfolio is the evidence; the resume is the map.

Design systems as proof of scale and process maturity

Designers who build and maintain design systems are credible signals for seniority and organization. A design system means you didn't just design screens; you codified a set of decisions that other people can use repeatedly. The strongest resume bullet on this topic names the scope: "Built and maintained the design system adopted across 6 squads (40 engineers); 85% of new features shipped using system components, reducing design review cycles by 30%." This shows the system is real, it's used, and it has measurable impact. It proves you can think in abstractions and systems, not just individual screens.

Many designers list design systems work without showing it's actually used. "Created a comprehensive design system" might mean you built a Figma library that no one looks at. Better: "Designed and shipped 20 core components in Figma; established design-review process; adoption reached 70% of the product team within 6 months." This shows you didn't just create assets—you drove adoption and changed how the team works. It also shows you iterated on it. Design systems are alive; they change as the product changes. Showing that yours evolved based on feedback is stronger than showing it was perfect on day one.

A design system is also proof of cross-functional collaboration. You had to work with engineering to understand what's feasible, with product to understand what matters, with the entire design team to get buy-in. Your resume can touch on this: "Built design system; worked with eng to ensure component APIs matched product needs; socialized with the team via monthly design reviews." This shows you didn't silently create something and hand it over. You engaged people.

Usability testing as a research signal, not a feature

Many designers list usability testing as a skill without showing they actually used it to drive decisions. "Conducted usability testing" is a task. "Conducted fortnightly usability tests with 5–8 users per round; findings drove iteration on the primary navigation, improving task success rate from 62% to 91%" shows testing was a decision-making tool, not a box to check. The metric (task success) proves testing was rigorous and outcome-focused. The frequency (fortnightly) suggests testing was part of the normal process, not a one-off.

The strongest design resumes show research fed into specific decisions. "Ran user interviews that identified three critical gaps in our settings experience; prioritized the three high-impact improvements and shipped them together; support tickets for account settings dropped 34%." Here, research identified real problems, you prioritized, you executed, and you measured the outcome. That's the full cycle of good design work. Research that doesn't lead to decisions is interesting but not strategic.

One more credibility signal: research rigor. "Ran user interviews" is vague. "Ran 12 one-on-one interviews with users in each segment (free, pro, enterprise); documented findings in a shared research repo that 20 team members access; identified 8 candidate problems, prioritized by frequency and impact, and shipped fixes for the top 3." This shows you did systematic, reproducible work. Other team members could read your research and understand your reasoning. That's the difference between research as intuition and research as method.

Frequently asked questions

Should I include my Dribbble or Behance link on my resume?

Only if your best work is there. If your personal portfolio is stronger and more complete (case studies, process, outcomes), link that instead. Dribbble and Behance are good for visual work, but they often lack the context hiring managers want. One portfolio link is cleaner than three.

What if some of my work is under NDA?

Show it anyway, but get permission from your former employer first. Many will let you share sanitized case studies if you remove the company name, client names, and any proprietary data. If you can't share work, write a case study in the portfolio that describes the project, your process, and the outcome without sharing any visuals. Hiring managers understand NDA constraints and respect the hustle to work around them.

How much should I talk about tools like Figma or Adobe XD?

Mention them once, grouped by function. "Tools: Figma, Prototyping, Usability testing, HTML/CSS" is enough. Don't list every tool you've ever opened. Hiring managers care that you can learn software, not that you're a Figma power user. If you've coded CSS or HTML to bring designs to life, mention it—that's a real advantage.

Is a design degree necessary to be a designer?

No. A portfolio that proves you can do the work matters more. If you're self-taught or bootcamp-trained, your portfolio is your degree. Just make sure your case studies show process, not just pretty screens, so hiring managers know you can articulate your thinking.

How do I handle a portfolio gap if I've been in non-design roles?

Show a personal project or side work that demonstrates current skills. "Redesigned the UI for an open-source project; improved mobile usability score from 62 to 89" is credible. If you've been out of design, do a small project, document the process, and put it in the portfolio. It shows you're serious and current.