Design Systems Designer
Resume Template

A free Design Systems Designer resume, pre-filled and ready to edit. Replace the highlighted placeholders (components, tokens, foundations, accessibility wins, plus the adoption and parity numbers your system moved) using the side panel on the left, and the resume rewrites itself as you type. Save as PDF when you are done.

Emmanuel Gendre - Former Google Recruiter and Tech Resume Writer

Authored by

Emmanuel Gendre

Tech Resume Writer

Get a Free Design Systems Designer Resume Review

I review personally all resumes within 12 hrs

PDF, DOC, or DOCX • under 5MB

Interactive resume template generator

Interactive Design Systems Designer Resume Template

Edit the side panel. The resume rewrites itself live. Save as PDF when you are done.

Edits update live as you type. Toggle Edit to rewrite paper text directly.

Edit mode is on. Click anywhere on the resume to rewrite text. Side-panel placeholders still update live.

Karim Naseer Senior Design Systems Designer

Vilnius, Lithuania karim.naseer.ds@gmail.com +370 6 555 0147

Profile Summary

  • Senior Design Systems Designer with 9 years of experience shipping consumer marketplace web and native apps at scale across second-hand commerce, mobile shopping, and seller tooling, specializing in component library architecture, design tokens, and design-engineering parity.
  • Hands-on coverage across components (Figma with variables and modes), tokens (Tokens Studio with Style Dictionary), documentation (Zeroheight linked to Figma), engineering parity (Storybook with Chromatic visual regression), and accessibility (axe DevTools with Stark for Figma), credentialed through IAAP CPACC accessibility certification.
  • Deep craft in component architecture with variants, properties, and slots, semantic and reference token modeling with theming, foundations work across type, color, spacing, and motion, and design-engineering parity through Storybook and tokens, applying methods such as contribution model with RFCs and component review and semantic versioning with deprecation policy and changelogs to deliver a shipped system that lifts adoption, parity, and ship velocity for product teams.
  • Engaged collaborator working cross-functionally with Product Design, Engineering, Brand, Accessibility, and Content teams inside a platform team that ships the system as a product to consumer squads, contributing to weekly contribution review, design crits, and roadmap shaping with an ownership-first mindset and clear release notes in Notion and Slack.
  • Mentor who shares technical excellence and fosters a culture of accessible-by-default, token-driven components and a contribution model that scales without breaking adopters through pairing sessions and review coaching, while running the systems guild and weekly office hours for product designers and engineers and publishing widely used component playbooks and migration recipes.

Technical Skills

Components & Figma:
Figma with variables and modes, auto-layout, variants and properties, component slots, interactive components, Figma libraries, Figma Dev Mode, prototyping, multi-file source publishing
Design Tokens & Theming:
Tokens Studio with Style Dictionary, W3C design-tokens format, JSON token pipelines, theming and modes, light and dark, multi-brand surfaces, semantic and reference tokens
Foundations & Visual Language:
typography scales, color systems with contrast pairs, spacing systems, 8-point grid, iconography, elevation and shadow, motion and easing, radius and surface
Documentation & Patterns:
Zeroheight linked to Figma, usage guidelines, do and do-not patterns, interaction patterns, accessibility notes, Notion playbooks, Supernova, Backlight
Accessibility Standards:
axe DevTools with Stark for Figma, WCAG 2.2 AA, keyboard navigation, focus management, ARIA roles and labels, screen-reader behavior, reduced-motion support, high-contrast modes
Design-Engineering Parity:
Storybook with Chromatic visual regression, React with TypeScript, Chromatic visual regression, GitHub PRs and code review, design-token sync, Style Dictionary build, Figma to code parity audits
Governance & Contribution:
contribution model, RFCs and proposals, component review, semantic versioning, deprecation policy, release notes, roadmap planning, adoption metrics, office-hours rota
Collaboration & Enablement:
Product, Engineering, Brand partnership, pairing sessions, design crits, Figma comments, Notion documentation, Linear and Jira tickets, Slack office hours, newsletter and changelog
Credentials & Education:
IAAP CPACC accessibility certification, Interaction Design Foundation certifications, design-system management workshops, Atomic Design framework, Material 3 study, Polaris and Carbon case studies

Education

Vilnius University M.Sc. in Human-Computer Interaction
Vilnius, Lithuania Sep 2013 - Jun 2015

Work Experience

Vinted Senior Design Systems Designer
Vilnius, Lithuania Apr 2021 - Present
  • Owned the Vinted design system shipped to web and native serving 22 product squads across 3 platforms (web, iOS, Android), with 140+ designers and engineers consuming the libraries on a daily basis.
  • Designed and maintained the component library, building auto-layout components with variants, properties, and interactive states, shipping 180 reusable components across web and native, and modeling 1,400 variant and state combinations so squads stop forking the kit.
  • Modeled design tokens and theming through a semantic-over-reference token model piped through Style Dictionary into web and native code, landing 640 tokens for color, type, spacing, radius, motion, and elevation, and shipping 4 brand and theme combinations (light, dark, high-contrast, seasonal) from the same source.
  • Built the foundations and visual language with a unified type scale, color system with verified contrast pairs, and an 8-point spacing system, shipping a 9-step type scale and 38 semantic color roles, replacing the ad-hoc style chaos that lived across teams before.
  • Drove accessibility standards into every component with WCAG 2.2 AA baked into every component with focus rings, ARIA roles, and screen-reader behavior verified in axe, reaching 2.2 AA conformance on all primitives and fixing 74 contrast pairs in the legacy palette across the audit.
  • Held design-engineering parity by making sure Storybook documented every component, Chromatic gated PRs, and the token build kept Figma and code in lockstep, with 320 stories published as living documentation and token drift between Figma and code held under 2% on the quarterly parity audit.
  • Ran governance, adoption, and enablement on a published contribution model with RFCs, component review, semantic versioning, and a deprecation policy, lifting active adoption to 92% of in-flight features, merging 48 community contribution PRs a year, hosting weekly office hours, and pushing ship velocity for product teams up by 2.4x on net-new feature work.
Avast UI Designer
Prague, Czechia Aug 2017 - Mar 2021
  • Wrote the pattern documentation and guidelines, producing usage guidelines, do and do-not examples, and interaction patterns published in Zeroheight, authoring 86 doc pages with 140+ do-and-do-not entries, and running 4 quarterly content reviews to keep the guidance fresh as the kit evolved.
  • Pushed tooling and automation forward by shipping an in-house Figma plugin that swept stale styles and surfaced detached instances, plus a token-export script for Android and iOS engineers, releasing 3 plugins to the design org and saving 36 designer hours per sprint on cleanup and engineer handoff.
  • Owned system strategy and roadmap with a quarterly system roadmap backed by adoption metrics and tied to product-team intake, lifting adoption from 41% to 78% across 11 product teams and defending the system roadmap with the Head of Design on a quarterly review.
  • Ran enablement and training across the org through onboarding tracks, monthly workshops, and a migration buddy program for teams moving off the legacy UI kit, delivering 22 workshops over the role and cutting onboarding cycle time for new designers to 2 weeks end to end.

Done editing? Download as a real, vector PDF. Selectable text, ATS-friendly, US Letter format.

About this template

A Design Systems Designer
Resume Template, by a Tech CV Consultant.

Quick intro: 12 years of recruiting experience, including many years at Google, and I now run a tech CV consultant service for systems folks who live inside Figma libraries, Storybook, and Tokens Studio. Design Systems Designer rewrites come in steady from the design-mature shops where the system is a real product: Atlassian, Shopify (Polaris), Adobe (Spectrum), GitHub (Primer), Salesforce (Lightning), GitLab (Pajamas), Stripe, Asana, Microsoft (Fluent), and IBM (Carbon). So when I tell you what works on a systems CV, it is from screening these resumes on the recruiter side, not from a public Figma community post.

Design Systems Designer is the specialist who treats the system as a product, distinct from three adjacent titles. The UX/UI Designer uses a system to ship a screen. The Product Designer uses a system to ship an outcome. The UX Researcher runs the research. Design Systems Designer owns the components, the tokens, the foundations, the accessibility, the parity between Figma and code, the contribution model, and the adoption roadmap. Recruiters at Atlassian, Shopify, Adobe, GitHub, Salesforce, GitLab, Stripe, Asana, Microsoft, and IBM filter for "Design Systems Designer" or "Design Systems Lead" specifically. A resume that reads like a generalist UI designer quietly loses the screen. Most candidates here opt for the full custom rewrite. We sit with the components you shipped, the tokens you modeled and themed, the foundations you owned, the accessibility you baked in, the parity you held between Figma and Storybook, the contribution model you ran, and the adoption and ship-velocity numbers your system moved. If that is more than you need today and a clean systems-shaped skeleton is the missing piece, this template covers it. ATS-clean, free, no signup. Give it a try.

How it works

How to use this template
to write a Design Systems Designer resume

The structure was written by a former Google recruiter. The placeholders push you to be specific exactly where it matters on a systems CV: the components you shipped, the tokens you modeled, the accessibility you baked in, and the adoption and parity numbers your system moved.

Strong systems bullets do not arrive in one draft. They build in five layers. Layer one names the action. Layers two and three add the tools you used (Figma, Tokens Studio, Style Dictionary, Storybook, Chromatic) and the part of the system they shipped (components, tokens, foundations, docs, accessibility). Layer four calls out the craft (the variant model, the token architecture, the contribution rules, the WCAG bar). Layer five quantifies what shifted: components shipped, tokens modeled, brands themed, WCAG conformance, token drift, adoption rate, contribution PRs, ship velocity. Bullets that complete layer five are the ones a hiring manager actually circles. The framework lives in How to Write Bullet Points for Tech Resumes.

  1. 01 Task What you did
  2. 02 Tools Figma, Tokens Studio, Storybook
  3. 03 Stack Components, tokens, foundations
  4. 04 Method Variant model, governance, WCAG
  5. 05 Metric Quantified impact

This template wires the five layers straight into your bullets so you do not carry the framework in your head. The side panel lines up clean: the tool picks feed layer 2, the part-of-system fields feed layer 3, the craft and governance fields feed layer 4, the count and rate inputs land at layer 5. The sentence skeletons carry layer 1. Why this matters: you only have to drop in real components, real tokens, real WCAG numbers, and real adoption rates. The structure does the rest, and the resume reads at layer 5.

  1. Pick your system stack

    Tap a chip to swap Figma variables for Penpot or native variables, Tokens Studio for Specify or an in-house pipeline, Storybook for Histoire or Ladle, Zeroheight for Supernova or Backlight, axe for Pa11y or Accessibility Insights. Every mention updates at once.

  2. Drop in your numbers

    Components shipped, variants and states, tokens modeled, brands themed, type scale steps, color roles, WCAG conformance, contrast fixes, Storybook stories, token drift, adoption rate, contribution PRs, ship-velocity lift, doc pages, plugins shipped, designer hours saved. No real numbers yet? The defaults pass for a senior systems resume.

  3. Save as PDF

    Click Download. The page generates a real vector PDF with selectable text and clean US Letter formatting. ATS-parsable.

Filled the template? Get a recruiter's eyes on it.

The template gives you a recruiter-vetted skeleton. The next step is making sure your specific components, tokens, accessibility wins, parity audits, and the adoption and ship-velocity numbers your system moved hold up under a 6-second screen.

Free, personally reviewed within 12 hours by a former Google recruiter.

Get a Free Resume Review today

I review personally all resumes within 12 hrs

PDF, DOC, or DOCX · under 5MB

Frequently asked

Your Questions about the Design Systems Designer Resume Template, Answered

Yes, the whole template is free. No signup, no email gate, no premium tier waiting at the end. Open the page, drop in your real component counts, token names, foundations work, accessibility wins, and the adoption or velocity numbers your system moved, hit Download, and you have your PDF.

Yes. The exported PDF is single-column with the section headers ATS systems expect (Profile Summary, Technical Skills, Education, Work Experience). No tables, no icons, no two-column tricks. Workday, Greenhouse, and Lever read it cleanly. Want a sanity check on the export? Run it through our ATS Checker.

Yes. Hit the Edit toggle above the preview, then click into any sentence on the paper and type over it. Side-panel placeholders keep flowing into the resume as you type, and the rest is plain editable copy you can shape to the actual library you ship in Figma, Storybook, Tokens Studio, Style Dictionary, or wherever your source of truth lives.

Click Download. The browser builds the PDF on the spot, with no print dialog, no signup, and no server round-trip. The output is real vector text on US Letter, parsed by ATS systems the same way they read any clean resume export.

Swap the defaults. The template leans Figma with variables and modes for the component side, Tokens Studio piped through Style Dictionary for the token side, Storybook with Chromatic for the engineering side, axe DevTools and Stark for accessibility, and Zeroheight for documentation. Every reference is a placeholder. Use the chips to swap Figma for Penpot, Tokens Studio for Specify or native Figma variables, Style Dictionary for a custom token pipeline, Storybook for Histoire or Ladle, Zeroheight for Supernova or Backlight. If your system leans heavily on the token side, lean on the tokens bullet, the foundations bullet, and the engineering-parity bullet. If it leans heavily on the adoption side, lean on the governance bullet and the strategy bullet in the second job.

The Design Systems Designer template is the dedicated systems specialist resume. It treats the system as a product and names the work directly: reusable components with variants and properties, tokens for color and typography and spacing and motion, theming and multi-brand surfaces, foundations work, pattern guidelines and do-and-do-not docs, WCAG 2.2 accessibility built into the components, Figma to Storybook parity, design-token pipelines via Style Dictionary or Tokens Studio, contribution model and versioning, adoption metrics, office hours, and the roadmap that keeps the system shipping. The UX/UI Designer template covers the craft of designing screens that use a system. The Product Designer template covers framing problems and moving product metrics with design. The UX Researcher template covers the research practice. Pick the Design Systems Designer template if your job title says Design Systems Designer, Design Systems Lead, DS Engineer, or you sit inside a Platform, Foundations, or Design Infrastructure team that ships a Figma library and a code library to the rest of the product org.

No. Systems hiring screens on the library you actually shipped, the tokens you modeled and themed, the foundations you owned, the accessibility you baked in, the parity you held between Figma and code, the contribution model you ran, the adoption you grew, the office hours and enablement you ran, and the roadmap you defended. Layout origin is not on the rubric. What does cost interviews is a resume padded with generic systems talk that never names a component, a token, a brand, a WCAG level, a contribution count, or an adoption number. This one is shaped to prevent that. The skeleton came from a former Google recruiter; the substance is yours.

Why trust this template

Emmanuel Gendre, former Google recruiter and tech resume writer

Emmanuel Gendre

Former Google recruiter · Tech resume writer

I built this Design Systems Designer template from the patterns I saw work, not from generic advice. Below is the data behind every bullet, skills line, and metric placeholder.

  • Experience Hundreds of Design Systems Designer resumes screened across Atlassian, Shopify (Polaris), Adobe (Spectrum), GitHub (Primer), Salesforce (Lightning), GitLab (Pajamas), Stripe, Asana, Microsoft (Fluent), and IBM (Carbon), during my Google recruiter years and at TechieCV. The Profile Summary and Skills sections mirror what survived the 6-second screen on a Head of Design Systems desk.
  • Expertise Bullets modeled on senior offers. The Vinted section is structured the way Senior and Lead Design Systems Designers write their experience when they land design-mature interviews: system scope and ownership, component-library depth, token architecture and theming, foundations work, accessibility standards, design-engineering parity, and the governance and adoption that turn the system into a product people actually use.
  • Trust Stack reflects the 2026 hiring bar. Figma with variables and modes for the component side + Tokens Studio piped through Style Dictionary for the token side + Storybook with Chromatic visual regression for the engineering side + axe DevTools and Stark for accessibility + Zeroheight for documentation + IAAP CPACC certification is what systems hiring managers expect today; suggestion chips cover realistic alternatives (Penpot, native Figma variables, Specify, Histoire, Ladle, Supernova, Backlight, Pa11y, WAVE, IAAP WAS, IDF, Figma Advanced) so you can match your real stack without losing keyword fit.
Read my full story →

More resources

Other Design Systems Designer Resume Resources