UI/UX Designer resume
For designers, your portfolio decides the outcome and your resume decides whether the portfolio even gets opened. So the resume has one narrow job. Get the link clicked, and show that you think about the problem and not only about the screens.
- 01A working portfolio link, at the very top, above everything else.
- 02Process evidence: your research, testing and iteration, alongside the final visuals.
- 03Outcomes from design decisions: task completion, drop-off, support tickets, conversion.
- 04Whether you have shipped with engineers, and whether you have built or worked in a design system.
Tools
- Figma
- prototyping
- design system
- wireframing
- Adobe XD
Research
- user research
- usability testing
- personas
- journey mapping
- A/B testing
Craft
- interaction design
- information architecture
- responsive design
- accessibility
- WCAG
Put down only what is true and what you can be interviewed on. A term you cannot defend will win you the screening and then lose you the interview.
Designed UI screens for the mobile app and created wireframes and prototypes in Figma.
Redesigned the KYC flow after 8 usability sessions, cutting drop-off at document upload from 41% to 18% and removing the top driver of support tickets.
- A portfolio link that needs a password, or that the reviewer has to email you for. Most won't bother.
- Case studies that are three screenshots with no problem statement and no outcome.
- A resume that's itself badly typeset. For this role it's a work sample whether you meant it to be or not.
Check yours against a real posting
Paste your resume and a ui/ux designer job description into the free ATS score checker or browse live ui/ux designer openings.
Check My ATS Score FreeHow many case studies should my portfolio have?
Three, each with the problem, what you did, and what changed. Depth is what gets you the interview.
Should my resume be visually designed?
Clean and well typeset, yes. Two-column and heavily graphical, no. It still has to survive a parser at most companies.
Do I need to know how to code?
Not required, but understanding component structure and constraints makes you notably easier to work with, and it's worth a line if it's true.