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

• Visual craft specialty in the summary

  'UI designer focused on Figma component libraries + micro-interactions' beats 'UI designer.' Specialty signals craft depth.

• Design-system + token work

  Component count, token system (variables-based in Figma), cross-team adoption. Senior UI designers are graded on system contributions.

• Portfolio with high-craft visual work

  UI portfolio is visual-craft-first. Surface visual sophistication: typography, spacing, micro-interactions, polish.

• Tool fluency precise

  Figma (advanced — Auto Layout, variables, component properties, dev mode). UI hiring screens explicitly.

• Brand-aware design

  Working from established brand systems + extending them. UI designers operate within marketing-set brand identity.

• Engineering handoff fluency

  Figma Dev Mode, design tokens, Storybook coordination. UI is the most engineering-adjacent design role.

1. 1

   Open with visual specialty + system scope

   Senior: 'Senior UI designer; owns the design system component library (60 components, variables-based tokens).' Mid: 'UI designer on the dashboard team; designed 38 components in the team's Figma library.' Entry: 'Recent design-program grad; shipped a portfolio with 20-component Figma library + token system for a fictional fitness app (variables-based, Dev-Mode-ready handoff).'

2. 2

   Quantify component-library scope

   Component count, variant count, family count, token categories (color + spacing + typography + radius + motion), cross-team adoption. The senior UI designer scope signal.

3. 3

   Surface micro-interaction work

   Hover/active/disabled states, focus rings, loading skeletons, empty states, modal open/close motion, async transitions. Name the interaction count + specific pattern types.

4. 4

   Show engineering-handoff fluency

   Figma Dev Mode, design tokens, Storybook coordination, CSS variable system. Senior UI designers ship the handoff — surface engineering partner count + cadence + outcome metrics (design-implementation drift).

5. 5

   Close with portfolio + community

   Portfolio link in header is mandatory. Closing signals: Config talks, published Figma community files, recognized design-system pattern contributions.

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.

• Design system

  Own the design-system component library (60 Figma components, variables-based tokens for color + spacing + typography + radius); designed 38 component variants across 8 component families; system used by 4 product teams + 80+ engineers.

  Why it works: Component count, token categories, variant count, family count, adoption.

• Micro-interactions

  Designed 24 micro-interaction patterns for the design system (button hover/active/disabled, focus rings, loading skeletons, empty states, async success/error transitions, modal open/close motion); each shipped with Figma prototype + Storybook reference + AE export for complex cases.

  Why it works: Interaction count, pattern types, three deliverable types.

• Visual craft

  Owned the dashboard-redesign visual system: refined the type scale from 14 sizes to 8, rebuilt the color palette as a token-based system (12 primitive colors + 38 semantic tokens), tightened spacing to a 4px-base scale; design audit passes rose from 62% to 96% on first review.

  Why it works: Three craft decisions with before/after, audit-pass outcome.

• Engineering handoff

  Partnered weekly with 4 engineers on Dev Mode handoff; co-authored the team's design-token spec (color + spacing + typography + radius + motion) shipped to engineering as a CSS variable system; reduced design-implementation drift incidents from 12/quarter to 1/quarter.

  Why it works: Cadence, partner count, spec authorship, drift outcome.

• Motion + craft

  Built a Lottie animation library for the marketing site (14 illustrations animated in After Effects + exported via Lottie); avg file size 38KB; load-impact on LCP < 50ms.

  Why it works: Tool stack, animation count, file-size budget, performance impact.

• Brand alignment

  Worked from brand-team-set color palette + type system; extended the marketing-only palette into a product-system token set (38 semantic tokens) while preserving brand recognizability per the brand-team review.

  Why it works: Source palette context, extension scope (38 tokens), brand-team review process.

• Figma ops

  Authored the team's Figma file-organization conventions (page structure + component naming + variant ordering); reduced time-to-locate-existing-component from 4 min to 30 sec for new hires.

  Why it works: Convention scope, time-savings outcome for new hires.

• Tooling

  Built the team's design-QA dashboard (Figma plugin + Storybook visual-regression integration); auto-flags spacing / token / color drift between Figma source and production; caught 38 drift incidents pre-merge in Q3-Q4 2024.

  Why it works: Custom tooling, drift-catch outcome, quarterly context.

• Mentorship

  Mentored 2 junior UI designers through their first design-system contributions; both shipped sole-owner components (table + form-field family) within 6 months.

  Why it works: Mentee count, component-family deliverables.

• Community

  Config 2024 — workshop facilitator on 'Variables-based tokens in Figma' (3-hour workshop, 80 attendees); workshop materials open-sourced on Figma Community.

  Why it works: Workshop format, attendance, open-sourced materials.

• Entry-level capstone

  Designed a 20-component Figma library + variables-based token system for a fictional fitness app as a design-program capstone; Dev-Mode-ready handoff documentation; cited in the program's portfolio review.

  Why it works: For entry candidates, a working component library + token system + handoff doc is high-leverage.

• Migration

  Migrated the team's design system from Sketch + manual tokens to Figma + variables-based tokens over 8 weeks; cataloged + redesigned 380 components; reduced cross-team component-divergence incidents from 12/quarter to 1/quarter.

  Why it works: Migration duration, component count, divergence outcome.

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

• Mistake

  Visual portfolio without system thinking.

  Fix

  Senior UI portfolios show component-library work + token systems, not just polished one-off screens.

• Mistake

  Generic 'Figma proficient' tool listing.

  Fix

  Name Auto Layout + variables + component properties + Dev Mode by specific feature. Senior Figma skills are specific.

• Mistake

  No engineering handoff evidence.

  Fix

  UI is the most engineering-adjacent design role. Surface Dev Mode + token + Storybook handoff work.

• Mistake

  Conflating UI with UX or product design.

  Fix

  UI is visual-craft-heavy + design-system focused. Tilt your resume toward the JD title.

• Mistake

  Listing every tool you've touched.

  Fix

  Figma + 1-2 motion tools (AE + Lottie) is enough. Tool-list bloat reads as junior.

• Mistake

  Missing portfolio link.

  Fix

  Portfolio in header is mandatory.

• Mistake

  Two-page resume below staff designer level.

  Fix

  One page until staff UI designer / design-system lead level.

• Mistake

  No micro-interaction work surfaced.

  Fix

  Micro-interactions are UI craft signal. Surface specific patterns shipped.

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.