Our direct client is looking for Figma Design Specialist, Remote- USA. Please send me the resume, rate and contact details.
Worker Location: Remote - United States
Job Description: Remote anywhere in US
Flexible hours but 9am CST is general start time
Bill Rate – best rate
About the Role
We are executing a complex Figma design system migration — moving a large, interconnected Figma environment 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 Figma 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.
What You’ll Do
Design Systems & Library Work
• 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
Token & Variable Work
• 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
Migration Execution
• 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 — document 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 — confirm no broken references, missing libraries, or disconnected tokens remain
What You Bring
Required
• Expert-level Figma proficiency — you know the platform deeply, including how files, libraries, components, variants, and publishing workflows interact
• Hands-on experience managing or rebuilding Figma shared libraries — you understand how library changes propagate and what breaks when they don’t
• Strong working knowledge of design token architecture — how tokens are structured, how they map to Figma variables and styles, and how to validate connections
• Experience with Figma’s Swap Library feature — you’ve used it in a real context, not just experimented with it
• Ability to audit large, complex Figma file systems and identify structural dependencies without being told where to look
• Detail-oriented and methodical — comfortable doing high-volume, precise reconnection work where mistakes have downstream consequences
• Self-sufficient day-to-day — you can take a brief and run with it without needing constant direction
Strongly Preferred
• Token Studio experience — setup, configuration, multi-brand token sets, and connection to Figma variables
• Experience with Figma Enterprise tier administration — org settings, team structure, seat management, library sharing settings
• Prior work on a design system migration, brand split, or Figma org transition
• Familiarity with multi-brand design systems — understanding how a shared foundation gets forked into brand-specific implementations
Bonus
• You’ve done this 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 findings and decisions to design leadership in plain language
Context & Environment
• You’ll work alongside internal design teams who are active 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 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 precision