<p><span style="text-decoration: underline;"><strong>About Us: <br></strong></span>
</p><p data-path-to-node="1">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.</p>
<p data-path-to-node="2">With over 15 years of proven results, we’ve expanded across industries including financial services, pharmaceuticals, aerospace, consumer products, and quick service restaurants.</p>
<p data-path-to-node="3">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.</p>
<p data-path-to-node="3"> </p>
<p data-path-to-node="3"><span style="text-decoration: underline;"><strong>About the Role: </strong></span></p>
<p data-path-to-node="5">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.</p>
<p data-path-to-node="6">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. <strong data-path-to-node="6" data-index-in-node="192">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.</strong></p>
<h3 data-path-to-node="8"> </h3>
<p></p>
<p></p><p><br></p><b>What You'll Do: </b><div>
<ul>
<li>
<p data-path-to-node="10,0,0">Audit Figma workspace files and map the shared library dependencies, component references, and token connections across Patterns, Recipes, Templates, and working files.</p>
</li>
<li>
<p data-path-to-node="10,1,0">Lead the duplication and restructuring of the Foundations library into a brand-specific version—stripping non-applicable assets while maintaining component naming integrity.</p>
</li>
<li>
<p data-path-to-node="10,2,0">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.</p>
</li>
<li>
<p data-path-to-node="10,3,0">Identify and manually resolve any components that cannot be automatically matched during the swap—including renamed, deleted, or structurally changed assets.</p>
</li>
<li>
<p data-path-to-node="10,4,0">Validate the published state of all Patterns, Recipes, and Template libraries post-migration to ensure all downstream files are receiving updates correctly.</p>
</li>
<li>
<p data-path-to-node="10,4,0">Document all library decisions, known gaps, and structural changes for the ongoing design team.</p>
</li>
<li>
<p data-path-to-node="12,0,0">Set up Token Studio in the new Figma account and connect it to a brand-specific token set.</p>
</li>
<li>
<p data-path-to-node="12,1,0">Validate that all token connections are intact post-migration—colors, typography, spacing, and component-level tokens.</p>
</li>
<li>
<p data-path-to-node="12,2,0">Identify and resolve broken or mismatched token references across migrated files.</p>
</li>
<li>
<p data-path-to-node="12,3,0">Ensure the token architecture supports an independent design system going forward.</p>
</li>
<li>
<p data-path-to-node="14,0,0">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.</p>
</li>
<li>
<p data-path-to-node="14,1,0">Coordinate with org admins on the team-level transfer to the new Enterprise account.</p>
</li>
<li>
<p data-path-to-node="14,2,0">Work through the migration in a sequenced order that minimizes disruption to active design work.</p>
</li>
<li>
<p data-path-to-node="14,3,0">QA the full migrated environment before handoff confirming no broken references, missing libraries, or disconnected tokens remain.</p>
</li>
</ul>
</div><p><br></p><b>What You'll Bring: </b><div>
<ul>
<li>
<p data-path-to-node="18,0,0">Expert-level Figma proficiency: You know the platform deeply, including how files, libraries, components, variants, and publishing workflows interact.</p>
</li>
<li>
<p data-path-to-node="18,1,0">Hands-on library management: Experience managing or rebuilding Figma shared libraries. You understand how library changes propagate and what breaks when they don’t.</p>
</li>
<li>
<p data-path-to-node="18,2,0">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.</p>
</li>
<li>
<p data-path-to-node="18,3,0">Figma Swap Library: Direct experience using Figma’s Swap Library feature in a real-world enterprise context, not just experimenting with it.</p>
</li>
<li>
<p data-path-to-node="18,4,0">System Auditing: Ability to audit large, complex Figma file systems and identify structural dependencies without being told where to look.</p>
</li>
<li>
<p data-path-to-node="18,5,0">Detail-oriented & Methodical: Comfort doing high-volume, precise reconnection work where mistakes have severe downstream consequences.</p>
</li>
<li>
<p data-path-to-node="18,6,0">Self-sufficient: You can take an ambiguous brief and run with it day-to-day without needing constant direction.</p>
</li>
</ul>
</div><p><br></p><b>Preferred Skills: </b><div>
<ul>
<li>
<p data-path-to-node="20,0,0">Token Studio experience: Setup, configuration, multi-brand token sets, and direct connection to Figma variables.</p>
</li>
<li>
<p data-path-to-node="20,1,0">Figma Enterprise Tier Administration: Understanding of org settings, team structure, seat management, and library sharing settings.</p>
</li>
<li>
<p data-path-to-node="20,2,0">Migration Playbook Execution: Prior work on a design system migration, brand split, or Figma org transition.</p>
</li>
<li>
<p data-path-to-node="20,3,0">Multi-brand Design Systems: Understanding how a shared foundation gets forked into brand-specific implementations.</p>
</li>
</ul>
</div><p><br></p><b>Bonus Points: </b><div>
<ul>
<li>
<p data-path-to-node="22,0,0">You’ve done this exact task before, moved a Figma environment from one enterprise account to another and <strong data-path-to-node="22,0,0" data-index-in-node="104">know where the bodies are buried</strong>.</p>
</li>
<li>
<p data-path-to-node="22,1,0">Figma plugin knowledge relevant to library management, bulk operations, or token tooling.</p>
</li>
<li>
<p data-path-to-node="22,2,0">Comfortable presenting complex technical findings and architectural decisions to design leadership in plain language.</p>
</li>
</ul>
</div><p><br></p><b>Context & Environment</b><div>
<ul>
<li>
<p data-path-to-node="25,0,0">You’ll work alongside internal design teams who are actively in production throughout the migration.</p>
</li>
<li>
<p data-path-to-node="25,1,0">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.</p>
</li>
<li>
<p data-path-to-node="25,2,0">The migration is highly time-sensitive with external deadlines.</p>
</li>
<li>
<p data-path-to-node="25,3,0">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.</p>
</li>
</ul>
</div><p><br></p><p></p>
<div>$100 - $112 an hour</div>
