A UI designer's resume has one job that other resumes don't: it has to work alongside a portfolio, not instead of it. The portfolio shows the screens. The resume needs to cover everything a portfolio can't — the tools you used, the kind of projects you've worked on, and what part you actually played when a project had five other people attached to it. This template is built for exactly that, so links, tools, and project details all have their own space instead of getting squeezed into a paragraph nobody reads.
A lot of designer resumes make the mistake of trying to describe the visuals in words — "created clean, modern, user-friendly interfaces." That line could belong to literally anyone. It says nothing your portfolio doesn't already say better, with actual pictures. The resume's real job is different: show the thinking, the process, and the responsibility behind the screens someone's about to click through.
Who Should Use This Template
This format fits pretty much anyone doing product or interface design, including if you work on:
- Websites
- Mobile or web apps
- Dashboards
- Landing pages
- Brand screens
- Full product flows, start to finish
Doesn't matter if you're freelance, in-house at one company, or bouncing between agency projects. What matters more is whether you can show real project work with real outcomes, not just polished mockups sitting on their own with no context.
Writing the Summary
Keep this tight and specific to the kind of design work you actually do. Don't open with a personality description — open with what you build and how.
Something like: "UI designer focused on dashboard and mobile app design, working in Figma from wireframes through to developer handoff." That one line already tells someone what to expect from the rest of the resume.
Only mention things like wireframes, user flows, responsive design, or handoff if you've genuinely done that part of the work. It's common for junior designers to list every stage of the design process because it sounds thorough, and then the interview exposes that they only ever touched the visual layer. Better to claim less and be able to back up every word of it.
What to Include
A designer's resume needs to answer three different questions for a reader, and it helps to keep them visually separate instead of blending them into one long paragraph.
| Category | What Goes Here |
|---|
| Portfolio & Tools | Your portfolio link, the tools you design in — Figma, Sketch, Adobe XD — and the kind of projects you've worked on |
| Design Output | Wireframes, UI screens, design systems you've built or contributed to, prototypes you've made |
| Process & Collaboration | Developer handoff, how you've incorporated client or user feedback, usability changes you've made |
The portfolio link deserves its own line near the top, not buried at the bottom under contact details. It's often the first thing a recruiter clicks, sometimes before they read a single word of the resume itself.
Talking About Actual Projects
This is where most designer resumes go flat. Instead of describing a project as a task you completed, describe it the way you'd explain it to another designer — what the problem was, what you did about it, and what changed.
- What the project was actually for — a booking app, an internal dashboard, a landing page redesign
- Where you started — existing product, blank page, a rough brief from a client
- What you personally designed, especially if it was a team project
- Any decision you made that mattered — simplifying a flow, cutting steps out of a signup process, reworking a layout after user testing
A line like "redesigned the onboarding flow, cutting the signup process from 6 steps to 3" tells a hiring manager something concrete. "Designed user-friendly onboarding experiences" doesn't, even though both sentences might describe the exact same piece of work.
Developer Handoff and Collaboration
If you've worked closely with developers, this is worth calling out specifically, because it tells a hiring team you understand that a design isn't finished when the mockup looks good — it's finished when it actually gets built the way you intended.
Mention things like whether you've documented specs, used tools like Figma's inspect mode, or gone back and forth with engineers on what's realistically feasible. Even a short line like "worked directly with two developers on implementation, adjusting spacing and states based on technical constraints" shows a level of maturity a lot of junior portfolios don't demonstrate.
Your portfolio shows the visuals. Your resume should explain the thinking and responsibility behind them.
That's really the whole point of this format. A portfolio can show that you can design a clean screen. It can't show whether you understood the problem, made a call under a deadline, or handled feedback that contradicted your first instinct. That's what the resume is for.
Usability and Feedback
If you've run or contributed to any usability testing, even informally, include it. Something as simple as "ran five user interviews before finalizing the checkout flow" shows a process, not just an aesthetic sense. Same goes for client feedback — if you've taken rounds of revisions and turned them into something better rather than just following instructions, that's worth a mention too.
Keeping Contact Details Simple
Don't overdesign this part, ironically. Just make sure it's complete:
- Full name
- Phone number
- A professional email address
- Portfolio link
- LinkedIn, Dribbble, or Behance, if any of those are actually active
If a Dribbble or Behance profile hasn't been touched in over a year, it's probably better left off than linked and looking abandoned.
A Mistake Worth Avoiding
Some designers try to make their resume itself a design showcase — heavy layouts, custom icons, unusual grids. It can work, but it's risky, especially if the resume ever gets passed through an ATS or printed out for a panel review. A resume is not a portfolio piece. Keep the design restrained and let the actual work do the impressing, with a link to the portfolio doing the rest.
Final Thoughts
A designer's resume works best when it stays out of its own way — clear tools, real project details, and a summary that says exactly what kind of design work you do. The visuals belong in the portfolio. The resume's job is to explain the decisions behind them, and to make it easy for someone to click through and see the rest.