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

• One primary portfolio link in the header (not three competing)

  Recruiters click whichever is closest to the top; multiple links signal you can't pick which work to vouch for.

• Surface ownership named, not 'design philosophy'

  'Owns the team-onboarding flow at Notion' beats 'user-centred designer passionate about delightful experiences.'

• Outcome metric paired with design work (activation, conversion, NPS)

  Deliverables alone don't differentiate; outcomes do. 'Activation lifted 41% → 55%' is the bullet that gets read.

• Partner PM + engineer count named explicitly

  Solo-designer claims are red flags. 'Co-led with the growth PM and a 4-engineer team' signals real product partnership.

• Design-system contribution surfaced (mid+ baseline)

  Storybook + design tokens + a11y framework — the senior signals product design hiring panels weight.

• Research method named through an application, not as a skills list

  'Ran 22 JTBD interviews' beats listing 'jobs-to-be-done' in skills. Method through demonstration is the senior pattern.

1. 1

   Lead with the surface you ship in, not your design philosophy

   Hiring panels triage designer candidates by what they've actually shipped. The first thing they look for is which products you've worked on and which surfaces you've owned. If you own the team-onboarding surface at Notion, that information belongs in the first line of your summary. 'Product designer at Notion; own the team-onboarding flow and the templates surface' is twenty words and tells the panel exactly what to ask about.

   For UX designers, the surface might be a research stream or an IA project: 'UX designer on the platform team; own the IA + research cadence for the merchant dashboard.' For senior product designers, it widens: 'Senior product designer owning the planning surface area across three product teams.'

   Avoid leading with philosophy. 'User-centred designer passionate about creating delightful experiences that solve real human problems' is the resume equivalent of corporate jargon — every designer writes it, and panels skip it. The summary leads with the noun the panel wants to read.

2. 2

   Pair design work with outcomes — yours or your team's

   Design impact is harder to quantify than engineering impact, but hiring panels still expect numbers. The metrics that matter: activation rate, conversion, retention, NPS, adoption, task-completion rate, time-to-value, perceived usability (SUS scores), accessibility conformance.

   The structure that works: [verb] [surface], [partner team], [outcome]. Examples: • Led the design rewrite of the team-onboarding flow with PM + a 4-engineer team; activation (workspace-with-2-members-in-7-days) lifted from 41% to 55%. • Owned the IA + interaction design for the cycle-planning surface; adoption among >20-person teams reached 78% within 6 months. • Designed the dark-mode rollout including the accessibility audit; WCAG AA conformance across all primary surfaces.

   If you can't claim the metric directly (because PM or eng owned the measurement), credit the team: 'the team shipped X, where I owned the design strategy.' Hiring panels respect honest attribution; they distrust inflated solo claims that fall apart in interview.

   For research-heavy designers, the outcome can be a roadmap input rather than a metric. 'Ran 22 jobs-to-be-done interviews; synthesis sourced three of the year's roadmap themes' is a credible UX outcome even without a conversion number.

3. 3

   Name your partner PM and engineer count

   Solo-designer claims are red flags. Design is collaborative; resumes that describe work without naming partners read as either inflated or as work done in isolation (which is itself a yellow flag for product design roles). Name the PM and the engineer count.

   The pattern: [did thing] with [PM title / engineering team size] [resulting in concrete artifact]. Examples: • Co-led the v3 launch with the Senior PM and a 6-engineer team; the design system updates from this work seeded the company's first Storybook docs site. • Partnered with the lead PM on the planning roadmap; the resulting design strategy memo became the template for the next three product-area kickoffs. • Designed the onboarding surface end-to-end with the growth PM; first-week activation rose 14 points after the launch.

   Naming the partner also signals which kind of designer you are. A designer who consistently names PM partners is product-strategic. A designer who consistently names research partners is research-led. A designer who consistently names engineer counts is shipping-focused. Hiring panels read these signals; calibrate to the role you're targeting.

4. 4

   Show research and process — not just deliverables

   Most designer resumes describe deliverables ('shipped a redesign,' 'created mockups for a feature'). Senior designer resumes describe process. 'Ran 14 usability tests on the v2 prototype; the three findings that surfaced reshaped the IA before development started' is the kind of bullet that signals real product design work.

   The research methods to name when relevant: jobs-to-be-done interviews, diary studies, formative usability, summative usability, concept testing, tree testing, card sorting, A/B testing, conjoint analysis, surveys (NPS/CSAT). Name the method and the artifact it informed.

   Examples: • Ran 22 jobs-to-be-done interviews on the enterprise tier prospects; synthesis sourced three of the year's roadmap themes. • Designed the formative usability protocol for the cycle-planning prototype; recruited 18 participants and ran the sessions over 3 weeks. • Built the design-research repository in Dovetail (now 140+ tagged insights); referenced across three product-area roadmap planning cycles.

   If you don't do research, that's fine — many product designers partner with researchers instead. Name the partnership: 'Partnered with the UX researcher on the diary study for the SMB segment; co-authored the synthesis deck.'

5. 5

   Link one primary portfolio — not three competing links

   The single most-overlooked element on a designer resume is the portfolio link. Most candidates link three: a personal site, a Dribbble, and a Behance. Recruiters click whichever is closest to the top; if that one is weak, they don't click the others.

   Link one primary URL in the header. Pick the one that: • Loads fast (under 2 seconds — recruiters give up). • Shows three to five strong case studies, not 25 mediocre ones. • Has process work (research, iteration, before/after) — not just final beauty shots. • Is currently maintained (no 'last updated 2022' timestamps).

   If you have multiple portfolios but only one is current, link only the current one and mention the others in your cover letter if relevant. Don't link a Dribbble that's three years stale just because you have one.

   For UX designers without polished visual work, a Notion page with case-study writeups is fine. The content matters more than the design of the portfolio site itself — many hiring managers prefer well-written case studies on a plain Notion page over a slick portfolio with thin content.

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.

• Activation

  Led the design rewrite of the team-onboarding flow; activation (workspace-with-2-members-in-7-days) lifted from 41% to 55%.

  Why it works: Names the specific surface, the activation metric in plain terms (so the panel can verify the definition), and the 14-point absolute lift. A panel can ask follow-up questions immediately: what hypothesis drove the rewrite, how was the experiment structured, what was the rollback plan.

• Adoption

  Owned the cycle-planning surface end-to-end; adoption among >20-person teams reached 78% within 6 months.

  Why it works: End-to-end ownership signal. Audience segment named (>20-person teams). Time-window detail (6 months) lets the panel grade pace. Adoption is the right metric for a B2B feature, not raw usage.

• Accessibility

  Co-led the dark-mode rollout including accessibility audit; WCAG AA conformance across all primary surfaces.

  Why it works: Accessibility work is undervalued on most designer resumes; this bullet surfaces it credibly. WCAG AA is the specific standard most hiring panels weight. 'Co-led' is precise attribution.

• Research

  Ran 22 jobs-to-be-done interviews on the enterprise tier prospects; synthesis sourced three of the year's roadmap themes.

  Why it works: Names the research method (JTBD), interview count (22), and the artifact (three roadmap themes). Research work tied to roadmap outcomes is the senior signal.

• Design system

  Built the design system documentation site (Storybook + custom MDX); primary reference for 70+ engineers across 14 product surfaces.

  Why it works: Names the artifact (Storybook + MDX docs site), the audience size (70+ engineers), and the breadth (14 surfaces). Design-system work generalises across the team — exactly the signal mid+ designer hiring panels want.

• Self-serve

  Designed the templates surface; four shipped templates (CRM, content calendar, OKRs, hiring pipeline) drove 12% of new-account activations.

  Why it works: Lists the specific templates as keywords. '12% of new-account activations' is the kind of business-metric outcome that pulls a design bullet forward.

• Usability

  Designed the formative usability protocol for the cycle-planning prototype; recruited 18 participants and ran the sessions over 3 weeks.

  Why it works: Process detail — recruitment count, session count, timeframe. Formative usability is a recognisable method that the panel can ask about. Most designers list 'usability testing' without specifying which kind.

• Partnership

  Partnered with the growth PM on the onboarding redesign; first-week activation rose 14 points after launch.

  Why it works: Partner explicitly named (growth PM) and the outcome attributed to the team, not solo. 14-point first-week activation lift is precise enough to be defended in interview.

• Process

  Authored the design-research repository in Dovetail; 140+ tagged insights, referenced across three product-area roadmap cycles.

  Why it works: Naming the tool (Dovetail), the artifact size (140 insights), and the cross-team reach (three roadmap cycles) signals process maturity. Repository work is rarely surfaced but heavily weighted by research-focused hiring panels.

• Launch

  Co-led the v3 launch with the Senior PM and a 6-engineer team; design-system updates from this work seeded the company's first Storybook docs.

  Why it works: Three partners named in one bullet (PM by seniority, engineer count). The 'seeded the design system' detail proves the work generalised beyond the launch.

• Process

  Reduced the design-engineering handoff cycle from 9 days to 3 by introducing component-level acceptance criteria in Figma.

  Why it works: Cycle-time metrics are rare on designer resumes. Before/after (9 → 3 days) plus naming the artifact (component-level acceptance criteria) is concrete and verifiable.

• Mentorship

  Mentored two junior designers through their first independent surface launch; both shipped their primary projects on the original timeline.

  Why it works: Mentorship signal for mid-level. Naming the count (two), the milestone (first independent launch), and the outcome (on original timeline) is verifiable in interview.

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 designer resumes — each one disqualifies candidates faster than weak experience does.

• Mistake

  Opening with design philosophy. 'User-centred designer passionate about creating delightful experiences that solve real human problems.'

  Fix

  Lead with the surface you ship. 'Product designer at Notion; own the team-onboarding flow and the templates surface.' Philosophy is what every designer writes; surface ownership is what differentiates.

• Mistake

  Three competing portfolio links in the header (personal site, Dribbble, Behance).

  Fix

  One primary link, ideally to the strongest case study. Recruiters click whichever is closest to the top; if that one is weak, they don't click the others. Multiple competing links signal you can't decide which to vouch for.

• Mistake

  Tool inventory. 'Skills: Figma, Sketch, Adobe XD, Photoshop, Illustrator, After Effects, Lottie, Rive, Principle, Framer, Webflow, Tailwind, HTML, CSS, JavaScript, Storybook, Zeplin, InVision, Abstract...'

  Fix

  Six to ten tools you've actually shipped work in for at least three months. Twenty-five reads as overreach. List the ones the JD names plus your strongest adjacent tools.

• Mistake

  Solo-designer claims. 'Designed the new onboarding flow' (no partner mentioned).

  Fix

  Name the partner PM and engineer count. 'Co-led the onboarding rewrite with the growth PM and a 4-engineer team.' Solo claims read as either inflated or as work done in isolation.

• Mistake

  Listing deliverables instead of outcomes. 'Created wireframes, mockups, and prototypes for new features.'

  Fix

  Pair each design surface with an outcome. 'Designed the cycle-planning surface; adoption among >20-person teams reached 78% within 6 months.' Deliverables are what every designer produces; outcomes are what gets read.

• Mistake

  Listing every research method without naming an application.

  Fix

  Name one or two methods you've actually used inside an experience bullet. 'Ran 22 jobs-to-be-done interviews on the enterprise tier prospects; synthesis sourced three roadmap themes.' Method lists in the skills section without applications signal you've read about them, not used them.

• Mistake

  Two-page resume with fewer than 8 years of experience.

  Fix

  One page. The portfolio carries the heavy lifting; the resume's job is to get the portfolio opened. A second page rarely earns the read at the recruiter stage.

• Mistake

  Stale portfolio site linked but no longer maintained.

  Fix

  Either update the portfolio before linking it, or use a Notion page with case study writeups instead. A stale portfolio is worse than no link — it actively reduces interview odds because it tells the panel you stopped caring about your own work.

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.