ATS CV Template for UX Designers — Complete Guide

Lead with a clear header, contact details, and a keyword-rich professional summary that mirrors the job description (ux-designer, UX research, usability testing, Figma, design systems). Your work history should read like a sequence of deliverables: discovery and user research, problem framing, information architecture, wireframes, interactive prototypes, validation, and iteration. For each role, include product context (SaaS/web/mobile), the methods you used, and at least one KPI result such as conversion lift, task success rate, or reduced time-on-task. Keep formatting consistent (standard headings, no tables for ATS-critical content) so the system can reliably extract titles, skills, and achievements using tools like Figma and usability testing terms.

Add a dedicated ‘UX Toolkit’ section that lists tools and methods with proof-ready phrasing: Figma for design and prototyping, Maze for validation or study design, Hotjar for behavioural insights, and Miro for synthesis. Include accessibility explicitly, referencing WCAG 2.1 AA and responsive design. Then add ‘UX Methods’ with examples of what you did—interviews, journey mapping, usability testing, and design system contribution. This gives both ATS and recruiters a fast path to confirming you match the role requirements without guessing.

Rewrite each experience entry using project bullets that include: what you changed, how you validated it, and the measurable outcome. For example, specify that you redesigned onboarding in Figma, ran moderated usability tests (e.g., 20–35 participants), and then iterated the prototype based on observed friction points. Quantify results with product KPIs such as task success rate, drop-off reduction, improved completion time, or Net Promoter Score (NPS) movement where available. If you used Maze, reference the study goal (e.g., prototype validation or funnel experiment) rather than only saying ‘ran tests’.

Show stakeholder and engineering collaboration directly in your bullets. Mention design system contributions (e.g., component updates, tokens, accessibility fixes) and how you worked with developers on handover, specs, and constraints. Where possible, tie your accessibility work to outcomes—such as improving screen-reader flow or increasing WCAG conformance—rather than listing WCAG as a standalone skill. This approach typically improves recruiter confidence because it answers the hidden question: ‘What exactly did you do, and what changed in the product?’

Include at least one section or set of bullets dedicated to design systems, because many UX jobs expect you to scale UX decisions across multiple teams. Describe your contribution in operational terms: creating or updating components in a Figma library, maintaining usage guidelines, aligning with developers on implementation, and ensuring consistency across responsive breakpoints. Reference specific accessibility work such as applying WCAG 2.1 AA requirements to colour contrast, focus states, keyboard navigation, and form error messaging. If you’ve used structured audits or checklists, name them and connect them to a KPI—for example, reducing user errors or improving task success for accessibility-critical flows.

Make your accessibility story measurable and test-backed. Mention how you validated improvements using usability testing protocols and, where relevant, assistive technology checks (screen readers) as part of your review process. You can also cite tools you used to support accessibility workflows, such as Figma’s inspection features or collaboration with QA teams. The key is to show that accessibility is integrated into your process—not tacked on after design is approved.

Match your CV ‘skills’ language to how UX roles are described in job adverts, but keep it human and evidence-based. Instead of listing generic terms, tie them to deliverables: user research leading to personas and journey maps, wireframing leading to stakeholder alignment, and prototyping leading to testable hypotheses. Tools should appear where they make sense (e.g., Figma for interactive prototypes, Maze for validation setup, Hotjar for session insights, Miro for synthesis). Use consistent phrasing such as ‘conducted usability testing’ or ‘built clickable prototypes in Figma’ to avoid ATS flagging your CV as keyword-stuffed.

If you have experience with metrics tracking or experimentation, include it carefully. Reference common product measurement concepts such as task success rate, conversion rate, retention, time-on-task, or SUS scores to show how you evaluate design decisions. For roles in B2B SaaS or marketplaces, include relevant context like onboarding, billing flows, dashboards, or information architecture for complex workflows. This makes your skills section feel grounded in real projects, which improves both ATS relevance and recruiter trust.