The specific signals an experienced ux designer hiring panel grades on during the eight-second scan.

• Surface owned + research methodology in the summary

  'Owns the merchant-onboarding flow + the team's research repository' beats 'UX designer.' Surface + methodology is what panels scan for.

• Usability metrics quantified

  Task completion rate, time-on-task, SUS score, error rate. Generic 'improved usability' parses as junior.

• Research methods named

  Generative interviews, usability testing, contextual inquiry, JTBD, service blueprints. Methodology breadth signals depth.

• Cross-functional partner count

  PM + engineering + research + data partner counts. UX is collaboration-heavy.

• Portfolio link in the header

  Portfolio is the single most important UX artifact. Must include 3-5 deep case studies.

• Outcomes (business + user)

  Conversion lift, task completion lift, support-ticket reduction. UX is graded on outcomes, not artifacts.

1. 1

   Open with surface + research scope

   Senior UX: 'Senior UX designer; owns the merchant-onboarding flow + the team's research repository (38 studies cataloged).' Mid: 'UX designer on the dashboard team; owns the data-visualization surface + the analyst-persona research stream.' Entry: 'Recent HCI grad; shipped 3 deep case studies on a portfolio (campus food-delivery app, library-finding tool, study-group coordinator) with 1,200+ user testing participants combined.'

   Surface + research scope is the first scan.

2. 2

   Quantify usability + business metrics with sample size

   Task completion rate, time-on-task, error rate, SUS score, completion funnel pass-rate. Pair every metric with sample size + statistical significance where applicable. 'Task completion 62%→84% (n=4,200, p<0.01)' is the gold-standard UX bullet.

3. 3

   Name research methods precisely

   Generative interviews (JTBD framework, n=18). Usability testing (Maze-based, n=120). Contextual inquiry (field study, n=8 customer sites). Service blueprint workshop with cross-functional stakeholders. Tree-test with n=80. Heuristic eval against Nielsen's 10.

4. 4

   Surface cross-functional partnership

   PM + engineering + research + data + content design partner counts. UX is collaboration-heavy; partner-count + cadence (weekly critique, sprint reviews, design-PM 1:1s) signals fluency in product-team rhythm.

5. 5

   Close with portfolio + case studies + community

   Portfolio link in the header is mandatory. 3-5 deep case studies (problem → research → design → outcome) beat 12 shallow ones. Closing signals: design-system pattern contributions, published case studies, conference talks at recognized UX venues.

Each follows the [verb] [object] [number] structure hiring managers grade against. Copy them as a starting point, swap in your own numbers, and read the annotation to understand why each one works.

• Outcomes

  Lifted activation-step task completion from 62% to 84% (post-redesign A/B test, n=4,200, p<0.01); reduced time-on-task from 4.2 min to 1.8 min; SUS score rose from 64 to 81.

  Why it works: Three usability metrics with sample size + statistical significance. Gold-standard UX bullet.

• Research

  Ran 18 generative interviews (JTBD framework) + 14 usability tests (Maze-based, n=120) over 6 weeks; surfaced 3 priority unmet needs that drove the onboarding redesign roadmap.

  Why it works: Interview count, method, test count, sample size, timeframe, strategic outcome.

• Collaboration

  Partnered with 2 PMs + 4 engineers + 1 researcher on the merchant-onboarding rebuild; led 14 design-critique sessions across the project; partnered with data on activation-funnel instrumentation pre-launch.

  Why it works: Partner counts, critique cadence, cross-discipline instrumentation work.

• Design system

  Designed 8 new patterns for the design system (empty-state, error-recovery, multi-step-form, async-loading); each shipped with Figma library + accessibility-annotation overlay; adopted by 4 product teams within 6 months.

  Why it works: Pattern count, specific types, accessibility detail, cross-team adoption.

• Design sprint

  Co-led a 5-day design sprint with 8 cross-functional stakeholders to validate the new pricing-page concept; produced a clickable prototype tested with 24 customers; concept validated for implementation within the sprint.

  Why it works: Sprint duration, stakeholder count, prototype testing, validation outcome.

• Research ops

  Authored the team's research-ops handbook (Dovetail-based) + cataloged 38 prior research studies with searchable insights; reduced time-to-find-relevant-prior-research from 90 min to under 5 min.

  Why it works: Tool (Dovetail), study count, search-time outcome.

• Accessibility

  Ran a WCAG 2.2 AA audit on the merchant dashboard surface (axe + manual screen-reader testing across NVDA + VoiceOver + JAWS); surfaced 28 violations + shipped remediation across 14 flows.

  Why it works: Standard, three screen readers, violation count, remediation scope.

• Metrics

  Built the team's HEART metrics dashboard (Happiness, Engagement, Adoption, Retention, Task Success) per product surface; now drives the quarterly product-review meeting.

  Why it works: Framework named (HEART), implementation scope (per surface), business-process integration.

• Mentorship

  Mentored 2 junior UX designers through their first independent end-to-end projects; both shipped sole-owner features (one onboarding, one settings) with measurable usability outcomes within 6 months.

  Why it works: Mentee count, project independence, deliverable outcomes.

• Community

  Published 3 case studies on Medium + UX Collective (combined 18k reads + 380 highlights); spoke at UX Australia 2024 (35-min talk, 280 in-room).

  Why it works: Publication count + venues + engagement metrics + conference speaking.

• Specialty design

  Owned the data-visualization surface on the analytics dashboard; lifted chart-comprehension rate from 58% to 79% via a chart-type-by-task heuristic (line for trends, bar for compare, scatter for correlation) tested with 24 analysts.

  Why it works: Surface owned, comprehension-rate before/after, design heuristic, user test sample.

• Entry-level

  Built a campus food-delivery app prototype as an HCI capstone (Figma + Maze testing with 280 students); identified 4 critical usability issues + iterated through 3 prototype rounds; final SUS score 84.

  Why it works: For entry candidates, a capstone with user testing + iteration cycles + SUS score is credible.

Same intent, two phrasings. Read why the right column lands on the keep-pile and the wrong column doesn't.

Patterns our writers see most often when reviewing ux designer resumes — each one disqualifies candidates faster than weak experience does.

• Mistake

  Leading with 'passionate about user-centered design.'

  Fix

  Open with the surface owned + research scope. Specific > generic.

• Mistake

  Artifact-volume claims. 'Created 38 wireframes.'

  Fix

  Surface usability outcomes (task completion, time-on-task, SUS) instead. Wireframe count is a weak senior signal.

• Mistake

  Vague research mentions.

  Fix

  Name the method + sample size + finding ('18 generative interviews, JTBD framework, surfaced 3 priority unmet needs').

• Mistake

  Missing portfolio link.

  Fix

  Portfolio in the header is mandatory for UX roles. Link to a portfolio with 3-5 deep case studies.

• Mistake

  Listing every tool you've touched.

  Fix

  Figma + 2-3 research tools (Dovetail, Maze, UserTesting) is enough. Long tool lists read as junior.

• Mistake

  Not surfacing accessibility work.

  Fix

  Accessibility is increasingly load-bearing at sophisticated companies. Surface WCAG audit work where applicable.

• Mistake

  Two-page resume below staff designer level.

  Fix

  One page. UX hiring panels prioritize portfolio review over resume reading.

• Mistake

  Conflating UX with UI / product design.

  Fix

  UX research depth, UI visual depth, product designer (often UX + UI) — these distinctions matter at sophisticated hiring teams. Tilt your resume toward the title in the JD.

Strong verbs lead strong bullets. Replace generic openers (worked on, helped with, was responsible for) with the specific verb that matches what you actually did.

ATS pipelines weight your Skills section as a structured list. Include 15-25 of the items below if they match your experience — not soft skills.