UX Designer CV Example and Writing Guide [2026]

A UX Designer CV works best when it is shaped around the job you want, not every design task you have ever handled. Before you write the first line, read the advert and mark the repeated signals. Does it mention user research, discovery, accessibility, design systems, mobile journeys, stakeholder workshops, SaaS onboarding, conversion optimisation, or public-sector service design?

Those words tell you what the employer is trying to buy. If the role is research-heavy, your first screen should show interviews, usability testing, research synthesis, problem framing, and findings that changed the roadmap. If the role is interaction-heavy, lead with flows, wireframes, prototypes, design systems, and handover quality. If the role sits inside a small product team, show that you can move between discovery, design, validation, and delivery without waiting for a perfect process.

This does not mean stuffing the CV with keywords. It means making the most relevant evidence easy to find. A recruiter should not have to guess whether your background matches the role. Put the right examples near the top, trim less relevant visual-design or marketing work, and use the same language the hiring team uses where it genuinely matches your experience.

A practical way to do this is to write a short target sentence before the CV. For example: “I am applying for a UX designer role focused on B2B SaaS onboarding, research synthesis, and design system collaboration.” Then check every section against that sentence. Anything that supports it can stay. Anything that distracts from it should be shortened or removed.

Your profile should do more than say you are creative, user-focused, or passionate about good experiences. Those phrases are common, and they do not show how you work. Use the first three or four lines to explain your design context, your strongest methods, and the kind of outcomes you can support.

A weak profile might say: “Creative UX designer with strong communication skills and a passion for user-centred design.” A stronger profile would say: “UX designer with five years of experience improving SaaS onboarding and account-management journeys. Skilled in user interviews, wireframing, prototype testing, and Figma handover, with recent work reducing form drop-off and support tickets across self-service flows.”

The second version gives the reader more to trust. It shows product area, methods, tools, and impact. It also creates a clear bridge into the experience section, where you can prove the claims with projects and achievements.

Keep the profile short. Four focused lines usually work better than a dense paragraph. If you are early in your career, mention your strongest project, placement, bootcamp, or portfolio focus. If you are senior, mention leadership, service complexity, research strategy, stakeholder influence, or design system ownership. If you are moving from UI, graphic design, psychology, customer research, content design, or product management, explain the connection briefly rather than hiding it.

You can include a portfolio link in or near the profile, but do not use the profile to summarise every case study. The CV should tell the recruiter why your portfolio is worth opening. The portfolio then gives depth.

UX design experience can become vague if you only list responsibilities. “Created wireframes”, “conducted user research”, and “worked with stakeholders” are useful signals, but they do not show quality. Turn each bullet into a small piece of evidence.

Use a simple formula: design action, context, result. For example: “Redesigned a multi-step account setup journey after user testing showed confusion around verification, helping the product team cut avoidable support queries by 22%.” That bullet tells the reader what you did, why you did it, and what changed.

Metrics are helpful, but they are not the only kind of proof. UX work often influences outcomes that are hard to isolate. You can still show impact through evidence such as “reduced repeated handover questions”, “shortened workshop alignment from three sessions to one”, “identified the top five causes of drop-off”, “improved accessibility defects before beta”, or “gave engineers annotated flows that reduced rework”.

For each role, choose three to five bullets. Your current or most recent UX role can be more detailed. Older roles can be shorter unless they contain work that is directly relevant to the target job. If you moved through adjacent positions, such as product designer, UI designer, digital designer, researcher, or business analyst, keep the wording focused on UX contribution rather than job title alone.

A good UX experience section should show discovery, design, testing, and delivery. It should also show collaboration. Product managers, engineers, content designers, data analysts, customer support teams, subject-matter experts, and accessibility specialists all shape real UX work. Mention the collaboration when it proves judgement, alignment, or delivery quality.

Your UX portfolio carries the deeper story. Your CV should make the recruiter want to open it. Add a portfolio link near your contact details and include two or three short project entries that point to the strongest case-study themes.

A project entry should be short enough to scan. Name the project, describe the problem, and list the evidence that matters. For example:

• Checkout recovery redesign: Led research and prototype testing for a high-friction checkout flow; mapped the main failure points, simplified form states, and supported a release that improved completion.
• Internal dashboard discovery: Interviewed operations users, grouped pain points into workflow themes, and created low-fidelity prototypes that helped the team prioritise the next build phase.
• Accessibility review sprint: Audited key journey templates against WCAG 2.2 principles, tested keyboard navigation, and worked with engineers to fix issues before public beta.

Do not repeat every portfolio detail. A recruiter will not read a full case study inside the CV. Use the CV to show the headline: what problem you worked on, what you contributed, and why it mattered. Then let the portfolio show artefacts, research notes, screens, decisions, and trade-offs.

If you cannot share confidential product work, explain the shape of the problem without naming the client. You can write “B2B onboarding flow for a financial services platform” or “internal case-management tool for a regulated service team”. That is better than leaving the project blank.

Many UX roles expect you to work with evidence. Even if the job is not pure research, employers want to know how you understand users before designing. Show the research methods you can use and, more importantly, how research changed the product.

Mention interviews, usability testing, contextual observation, surveys, analytics review, support-ticket analysis, diary studies, discovery workshops, or research synthesis only where you used them. Pair each method with a practical result. “Ran six moderated usability tests” is fine. “Ran six moderated usability tests that exposed confusion around account permissions and changed the navigation labels before build” is stronger.

The GOV.UK Service Manual frames user research around understanding user needs, planning research, preparing sessions, sharing findings, and analysing what has been learned. That is useful language for a CV because it shows the full loop: you did not only run sessions; you turned findings into decisions.

If you are junior, you may have fewer live research examples. Use portfolio projects, coursework, volunteering, hackathons, or redesign exercises, but be honest about the context. You can still show that you wrote research questions, recruited participants, took notes, identified themes, and changed a prototype because of what you learned.

If you are senior, show research leadership. That might include planning discovery work, setting research objectives, choosing the right method, helping non-designers observe sessions, protecting research quality under time pressure, or turning messy findings into a clear product decision.

Accessibility belongs in a UX Designer CV when you have evidence to support it. In the UK, accessibility is a practical product concern, especially for public services, education, healthcare, finance, SaaS platforms, and products with broad audiences. GOV.UK guidance says teams should think about accessibility from the start, include disabled people in research, and meet WCAG 2.2 level AA as a minimum for government digital services. W3C’s WCAG 2.2 standard is also a useful reference point for digital accessibility language.

Do not write “accessibility aware” and stop there. Give examples. You might mention keyboard navigation, focus states, form labels, colour contrast, error messages, screen-reader-friendly structure, inclusive research recruitment, accessibility audits, or prototype reviews. If your experience is limited, say what you contributed rather than pretending to be a specialist.

A strong bullet could be: “Worked with engineers to improve focus states, error messages, and form labelling across a sign-up journey, reducing accessibility defects before beta release.” That bullet is more useful than “Knowledge of accessibility” because it shows how the knowledge affected work.

Accessibility also helps differentiate you from applicants who talk only about visuals. A UX designer who can consider different devices, assistive technology, cognitive load, and real-world use conditions brings value beyond tidy screens.

Tools matter, but they should not dominate the CV. Figma, FigJam, Miro, Maze, Dovetail, Hotjar, Google Analytics, Jira, Confluence, Storybook, Adobe tools, and design system documentation can help a recruiter understand your workflow. They are not proof on their own.

Group tools with methods so the skills section feels practical. For example, instead of writing a long flat list, use clusters:

• Research and discovery: interviews, usability testing, survey analysis, journey mapping, research synthesis.
• Interaction design: user flows, wireframes, prototypes, information architecture, design patterns.
• Delivery: Figma components, design system usage, annotated handover, acceptance criteria, design QA.
• Accessibility: WCAG 2.2 awareness, keyboard testing, form labelling, contrast checks, inclusive research.

This makes the skills section easier to scan and helps applicant tracking systems pick up relevant terms without turning the page into a keyword dump.

If the job advert asks for a specific tool you have used, include it. If you have not used it, do not pretend. Many UX tools can be learned quickly, but false tool claims are easy to expose in a portfolio review or interview.

A Junior UX Designer CV should show potential, process, and coachability. Recruiters will not expect a long list of shipped outcomes, but they will expect clear thinking. Use portfolio projects to show how you framed a problem, chose research methods, tested ideas, iterated, and reflected on trade-offs. Include education, bootcamp work, internships, placements, volunteering, or adjacent experience where it proves user empathy, communication, analysis, or digital delivery.

Your junior bullets can still be evidence-led. For example: “Tested a low-fidelity booking prototype with five participants, identified repeated confusion around date selection, and simplified the flow before high-fidelity design.” That is stronger than “Created a booking app prototype”.

A Senior UX Designer CV should show influence and ownership. Include examples of leading discovery, shaping design direction, mentoring designers, improving team process, aligning product and engineering, working with analytics, and raising accessibility or research standards. Senior applications should also show how you handle ambiguity. Employers want to know that you can move from unclear problem to useful product direction without waiting for perfect information.

If you are applying to a lead or principal role, add more evidence of strategy: research planning, service blueprinting, design principles, cross-team design systems, stakeholder facilitation, product metrics, and decision-making under constraints. Keep the CV concise, but make sure your scope is visible.

A UX Designer CV should be well-designed, but it should not behave like a portfolio page. Avoid experimental layouts, tiny text, complex sidebars, low contrast, image-heavy sections, and visual flourishes that make the content harder to parse. The recruiter may read it in an ATS, on a laptop, or as a PDF preview. Clarity beats novelty.

Use a clean two-page structure if you have enough relevant experience. One page can work for early-career candidates, but do not cram the page so tightly that the work becomes hard to understand. Use clear headings, consistent dates, short bullets, and enough white space.

Place contact details, location, portfolio link, and LinkedIn or website at the top. Use a profile, key skills, experience, projects, education or certifications, and optional additional sections. Put the most relevant section before less important material. If your portfolio is excellent but your employment history is short, feature selected projects earlier. If you have strong product experience, lead with experience.

Export as a PDF unless the employer requests another format. Check that links work, text can be selected, and the file name is professional, such as mia-carter-ux-designer-cv.pdf.

Keep this section simple. Include your name, target title, location, email, phone, LinkedIn if useful, and portfolio URL. If you work remotely or are open to hybrid roles, mention that briefly only where it helps. For example: “London, UK — open to hybrid UX roles”.

Your portfolio link should be easy to spot. Avoid hiding it in a paragraph. If the portfolio needs a password, include it only if you are comfortable sharing it with employers or provide a password after contact. Check the link from a private browser before applying.

Use the profile to anchor the CV. Mention your years of experience if useful, but do not rely on time alone. The best profiles combine context, methods, and outcomes.

Examples:

• “UX designer with four years of experience improving onboarding, account setup, and self-service journeys for SaaS products. Strong in user interviews, wireframing, usability testing, Figma prototyping, and cross-functional handover.”
• “Junior UX designer with portfolio projects in service redesign, accessibility review, and mobile booking flows. Confident in research planning, interview notes, low-fidelity prototypes, and iterating designs from user feedback.”
• “Senior UX designer with experience leading discovery, research synthesis, interaction design, and design system adoption across complex B2B products. Known for turning ambiguous problems into clear journeys, testable prototypes, and decisions teams can ship.”

Choose the version that reflects your actual level. Avoid profile claims you cannot support later in the CV.

Make the skills section useful by grouping evidence. UX recruiters often scan for research, interaction design, prototyping, accessibility, and collaboration. Product leads may look for metrics, trade-offs, systems thinking, and handover quality. ATS tools may look for specific terms from the advert.

Include a mix of methods, tools, and working strengths. For example: user research, usability testing, journey mapping, information architecture, Figma, prototyping, accessibility, design systems, workshop facilitation, stakeholder management, data-informed design, and design QA.

Do not list every design tool you have opened once. Prioritise tools and methods you can discuss in an interview.

For each role, include your job title, employer, dates, and three to five achievement-led bullets. Start each bullet with a strong verb, but avoid exaggerated language. Useful verbs include researched, mapped, tested, redesigned, simplified, facilitated, prototyped, synthesised, improved, aligned, documented, and handed over.

Good UX bullets often include one of these proof types:

• A user problem you uncovered.
• A design decision you influenced.
• A journey or component you improved.
• A testing or research method you used.
• A measurable outcome or observable improvement.
• A collaboration or handover challenge you solved.

Try to avoid bullets that could apply to any designer. “Worked on digital products” is too broad. “Mapped a high-friction billing journey, tested two prototype options, and helped the team choose a shorter renewal flow” is much clearer.

Use selected projects if they add evidence that the experience section cannot fully show. This is especially useful for junior designers, career changers, freelancers, and candidates whose strongest work sits outside employment.

Each project should include the problem, your contribution, and the result or learning. Keep it short. If the reader wants the full story, they can open your portfolio.

UX roles can come from varied backgrounds: design degrees, psychology, human-computer interaction, digital product work, coding, research, service design, or self-directed portfolio routes. Include education where it supports your candidacy, but do not let it crowd out stronger project evidence.

Certifications can help when they are relevant, such as Google UX Design Certificate, accessibility training, research methods courses, analytics training, service design workshops, or Figma/design-system courses. Add completion dates if they are recent and useful.

Optional sections can work well when they support the job. You might include languages, awards, speaking, mentoring, volunteering, open-source design contributions, accessibility community involvement, or product analytics experience. Keep them brief and avoid hobbies unless they support your design story.

• Planned and ran user interviews for a self-service onboarding journey, identifying three repeated points of confusion that shaped the next prototype.
• Synthesised usability-test findings into a short decision deck, helping product and engineering agree which flow changes should ship first.
• Mapped support-ticket themes against key journey steps, revealing where unclear labels and error states were creating avoidable contact.

• Redesigned a multi-step account setup flow in Figma, reducing repeated form fields and giving users clearer progress feedback.
• Created low-fidelity and high-fidelity prototypes for a mobile booking journey, testing two navigation options before final handover.
• Improved information architecture across a settings area so users could find permissions, billing, and notifications without relying on support.

• Reviewed core journey templates against WCAG 2.2 principles, improving focus states, error messages, contrast, and form labelling before release.
• Ran a testing sprint with users who relied on assistive technology, turning findings into prioritised fixes for the product backlog.
• Worked with engineers to improve keyboard navigation and validation feedback across a high-traffic sign-up flow.

• Facilitated workshops with product, engineering, support, and compliance teams to agree the user problem before solution design started.
• Built annotated Figma handover files with component states, interaction notes, and edge cases, reducing rework during implementation.
• Partnered with analytics and product teams to compare user behaviour before and after a journey redesign.