CompassX·about 16 hours ago
CompassX is a boutique business and technology consulting firm. We help Fortune 500 and high-growth clients deliver their most strategic initiatives, from enterprise transformations to digital and data-driven projects.
With over 15 years of proven results, we’ve expanded across industries including financial services, pharmaceuticals, aerospace, consumer products, and quick service restaurants.
We are honored to be recognized as a three-time winner of Consulting Magazine’s Best Boutique Firms to Work For, and previously recognized as a “Best Place to Work” in Southern California and one of INC.’s 5000 fastest-growing private companies in the U.S.
About the Role:
Our client is executing a complex, enterprise-level Figma design system migration, moving a massive, interconnected ecosystem from one enterprise account to another. The work involves shared libraries, component hierarchies, and a token architecture managed through Token Studio.
We are looking for a Sr. Figma Design System Specialist with deep design systems expertise to lead this effort. You will be embedded with our design team, working hands-on through every phase of the migration. This is not a generalist design role, we need someone who lives in the technical side of Figma and understands how shared libraries, components, tokens, and publishing workflows fit together at scale.
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.
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.
Token Studio experience: Setup, configuration, multi-brand token sets, and direct connection to Figma variables.
Figma Enterprise Tier Administration: Understanding of org settings, team structure, seat management, and library sharing settings.
Migration Playbook Execution: Prior work on a design system migration, brand split, or Figma org transition.
Multi-brand Design Systems: Understanding how a shared foundation gets forked into brand-specific implementations.
You’ve done this exact task before, moved a Figma environment from one enterprise account to another and know where the bodies are buried.
Figma plugin knowledge relevant to library management, bulk operations, or token tooling.
Comfortable presenting complex technical findings and architectural decisions to design leadership in plain language.
You’ll work alongside internal design teams who are actively in production throughout the migration.
Two additional Technical Figma Designers will join the engagement in month one and carry execution work through month three. You’ll help orient them and keep the work sequenced.
The migration is highly time-sensitive with external deadlines.
This is not a role where you’ll be told exactly what to do. We need someone who can assess the environment, identify the right approach, and execute with absolute precision.