Lead with system scope
Put your current design system role first, then make the system’s scope easy to understand: product areas served, teams supported, platforms covered and whether you owned strategy or delivery. Name the design and engineering partners you worked with. Avoid calling a library “enterprise-wide” unless teams across the organization actually used and maintained it.
Show adoption and outcomes
Describe the work and its effect on product teams: components consolidated, duplicate patterns removed, implementation time saved, accessibility issues fixed or teams onboarded. Use numbers you can explain, and identify the timeframe or scope when useful. A component count by itself says little; connect it to usage, maintenance or a product workflow improvement.
Explain accessibility work
State the WCAG version and conformance level you used, such as WCAG 2.2 AA, and name the work you did: keyboard behavior, focus states, contrast, testing or issue remediation. Avoid claiming a system is fully compliant based on an audit of only a few components. Employers may value a clear account of scope, methods and follow-up more than a broad compliance claim.
Make tools and governance visible
List the tools you used in context, such as Figma Variables for tokens or Storybook for component documentation and review. Include portfolio or documentation links if they show your decisions, contribution model and examples of adoption; remove confidential product details. There is no standard license for this role, so leave out unrelated certificates and use space for system work instead.