UX/UI designer resume guide, examples and templates
Show how you moved from a user problem to a design decision. Compare three real resume layouts, read a complete UX/UI example and connect your research, interface work and portfolio without overstating the results.
These previews use the same layouts as the builder, with identical example content. Open a full preview to inspect the text and spacing.
Fictional candidate, employers, education and results. The optional portrait is AI-generated. Use your own evidence and photo; the example is not inserted into your resume.
Studio
Teal section bands and a structured introduction give interface designers a distinct presentation while keeping the work readable.
Before sending: The education rail is narrow, while projects follow experience in the main column. Keep supporting details short and use a portfolio for full case studies.
“Use” opens signup with that design and photo preference selected for the builder. A free account is required. Free-plan PDF downloads include a watermark; see current plans for paid options. Photo conventions vary; follow the employer’s instructions and local expectations.
For a closer look at Studio’s separate contact, profile and skills areas, explore the Studio template design guide.
Make your UX and UI contribution visible
A polished screen is evidence of a finished artifact. Your resume also needs to explain the work behind it: the problem you investigated, the behavior you designed and the decisions you made with others. “UX/UI” can span different responsibilities, so choose examples that match the opening instead of presenting every designer as a researcher, visual specialist and design-system owner at once.
Cala Health’s UI/UX role combines interface design, research, component systems and engineering documentation. Livefront’s product-design role describes user flows, visual craft, prototypes and work within platform constraints. These are examples of scope, not a universal hiring checklist. A specialist UI application may lead with visual hierarchy and state design; an interaction-focused application may lead with a difficult workflow and the evidence behind its revision.
An adjacent early-career example, Envoy Global’s Product Designer role in Hyderabad, emphasizes comparing approaches, testable journeys and interface-state documentation. It illustrates a related role outside the US rather than a general US requirement.
Keep your real employment titles. You can explain a relevant responsibility in a bullet without renaming a junior role as “Lead UX Designer.” Likewise, distinguish a design that shipped from one tested in a prototype, and a study you supported from one you independently planned and ran.
A complete UX/UI designer resume example
Taylor Brooks is a fictional designer with four years in workplace and booking software. Every employer, qualification, participant count and result below is invented for teaching. All three designs use this same content. The independent concept is labeled clearly, and no live portfolio is implied.
Taylor Brooks
UX/UI Designer
taylor.brooks@example.com · Fictional example
Summary
UX/UI designer with four years in workplace and booking software. Connects research findings to interaction decisions, detailed interface states and engineering reviews.
Experience
UX/UI Designer · Cedarline Workspace
July 2024–present
Co-moderated six administrator interviews with a researcher; mapped permission-review pain points and prioritized two navigation changes with product.
Prototyped two permission-review flows in Figma; retained an explicit confirmation step after engineering review of audit requirements.
Observed seven of eight participants complete a prototype permission task without help; revised the unclear label found in the remaining session.
Junior UI Designer · Orchard Booking
July 2022–June 2024
Specified focus order, error messages and responsive states for a booking form; reviewed implementation with engineers before release.
Added empty and loading states to an existing component library; documented usage rules and incorporated feedback from two product teams.
Created a room-booking concept; tested its prototype with five volunteers and documented changes to availability labels. Not commissioned or shipped.
Education
B.A. in Interaction Design · Westhaven University · May 2022
Notice the two different research activities: six discovery interviews and a later prototype study with eight participants. Their counts answer different questions and should not be combined. The resume also describes the label that needed revision, rather than using a success number to hide the remaining issue.
Six UX/UI bullet rewrites with evidence checks
Build each claim around your action → design context → decision, observation or contribution. A specific, defensible decision can be more useful than an invented conversion lift. The examples below are teaching rewrites, not text to copy as your own experience.
1. Research scope and your contribution
Vague version
Led user research to understand customer needs.
Specific version
Co-moderated six administrator interviews with a researcher; mapped permission-review pain points and prioritized two navigation changes with product.
Names the participants, method and shared responsibility. Co-moderating is useful evidence without claiming ownership of recruitment, the whole research program or a representative survey.
Check before using a similar claim: Your interview tasks, contribution to synthesis, participant criteria and the decision record.
2. A design decision with a constraint
Vague version
Designed intuitive experiences in Figma.
Specific version
Prototyped two permission-review flows in Figma; retained an explicit confirmation step after engineering review of audit requirements.
Shows an alternative considered and why the shortest flow was not automatically the best choice. The result is a justified interaction decision, not an unsupported claim that the interface became intuitive.
Check before using a similar claim: The compared flows, constraint, critique notes and your role in the final decision.
3. A bounded usability observation
Vague version
Achieved 88% usability and improved customer satisfaction.
Specific version
Observed seven of eight participants complete a prototype permission task without help; revised the unclear label found in the remaining session.
Reports the task and participant count in a separate prototype study. It does not establish population success, improvement over a baseline, satisfaction or a shipped product result. The unresolved finding still matters.
Check before using a similar claim: Task wording, participant criteria, assistance rules, session notes and the prototype version tested.
4. Specific UI and implementation work
Vague version
Ensured accessible designs and seamless developer handoff.
Specific version
Specified focus order, error messages and responsive states for a booking form; reviewed implementation with engineers before release.
Replaces broad assurances with inspectable interface details and collaboration. These activities alone do not establish full accessibility conformance or that every implementation issue was resolved.
Check before using a similar claim: Annotated states, implementation-review findings and the checks you personally performed.
5. A design-system contribution
Vague version
Built and owned the company design system.
Specific version
Added empty and loading states to an existing component library; documented usage rules and incorporated feedback from two product teams.
Makes the boundary clear: contributing states and guidance to an existing system is different from creating or owning the entire system. Name the contribution that another designer could inspect.
Check before using a similar claim: Component changes, usage guidance, reviews and what was accepted into the shared library.
6. An honest concept project
Vague version
Transformed the library booking experience for thousands of users.
Specific version
Created a room-booking concept; tested its prototype with five volunteers and documented changes to availability labels. Not commissioned or shipped.
Identifies an independent concept and a limited test. Volunteers may not represent actual library patrons; a prototype is not evidence of adoption, client work or a production outcome.
Check before using a similar claim: Recruitment limitations, task notes, before-and-after screens and a clear concept-study label.
Nielsen Norman Group’s usability-testing overview distinguishes discovering problems from collecting quantitative benchmarks. In this sample, “seven of eight” describes the observed sessions. Rounding it to “88% usability” would erase what was measured. Without comparable baseline tasks and conditions, it also cannot establish an improvement caused by the design.
Support skills with work the reader can inspect
Use the vacancy’s terminology when it accurately describes your experience. Figma is a tool; interaction design, research synthesis and implementation review describe different work. List a method only if you can explain how you used it, and replace proficiency bars with concrete evidence.
UX/UI skills and supporting evidence from the fictional sample
Skill area
Evidence to include
Example in Taylor’s resume
Research
What you did, with whom and how it informed a decision.
Co-moderated administrator interviews and prioritized navigation work.
Interaction design
A flow, alternative or constraint that shaped behavior.
Compared two permission flows and retained a confirmation step.
Usability testing
Task, participant scope, observation and resulting change.
Seven of eight participants completed one prototype task without help.
Visual and UI craft
Hierarchy, states, responsive behavior or interface details.
Specified error messages, focus order and form states.
Design systems
The exact contribution and how others use it.
Added component states and documented usage rules.
Collaboration
A decision, review or implementation activity you contributed to.
Reviewed constraints and the built interface with engineers.
Describe accessibility work at the level you actually performed. Specifying focus order or reviewing error states is meaningful; it is not interchangeable with auditing an entire product or certifying conformance. If a specialist checked the design, explain that collaboration rather than taking credit for their assessment.
Connect the resume to a case study, not a gallery alone
The resume gives the short claim. A portfolio can show the reasoning and artifacts behind it. NN/g’s portfolio guidance recommends explaining the problem, individual role, design process and iterations alongside final screens. Select evidence relevant to the role rather than showing every project you have ever touched.
Name the problem and scope. For Taylor’s permission flow, explain who reviews access and what made the existing task difficult. State whether the work reached production or remained a prototype.
Separate your work from the team’s. Identify who recruited participants, moderated sessions, analyzed findings and implemented the interface. Explain your contribution without presenting a team deliverable as solo work.
Show the decision trail. Compare the two flows and explain the confirmation-step tradeoff. A rejected alternative can show judgment when its drawback is clear.
Pair a finding with a change. Show the label that caused difficulty and the revision. Include the study context and remaining uncertainty instead of converting a small sample into a product-wide claim.
Make the link usable. Add a clearly labeled portfolio URL to your real resume and test it without being signed in. Check permissions, mobile readability and the employer’s requested format. Share only material you are authorized to disclose; use an explicitly labeled reconstruction or sanitized example when appropriate.
This fictional sample deliberately has no portfolio link: there is no real case study behind the invented candidate. For your own application, a working link should lead to work you can discuss. A case-study title, one relevant sentence and a link usually serve a resume better than screenshots squeezed into the experience section.
Adapt the evidence to your career stage
First UX/UI role
A course, volunteer or independent study can show useful judgment. Label its setting, your contribution and whether it shipped. Explain how participants were recruited; friends testing a concept are not automatically representative customers. Keep relevant earlier work if it demonstrates problem definition, communication or interface craft.
Taylor’s concept entry could move above employment for a career changer. Expand its method and limitation rather than inventing a client, adoption count or commercial result. Name a course certificate accurately; completing training does not turn a concept into professional employment.
Experienced or senior role
Prioritize decisions with meaningful scope: a cross-team workflow, a design-system change adopted by others, or how you resolved a constraint. Explain whose decision it was and your influence. Mentoring, critique and coordination need concrete examples just as design execution does.
Avoid claiming the whole product outcome when several teams contributed. If post-launch results are available, state the measure, observation window and your role. If they are unavailable, describe what shipped, how it was reviewed and what remains unknown.
Review the resume and keep the application consistent
Compare the target role’s UX, UI and collaboration needs with the evidence you lead with.
Verify dates, titles, study counts and ownership against your records. Distinguish observations, recommendations and released changes.
Read the exported resume at full size, copy its text and check the application fields after upload. Follow the employer’s file-format instructions.
Open the portfolio link and check that its project status, role description and results agree with the resume.
The three design buttons above open signup for the selected builder layout and photo preference. A free account is required; free-plan PDFs include a watermark. See pricing for paid options. This guide does not provide a separate Word or Google Docs download.
Should a UX/UI designer resume include a portfolio?
Follow the employer’s application requirements. The employer examples cited here ask for portfolio evidence. If you have relevant work you can share, add a clearly labeled, working link. Explain the project context and your contribution; a collection of attractive screens alone may not show how you made decisions.
Can I use usability-test results in a resume bullet?
Yes, when you can explain the task, participants, method and observation. Keep the count and context clear. A small prototype study does not establish a population-wide success rate, customer satisfaction or an improvement without comparable evidence.
Do I need a creative resume layout for a design job?
Choose a layout that makes your evidence easy to read. Studio, Editorial and Banner offer different visual structures, but no design guarantees interviews or parsing accuracy. Use your portfolio for detailed visual work and follow the employer’s format instructions.
Should I include a photo?
Use the employer’s instructions and the norms relevant to your application. The photo toggle is an optional preview comparison; this sample portrait is fictional. Selecting a photo layout does not add the sample portrait to your real resume.
Sources and editorial scope
Resumize prepared this page with AI-assisted research and drafting, primary-source checks and separate content and functionality review. Sources were checked on October 23, 2026. US employer examples and the explicitly identified Hyderabad role illustrate how responsibilities vary; they do not measure hiring prevalence or define every UX/UI role. Job descriptions can change or close. The candidate and study results are fictional. Advice is editorial guidance, not a promise of hiring or search results.
US employer example connecting visual and interaction design, user research, component systems and engineering documentation. Its healthcare-specific requirements are not universal UX qualifications.
Portfolio guidance: explain the problem, individual role, design reasoning and iterations alongside final screens. Published in 2019; not a current hiring-prevalence estimate.
International early-career employer example: comparing approaches, creating testable journeys and documenting interface states for engineering. An adjacent Product Designer title, not evidence of US hiring prevalence.