This guide is for UX Designers, UX/UI Designers and Product Designers applying to roles at any level, from first job to senior. By the end you'll know which keywords to include, how to write a summary and bullets that prove impact, and how to adjust one resume for SaaS, ecommerce, healthcare and government employers.
Keyword match
UX Designer, Billing Platform
6/8must-have skills
Found on your resume
Missing
Jordan Avery
Denver, CO · jordan.avery@email.com · linkedin.com/in/jordanavery · jordanavery.design
1Summary
B2B SaaS UX Designer, 5 years on scheduling and billing tools. Pairs moderated research with Figma prototyping to cut task time and support load.
2Skills
Figma · Usability Testing · User Research · Prototyping · Information Architecture · Design Systems · WCAG 2.2 AA · Journey Mapping · Maze · Amplitude
3Experience
UX Designer Harborline Software · Mar 2022–Present
The portfolio link sits in the header because many hiring managers open it first, so use a short, working URL.
Common mistakesThe first summary line gives domain and years of experience, so the fit is clear right away.
Summary examplesThe skills list uses the terms postings use, which helps ATS matching and a quick human scan.
Keywords and skillsThis bullet names the research method, sample size and a before/after usability number, the evidence pattern hiring managers trust most.
Bullet pointsA recognized UX certification next to a related degree shows structured training without taking up space.
CertificationsEveryone makes wireframes and personas. Managers want to know what changed after your design shipped: task success, conversion, support tickets, activation.
Name the method (interviews, usability tests, tree tests, contextual inquiry), roughly how many participants, and what you changed because of it.
UX work is collaborative, so reviewers look for what you owned. "Led," "owned end to end" and "contributed to" mean different things; use them accurately.
Design systems, built-in accessibility and specs engineers can build from without rework show your designs survive handoff.
The projects in your bullets should be your portfolio case studies, with the same names and numbers.
O*NET, which groups UX work under web and digital interface designers, flags Figma, Jira and Adobe Creative Cloud as in-demand skills in job postings for that occupation.
Soft skills
Don't list "empathetic" or "collaborative." Prove them with a bullet about running a workshop, presenting to a VP or working through engineering constraints.
UX Designer with a Google UX Design Certificate and three years in retail store operations. Designed and tested a curbside-pickup app concept across three rounds with 9 participants, iterating until every participant finished checkout without help. Comfortable working inside an existing design system and annotating specs for developers.
Why it works: It turns a non-design job into domain knowledge and backs up "tested" with a real round count and result.
Product Designer with 6 years in fintech, owning onboarding and identity-verification flows from discovery through launch. Runs both moderated and unmoderated studies, hands off engineering-ready specs in Figma, and tracks results in Amplitude. Most recent KYC redesign lifted completion from 54% to 71%.
Why it works: It states a clear area of ownership, names the full workflow and ends with one specific result.
Senior UX Designer with 10 years leading design for clinical documentation software used by 4,800 providers. Sets design direction across three product squads, governs a 137-component design system, and mentors four designers. Brings exam-room observation into roadmap decisions, most recently cutting average note-completion time by 2.4 minutes.
Why it works: The scope numbers (users, squads, components, direct mentees) make seniority concrete instead of implied.
WeakCreated wireframes and prototypes for the mobile app.
StrongPrototyped a three-step returns flow in Figma and tested it with 8 customers, removing a confirmation screen where 5 of them stalled.
What changed: It names a specific flow, a test and the decision the test led to.
WeakHelped with usability testing.
StrongModerated 11 of 18 usability sessions for the account-settings redesign and synthesized 23 tagged issues in Dovetail, 17 of which shipped as fixes.
What changed: It separates your share of the work from the team's and shows that your findings led to fixes.
WeakResponsible for redesigning checkout.
StrongRedesigned mobile guest checkout, cutting form fields from 14 to 8; cart-to-order conversion rose 6.3% in a four-week A/B test.
What changed: "Responsible for" became an action, and the result cites how it was measured.
WeakImproved the website's accessibility.
StrongAudited the patient portal against WCAG 2.2 AA, logged 64 issues, and redesigned focus states and form errors; automated scan violations fell 71% by the next release.
What changed: It names the standard, the scale of the audit and a result anyone can check.
WeakWorked with developers on handoff.
StrongAnnotated specs in Figma Dev Mode and joined sprint reviews for the invoicing launch, reducing design-related QA bugs from 31 to 9 between releases.
What changed: It shows handoff quality as fewer defects, which engineering managers care about.
WeakMade onboarding better using research.
StrongInterviewed 12 churned workspace admins, then rebuilt setup around their first real task; 30-day activation increased from 38% to 47%.
What changed: It connects the research to the design decision and the decision to a product metric.
WeakLed the design system.
StrongLed a 3-designer, 5-engineer effort that merged 4 legacy UI kits into 112 tokenized components, now used by 9 product teams; average new-screen build time dropped from 6.5 to 4.2 days.
What changed: Team size, cross-team adoption and an efficiency gain show senior scope.
WeakMentored junior designers and managed stakeholders.
StrongStarted biweekly critiques and a research share-out for a 7-person design team; 2 designers were promoted within 18 months, and 3 research-backed initiatives won VP roadmap approval.
What changed: It turns vague leadership claims into results for people and for the roadmap.
The BLS lists no license or certification requirement for digital designers, so your portfolio is the credential that matters most. Education requirements range from a high school diploma to a bachelor's degree. Employers may prefer a bachelor's in web design, digital design or graphic arts, but you may not need specific education credentials if prior work or projects show your ability. Postings also regularly mention degrees in HCI, psychology, interaction design and computer science.
Put a combined "Education & Certifications" section below Experience. Career changers with little UX work history can move it above Experience for their first role.
Listing one in progress
Give the expected date and progress so it can't be mistaken for a completed credential:
NN/g UX Certification — 3 of 5 courses complete (expected June 2027)
IAAP CPACC — exam scheduled March 2027
Two-column layouts, skill-level icons and text inside graphics often break ATS parsing.
FixUse a clean single-column file with real text and standard headings, and save visual craft for your portfolio.
"Created personas, journey maps and wireframes" describes the process, not the impact.
FixKeep one artifact per bullet at most and end with what changed.
Broken links, expired prototype URLs or password pages with no password lose you the read.
FixUse a short custom URL, test it in a private window, and put any password next to the link.
Adobe XD is in maintenance mode with no new features in development, and InVision discontinued its design collaboration services at the end of 2024, so a list led by either suggests stale skills.
FixLead with Figma and your current research and analytics tools, and add older tools only when a posting names them.
"Increased conversion 20%" invites the interview question, "What did you do, and how was it measured?"
FixState your part ("designed the variant that…") and the method (A/B test, before/after over a set period).
Keep it to one page if you have under about eight years of experience, and two pages at most for senior and lead roles. Your portfolio carries the depth; the resume only needs your strongest results and enough context to get reviewers into your case studies.
Clean and well spaced, yes. Heavily stylized, no. Reviewers will notice your typography and hierarchy, but the file still has to pass an ATS (see mistake #1).
If you're entry level or changing careers, yes. Pair it with at least one case study that includes real usability testing, because the certificate alone won't carry an application. Once you have a couple of years of shipped work, move it to the bottom or drop it.
Gaps after tech layoffs are common, and a short explanation is usually enough. If you freelanced, did contract or nonprofit work, or built a new case study during the gap, list it with dates like any other role. Otherwise, cover it in one line of your cover letter.
Match the title in the posting in your header and summary when your work fits it, but never change official job titles in your experience section. If your past title differs from your actual work, a parenthetical works: "UX Designer (Product Design, Payments)."
Agencies hire for range and client skills. Group bullets by client, describing any you can't name by industry ("national grocery chain"). Show that you handled several accounts at once, and include one bullet about presenting to clients or contributing to a new-business pitch.
Paste a job ad and get a fit score, the keywords you're missing and the one thing to fix first.
Start for free