Examples & writing guide
UX designer CV examples
Updated 7 November 2026
Connect a research finding to the prototype decision it changed: occupational guidance for UX designers in England describes designing and testing prototypes from user research, refining designs through follow-up evidence and explaining solutions clearly to stakeholders. These entry and senior UX designer CV examples show how to present that chain of reasoning, with project evidence for a first role and broader responsibility for an experienced applicant.
Examples by experience level
Junior UX designer - Community project and customer support
TemplateTeal Signal2 / 5
Why this works
The project connects a research finding to a design decision and an observed result without implying previous full-time UX employment; this profile, every employer, the history and all achievement figures are fictional and illustrative.
Continue writing your CVSenior UX designer - Service redesign and team responsibility
TemplateBlue Horizon3 / 5
Why this works
Progression across three roles makes wider design responsibility visible while distinguishing personal decisions from team delivery; this profile, every employer, the history and all achievement figures are fictional and illustrative.
Continue writing your CVJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Personal statement | Riley identifies a first-role goal and supports it with a community project and customer support background. | Jordan introduces nine years of experience, responsibility across two service journeys and support for two designers. |
| Main evidence | Riley's booking project explains how participant feedback changed the prototype and records the second-round result. | Jordan's recent role connects research findings to design scope, release sequencing and stakeholder agreement. |
| Ownership | Riley designed the volunteer prototype and presented recommendations to the centre coordinator. | Jordan owns design decisions across two journeys and coaches two designers, while identifying researcher and developer contributions. |
| Results and their limits | Riley reports five of six participants completing a revised task without prompting, within a small project. | Jordan reports prototype findings as directional evidence and also explains the agreed release decision. |
| Section emphasis | The recent community project leads experience; the education note adds a separate learning example. | Recent employment carries the detail, followed by earlier roles that show progression; education stays compact. |
How to write an UX designer CV
Use reverse-chronological order within experience, projects and education, so the reader can follow your most recent work first. Start with contact details and a focused personal statement, then place your strongest relevant evidence next. Riley's project deserves space before earlier customer support work; Jordan's recent employment carries the main argument.
Choose the shortest readable length that covers your relevant evidence. Cut repeated duties before reducing text size, and keep dates and spacing consistent. Check the target application's instructions for any requested format, file type or additional material.
| Section | Writing pointer |
|---|---|
| Contact details | Keep your name, location and contact information easy to find. |
| Personal statement | Connect your background to evidence developed later in the CV. |
| Experience or projects | Give the strongest relevant work space and make your contribution clear. |
| Skills | Select capabilities you can connect to a specific example. |
| Education | Record your learning accurately and add relevant project detail selectively. |
| Extras | Include material that adds evidence rather than repeating another section. |
Treat a UX designer CV template as a starting structure. Adjust the space given to each section around your own history: a junior UX designer CV can build its argument through a substantial project, while Jordan's version uses sustained employment and wider decisions.
Personal statement examples
Riley Sample: Design graduate seeking a first UX Designer role, with a community booking project and customer support experience. Used feedback from six participants to revise a booking prototype; five completed the revised task without prompting in a second round. This works because it identifies Riley's starting point and gives a concrete result developed in the project entry. For your own opening, connect your background, strongest evidence and intended contribution. Riley can point to project decisions; Jordan can draw on nine years of work and responsibility across two service journeys.
I am a passionate and innovative UX designer with excellent skills and a strong eye for detail. I want an exciting opportunity where I can make a difference. This version leaves the reader to guess what Riley has done. It also blurs the distinction between seeking a first role and already having an established UX career.
Writing your experience
Occupational guidance for UX designers in England describes research-based prototype design and testing, refinement through follow-up evidence and clear explanations of design solutions to stakeholders. Use whichever of those subjects your own work supports; a CV does not need to claim every duty.
Build each achievement around a problem, your action, the decision you made and the observed result. A useful test is whether the reader can explain why you changed the design after reading the bullet. Name the finding that shaped your choice rather than simply saying you used research.
These fictional before-and-after examples show the difference:
- Before: "Created a booking prototype." After: "Compared two booking flows after participants searched by activity rather than date; selected a session-first route and recorded why the calendar-first option was rejected." The revision makes Riley's decision visible without inflating the volunteer project into a commercial launch.
- Before: "Improved the account-change journey." After: "Separated contact and payment changes after research exposed confusion between the two; agreed a staged release with product and development leads while payment questions remained unresolved." This gives Jordan's wider responsibility a concrete boundary.
- Before: "Presented designs to stakeholders." After: "Presented research clips and two cancellation-flow alternatives to operations stakeholders; gained agreement to remove an ambiguous confirmation step." The outcome is a documented decision, so a percentage adds nothing here.
Choose verbs that describe your contribution: compared, designed, tested, revised, explained or recommended. Use supported or observed when those better reflect your role. If research was a colleague's responsibility, explain how you used the findings rather than claiming you led the study.
For an entry project, state what you owned and who reviewed it. For senior work, explain which decisions were yours, where others contributed and what happened after the decision.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
List education and training in reverse-chronological order. Give the qualification or course title, provider and completion date. For learning still in progress, state its status clearly and label any expected completion date as expected. Keep completed study distinct from attendance or unfinished work.
For an entry applicant, relevant learning can add substance when employment is limited. Choose a project that helps explain your contribution: what you investigated, what you produced and what changed after feedback. Riley's education entry briefly mentions a prototype comparison; the more detailed community project sits in experience, where its decisions and results have room to breathe.
For an experienced applicant, give education enough space to be clear without repeating earlier project detail that recent work already demonstrates. Jordan's compact record leaves room for the service decisions and coaching responsibility described above.
If you include additional training, use its exact title and provider, and distinguish completion from participation. Add a short note about resulting work only when it contributes something useful to the application. Avoid presenting a course title as proof of experience you have not gained.
Check that titles, dates and completion status agree across your CV and application. Follow the target posting's instructions about any requested education details or supporting documents.
Common mistakes to avoid
AvoidListing skills without showing where you used them.
InsteadConnect each prominent skill to a project or employment entry. Replace a vague software rating with a brief explanation of what you produced or changed.
AvoidReporting a result without explaining the design decision.
InsteadAdd the finding, your response and the relevant context. For a test result, distinguish a participant count from a claim about wider business performance.
AvoidClaiming team work as personal ownership.
InsteadSeparate what you designed, recommended or supported from what researchers, developers and other designers contributed.
AvoidUsing dates or job titles that conflict elsewhere in the application.
InsteadCheck the chronology against your records and use consistent titles. Label volunteer and project work clearly, as Riley's example does.
AvoidMaking every task look equally important.
InsteadGive more space to decisions that support the role you are targeting. Remove repeated duties and split dense paragraphs into concise achievement bullets.
Frequently asked questions
Use a clearly labelled project, internship, volunteer assignment or transferable employment example. Explain the problem, your own contribution and what you learned or changed; Riley's project shows how to do this without claiming a previous full-time UX title.
Use the shortest readable length that covers your relevant evidence and follows the target application's instructions. Remove repeated tasks before shrinking the text or squeezing the spacing.
Choose examples that let you explain your decisions and personal contribution. A focused account of what changed after feedback is more useful as writing evidence than a collection of unexplained screens; follow any instructions about submitting additional material.
Name tools you actually used when they are relevant to the application, then explain the work they supported. Avoid filling your CV with ratings that the experience section cannot substantiate.
Use the structure, then replace it with your own exact study titles, providers, dates and completion status. Give a learning project extra space only when it adds evidence beyond the rest of your CV.
Follow the target posting's instructions about photographs and file types. Keep your chosen layout readable and check the saved version before submitting it.
From example to application
Turn this UX designer example into a CV that sounds like you.
Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.