Senior Figma Design System Specialist

Role Overview

• Audit Figma workspace files and map the shared library dependencies, component references, and token connections across Patterns, Recipes, Templates, and working files.
• Lead the duplication and restructuring of the Foundations library into a brand-specific version—stripping non-applicable assets while maintaining component naming integrity.
• Execute Figma’s Swap Library feature across the full file set to reconnect components after the Foundations library is re-homed in the new account.
• Identify and manually resolve any components that cannot be automatically matched during the swap—including renamed, deleted, or structurally changed assets.
• Validate the published state of all Patterns, Recipes, and Template libraries post-migration to ensure all downstream files are receiving updates correctly.
• Document all library decisions, known gaps, and structural changes for the ongoing design team.
• Set up Token Studio in the new Figma account and connect it to a brand-specific token set.
• Validate that all token connections are intact post-migration—colors, typography, spacing, and component-level tokens.
• Identify and resolve broken or mismatched token references across migrated files.
• Ensure the token architecture supports an independent design system going forward.
• Run a proof of concept test early in the engagement: duplicate a low-lift team, transfer it to a test workspace within a provided sandbox, and repeat for a library file documenting findings before full migration begins.
• Coordinate with org admins on the team-level transfer to the new Enterprise account.
• Work through the migration in a sequenced order that minimizes disruption to active design work.
• QA the full migrated environment before handoff confirming no broken references, missing libraries, or disconnected tokens remain.

Requirements

• Expert-level Figma proficiency: You know the platform deeply, including how files, libraries, components, variants, and publishing workflows interact.
• Hands-on library management: Experience managing or rebuilding Figma shared libraries. You understand how library changes propagate and what breaks when they don’t.
• Design Token architecture: Strong working knowledge of design token architecture—how tokens are structured, how they map to Figma variables and styles, and how to validate connections.
• Figma Swap Library: Direct experience using Figma’s Swap Library feature in a real-world enterprise context, not just experimenting with it.
• System Auditing: Ability to audit large, complex Figma file systems and identify structural dependencies without being told where to look.
• Detail-oriented & Methodical: Comfort doing high-volume, precise reconnection work where mistakes have severe downstream consequences.
• Self-sufficient: You can take an ambiguous brief and run with it day-to-day without needing constant direction.