UX CVs work alongside a portfolio, so the CV should signal impact and process: research, iteration, and the business result. Link the portfolio and quantify the wins.
Build my UX Designer CV β free βtailored to the job Β· 2 min βLast updated: 27 June 2026
A UX CV works in tandem with a portfolio, so its job is different: the portfolio shows the craft, while the CV signals impact, process and seniority in seconds. Reviewers look for the outcome your design produced and the process you ran to get there β research, iteration, testing, handoff β not just a list of tools. The single most important thing many UX CVs forget is a working portfolio link; without it the CV can't do its job.
Applicant-tracking systems rank on relevance β weave the ones that genuinely apply to you into your experience:
Strong bullets lead with a verb and end with a number. Templates to adapt to your own results:
letsapply.now turns your real experience into bullets like these β quantified and tailored, never fabricated.
The structure a ux designer CV is scanned for β roughly in this order:
What weakens a ux designer CV most often:
A summary sits at the very top and frames everything below. Here's an editable template for a ux designer β adapt every detail to your own experience:
Product designer (5 yrs) who pairs user research with measurable outcomes β redesigned core flows that lifted completion double digits. (Adapt the specialism, methods and results to your own work, and link your portfolio.)
letsapply.now writes yours from your real profile β mirroring the job, never inventing a claim.
Yes β they do different jobs. The portfolio proves the craft; the CV lets a recruiter scan your seniority, process and impact in seconds and decide to open the portfolio at all. Link them tightly, and make the link impossible to miss.
Tie designs to outcomes: task-completion rate, conversion, support tickets reduced, time-on-task. "Redesigned onboarding after 20 usability sessions, lifting completion 33%" shows both the process and the result.
Briefly, as context β but tools aren't skills. A reviewer cares more that you ran research and shipped a measurable improvement than which app you drew it in. Lead with process and outcomes.