UX designers own the strange irony of hiring: professionals of user-centered thinking who routinely submit resumes designed for themselves rather than for the two users who actually read them. User one is a parser plus a recruiter keyword-searching its output; user two is a design leader deciding in under a minute whether to open your portfolio. The resume that serves both is a boring, parseable document whose bullets carry business outcomes, and the example below is exactly that. Treat your own hiring funnel like a usability problem: your beautiful two-column PDF is failing its first usability test inside an applicant tracking system right now.
The market context should shape your evidence before you write a bullet. UX hiring tightened hard after the 2023-2024 corrections and has stayed selective: fewer generalist openings, more demand for measurable product impact, research rigor, and design-system scale, plus rising expectations that designers work fluently alongside engineers and data. The resumes that clear screens in this market are outcome resumes: conversion moved, task success raised, support contacts cut, adoption grown. "Redesigned the onboarding flow" is an activity; "redesigned onboarding, raising day-7 activation 18% against a holdout" is a hire.
The resume and the portfolio have different jobs, and confusing them costs interviews. The portfolio proves depth: process, judgment, craft, the messy middle. The resume gets the portfolio opened: keywords for the filter, outcomes for the skim, and a plain-text portfolio URL that survives parsing. That means no case-study narration in the resume (nobody reads paragraphs), no visual flourishes that scramble extraction, and no assumption that the reader will click before being convinced the click is worth it. One strong metric per role is what earns the click.
Structure: headline with title and specialty ("UX Designer | Research / B2B SaaS"); a summary with years, domain, and your best measurable outcome; experience with three to five bullets per recent role, each an outcome; a skills section grouped into methods, tools, and collaboration; education and certifications last and brief. Portfolio and LinkedIn URLs in the header in plain text. One page until roughly eight to ten years. Single column, standard headings, PDF, per the format guide; design leaders read hundreds of resumes and reward the ones that respect their time.
Write outcome bullets in the language the business tracks. The metrics that make UX bullets land: conversion and activation rates, task success and time-on-task from usability testing, support-ticket and error-rate reductions, adoption of shipped features, retention movement, and accessibility compliance reached. The shape: what you designed, the method behind it in a parenthetical, and the number that moved. "Redesigned checkout after 12 moderated usability sessions surfaced address-entry failures; completed purchases rose 9%" shows method and impact in one line. When A/B or analytics numbers do not exist, usability-testing deltas and qualitative-to-quantitative chains still count. Our quantifying guide covers reconstructing them honestly.
Make research evidence specific, because 'user-centered' is claimed by everyone. Hiring managers discount the vocabulary (personas, empathy, human-centered) because every resume carries it; they trust counts and consequences: "ran 40+ moderated sessions and 6 unmoderated studies across two years", "built the continuous-discovery cadence (5 customer conversations weekly) the product trio still runs", "killed a roadmapped feature by testing a prototype with 8 target users before a sprint was spent." That last shape, research that changed a decision, is the strongest research bullet available, because it proves influence rather than activity. If you are a designer who leans on researchers, say what you ran versus consumed honestly; design leaders can tell anyway.
Show systems and scale, not just screens. Design-system work, accessibility programs, and cross-platform coherence are where UX seniority reads on paper: "built 40 components of the design system (tokens, documentation, Figma libraries) adopted by 3 product teams, cutting design-to-dev handoff defects 50%" or "led the WCAG 2.2 AA effort across the account surfaces, clearing the audit that two enterprise deals required." Even at mid-level, one systems bullet signals you think beyond individual flows. Collaboration texture belongs here too: pairing with engineers in the code review of interaction details, working with data science on experiment design, co-writing product specs. Those bullets answer the question modern design orgs actually ask: can this person operate inside a product team, or only beside one?
Prune the tools list and let methods lead. Figma is assumed the way keyboards are assumed; listing eight design tools reads junior. The skills section that works: methods first (usability testing, journey mapping, information architecture, prototyping fidelity range, experiment design), tools second and short (Figma, FigJam, Maze or UserTesting, analytics you actually read: Amplitude, Fullstory), and collaboration third (design systems, accessibility standards, agile rituals you genuinely participate in). AI design tooling is worth one honest line if you use it in real workflows (rapid concepting, copy variants, research synthesis) because postings have started asking, but a bullet showing judgment about where AI output ends and craft begins is stronger than a list entry. The pruning logic is in the skills section guide.
Keep education, certifications, and the bootcamp question in proportion. Degrees in HCI, design, or psychology earn their line; unrelated degrees need no apology. Bootcamp certificates (General Assembly, Springboard and kin) list once without decoration; in a tight market they do not carry a candidacy, so the portfolio and any real shipped work must. The certificate with growing screen value is accessibility (IAAP CPACC or WAS), because compliance pressure made it a posting keyword. NN/g certificates read as commitment to craft and are harmless-to-mildly-positive. What reads badly: a certificate wall standing in for outcomes, or "UX certified" phrasing anywhere. Evidence first, credentials as footnotes.
The recurring UX resume failures: the designed resume that fails parsing (two columns, icon-fonts, portfolio-style layouts); process-narration bullets ("conducted stakeholder interviews, created wireframes, iterated on feedback") that describe every UX job ever; zero numbers anywhere; "passion for user experience" and other empathy adjectives standing where outcomes should; a portfolio link buried, broken, or password-noted incorrectly; and title soup (UX/UI/product designer all at once) that matches no search cleanly. Every one is fixable in an evening, and collectively they decide most screens. The broader checklist is in the common mistakes guide.
Tailoring UX applications means matching the org's design maturity and vocabulary. Product-led companies want experiment and metric fluency first; enterprise and regulated companies reward accessibility, research rigor, and stakeholder navigation; agencies want range and velocity; early startups want end-to-end scrappiness and shipping speed. Mirror the posting's title exactly in your headline ("Product Designer" and "UX Designer" are separate search strings; carry the one they use, and the other once in the body), and reorder bullets so their loudest need is answered first. The ten-minute mechanics are in the tailoring guide.
The 2026 context: AI tooling now produces competent wireframes, first-pass flows, and interface copy, which has commoditized exactly the production layer that padded junior UX portfolios and raised the premium on what it cannot do: problem framing, research judgment, taste under constraints, accessibility depth, and the influence to change what gets built. Design leaders are explicit about this shift, and resumes that lead with decision-changing research and measured outcomes are answering it. The example below renders with our real template engine; the "Use this example" button opens it in the builder so you can replace Maya's history with yours, and the ATS extract at the bottom shows exactly what a parser keeps from this layout.
Domande frequenti
- UX designer vs product designer vs UI designer: which title should my resume use?
- Mirror the posting, because these are search strings before they are identities, and the market has largely converged on "product designer" for end-to-end product work while "UX designer" persists at enterprises, agencies, and research-leaning roles. The practical mechanics: put the target posting's exact title in your headline ("Product Designer | B2B SaaS"), include the alternate string once somewhere natural in the body, and keep your official past titles as recorded, since background checks verify them. The distinctions that matter underneath: "product designer" postings expect ownership across the problem (research through shipped outcomes, metric fluency, experiment participation); "UX designer" postings range wider, from identical-to-product-designer to research-heavy or flow-focused roles; "UI designer" is now a narrower visual-craft market (design systems, marketing surfaces, brand-heavy products) and worth targeting only if visual craft is genuinely your edge. The compound "UX/UI designer" is worth avoiding in your headline: it reads as bootcamp phrasing to senior screens and matches searches worse than either term alone. If your history mixes titles, unify the story in the summary rather than the title line: "designer with 6 years across research-led UX and end-to-end product work" covers the range without keyword mush. And whichever title you carry, the evidence requirements are converging anyway: outcomes, research that changed decisions, and systems contributions read as seniority under every label the market currently uses.
- What belongs on the resume vs in my portfolio, and how do they work together?
- The resume gets the portfolio opened; the portfolio gets the interview; confusing the two jobs weakens both. The resume's share: titles, scope, and outcome bullets with numbers, keyword coverage for the filter, and a plain-text portfolio URL. It should contain zero process narration (no "conducted interviews, synthesized insights, iterated on wireframes": that describes every UX job ever performed) and zero case-study storytelling, because nobody reads paragraphs in a screen and every line of narration displaces an outcome that would have earned the click. The portfolio's share: three to five case studies that show judgment, not just artifacts: the problem and constraints, what you tried and discarded, the research that changed direction, the shipped result and its numbers, and one honest reflection on what you would do differently. Design leaders consistently say they read for decision-making quality and skim the deliverables. The connective tissue most candidates miss: consistency between the two. Every big claim on the resume should be findable in the portfolio within two clicks (the 24% onboarding lift on the resume should be a case study, not a mystery), and the portfolio's headline projects should match the specialization your resume claims, because a research-forward resume pointing at a visual-showcase portfolio reads as misdirection. Practical hygiene that decides real screens: the link works logged-out, the password (if any) is in the resume line, it loads fast on a phone, and NDA work is handled with sanitized case studies rather than "available on request", which usually converts to "never seen". Check all of it the week you apply.
- How do I quantify design work when I was never given metrics?
- Chase the numbers backward through the people who had them, and where none exist, generate defensible ones from research, because "design is unmeasurable" is almost never literally true. First, the retroactive hunt: the PM you shipped with has (or can pull) before-and-after analytics for your features; support leads can tell you whether contact volume moved after your redesign; sales engineers know which deals cited the accessibility work. A short message to a former colleague ("did activation move after the onboarding rebuild we shipped in March?") recovers more resume metrics than most designers expect, and the numbers are as honestly yours as the PM's. Second, research-native measurement you control: usability-testing deltas (task success 55% to 90% across iterations), comprehension scores on concept tests, System Usability Scale movements, time-on-task changes; these are legitimate quantified outcomes, and framing them as such ("in moderated testing") keeps them honest. Third, proxy shapes when both fail: adoption counts ("used by 800 sales teams"), scale of the surface ("12K partners/year"), and efficiency outcomes ("handoff defect rounds from 3 to 1"). What keeps all of this defensible in interviews: know the derivation of every number you print, prefer ranges and "roughly" over false precision, and never claim causation an A/B test did not establish ("conversion rose 9% after the redesign" is honest; "my redesign caused 9%" invites a fight you do not need). Going forward, instrument by habit: agree success metrics with your PM at kickoff, screenshot dashboards at ship-plus-30-days, and keep a wins file. Six months of that habit permanently ends this problem, and our quantifying guide covers the reconstruction method in detail.
- Is a UX bootcamp certificate enough to get hired in this market, and how should I present it?
- On its own, no longer, and presenting it as the centerpiece actively hurts; presented as one line under evidence of real work, it is fine. The market shifted: the 2021-era pipeline that hired certificate-plus-capstone juniors contracted hard, entry-level UX postings now draw hundreds of applicants, and screeners have seen so many identical bootcamp capstones (the meditation app, the pet-adoption redesign, the local-business concept) that the format itself reads as inexperience. What actually carries career-changers now is real work with real constraints: a nonprofit or small business that shipped your design and will say so, a redesign for your current employer (whatever your title), freelance projects with live URLs and outcomes, or deep contribution to an open-source product's UX. One shipped project with a user-tested iteration loop and a number attached outweighs three speculative capstones, because it proves the thing certificates cannot: you can design under constraints someone else set. Present the certificate in one line in education, uncaptioned; put your prior career to work rather than hiding it (support, teaching, marketing, and operations backgrounds all carry user-facing evidence that pure design graduates lack, and the career change guide covers that reframing); and target the openings where career-changers actually land: smaller companies, agencies, contract roles, and industries connected to your prior domain, rather than the big-tech junior postings with thousand-deep applicant pools. In interviews, the winning posture is craft-forward honesty: here is what I have shipped, here is what I have not done yet, here is how fast I closed the last gap. Design leaders hire trajectory when they see evidence of it.
- How should I handle AI design tools on my resume: threat, skill, or neither?
- As a workflow competence with judgment attached, in one bullet or line, never as an identity and never omitted defensively. The market reality: AI tooling now produces competent wireframes, flow drafts, interface copy, and research synthesis, which commoditized production output and raised the premium on what design leaders were already trying to hire: problem framing, research judgment, taste, accessibility depth, and influence over what gets built. Your resume should respond on both sides. Lead with the layers AI cannot do (decision-changing research, measured outcomes, systems work, facilitation), because that is the value argument; then show honest tool fluency where it produced real leverage: "cut concept-exploration time in half using AI generation for divergent options, curating and testing the survivors with users" or "used AI synthesis on 60 support transcripts to seed interview guides, validating themes in 12 live sessions." The shape that works pairs the tool with the human judgment applied on top: generate-then-curate, synthesize-then-validate. What reads badly: an "AI tools" list entry with nothing behind it (as informative as listing "internet"), claims of AI-driven process with no craft evidence underneath, and, at the other pole, a resume and interview posture of refusal, which design leaders now read the way "I do not use Figma" was read five years ago. Expect the interview question directly ("how do you use AI in your workflow?") and prepare the two-part answer: where you extract speed from it, and where you do not trust it (accessibility, edge-state design, anything user-facing that has not been tested with users). That answer, delivered specifically, converts the threat framing into exactly the judgment evidence this market pays for.
- How many case studies and roles should the resume show, and what do I cut as I get more senior?
- The resume shows roles and outcomes, not case studies (those live in the portfolio, three to five strong ones), and the seniority rule is the standard one sharpened for design: one page to roughly ten years, current role carrying four or five outcome bullets, previous role two or three, everything older compressed to a line, and the whole document pruned so each bullet earns space with a number or a scale fact. What designers specifically over-keep as they grow: early-career production work (banner-era artifacts, marketing-site tickets) that dilutes a product-design narrative; tool lists that accumulate rather than prune (eight tools reads junior; five reads deliberate); duplicate evidence (three redesign bullets proving the same skill, where one redesign plus one research-influence plus one systems bullet proves range); and process vocabulary that survived from a bootcamp template. What earns space as you get senior: mentorship and critique leadership ("mentor three designers", "run the weekly critique that raised shipped-quality bar"), practice-building (research cadences, design-system governance, hiring), cross-functional influence (roadmaps redirected, experiment programs co-owned), and the outcome numbers at growing scale. Agency and freelance histories consolidate rather than itemize: one role line with the strongest two or three engagements as bullets, clients described by domain and scale. The two-page exception is real for design leads and above (team scope, program work, and speaking or publication evidence can justify it), but page one must still decide the screen alone. And whatever the length, run the brutal read before sending: if a stranger skimmed only your bullets' final clauses, would they see a list of numbers that moved, or a list of activities performed? The first version gets portfolio clicks; the second gets archived. Full length logic in our resume length guide.