Design and maintain Lux components, tokens, and patterns. Own the work end to end, from Figma library to production usage.
Keep the Figma library clean as it grows. Variants, auto-layout, tokens, responsive primitives.
Design to the Lux token architecture across color, typography, spacing, radius, and motion. Maintain the density-with-dignity rhythm that keeps enterprise UIs usable without feeling cramped.
Partner with engineering on component library so design intent survives the handoff.
Own documentation in zeroheight. Components, patterns, accessibility notes, contribution rules. If teams can't find it, they won't use it.
Work in AI-native design workflows where components move between Figma and code, and production code flows back to validate the system.
Contribute to prompt and pattern libraries that make AI-assisted design produce system-compliant output by default.
Set up governance that scales. Contribution models, reviews, versioning, deprecation. Generation is cheap now. Governance is the differentiator.
Support adoption across product teams. Unblock designers, partner with PMs, help developers ship with confidence.
Use telemetry and component usage data to decide what to build next, what to deprecate, and where the system is leaking.
What You Bring
3-5 years of product design experience, with at least 2 years focused on design systems.
Strong UI craft and a portfolio demonstrating scalable component and pattern design.
Deep expertise in Figma design systems: components, tokens, variants, libraries, and DS operations.
Strong understanding of design tokens and how they translate into cross-platform implementation.
What Could Set You Apart
Strong systems craft and Figma depth are the floor. What separates candidates is how you think about design systems when AI is a first-class consumer of your work.
You've led or contributed to a design system migration from one technical foundation to another without breaking adoption mid-flight.
You've done deep work in enterprise UI: dense tables, long workflows, role-based interfaces, the unglamorous patterns that make business software actually usable.
You've used tools like Cursor, Claude Code, or Copilot to build working components or validate patterns in code, not just Figma.
You understand how AI agents consume design systems. When an agent generates a screen, your tokens are the vocabulary and your patterns are the grammar. You have a point of view on what that means for the system.
You can articulate the shift from design system as library to design system as protocol. When generation is free, governance, telemetry, and quality are the differentiators.
You test, measure, and iterate based on real adoption rather than theoretical perfection.
About Epicor
We're Proactive, Proud, Partners .
Competitive Pay & Benefits
Health and Wellness: Comprehensive health and wellness benefits designed to support your overall well-being.
Internal Mobility: Opportunities for mentorship, continuing education, and focused career goal setting, with 25% of positions filled internally.
Career Development: Free LinkedIn L
Benefits
Health insurance
Additional Information
Job Description Summary
Lux is Epicor's design system. It's the foundation for every product we ship and the vocabulary AI agents use to generate interfaces on our platform. Figma is the source of truth. Zeroheight is the front door.
We think about Lux as having three audiences: designers working in Figma, developers working in code, and AI agents generating UI at runtime. The system has to work for all three.
This role sits on the Design Infrastructure team. You'll own components, tokens, patterns, and documentation that thousands of designers, developers, and agents depend on every day.
Epicorsoftware · Hyderabad, India