Senior UX Designer, Design Systems Architect

Ryan; Austin (TX); Hybrid; USD 110,000 - 180,000; Full time

Benefits offered by this job

Unlimited PTO

401(k) match

Growth opportunities

Job summary

Ryan, LLC, a global leader in tax services and technology solutions, seeks a Senior UX Designer, Design Systems to own and evolve the design system powering our digital tax products.

You will ensure components remain sharp, patterns consistent, and the system scalable as products evolve. This craft-first role demands meticulous attention to token naming, component behavior, and documentation clarity.

Qualifications

• 5–8 years of product/UX design experience, with meaningful time owning or significantly contributing to an enterprise-level design system
• Proven track record of building, maintaining, and scaling component libraries used by multiple products
• Financial, enterprise, or B2B background is a plus
• Demonstrated ability with AI tools and processes that accelerate design and research (e.g., Claude, Figma Make, Lovable etc)

Responsibilities

• Design, build, and maintain a library of reusable components in Figma that are well-structured, thoroughly documented, and ready for both designers and developers to use
• Own our token and variable architecture in Figma, keeping it clean, scalable, and synchronized with what engineering is implementing in code
• Write and maintain clear, practical documentation for components and patterns, covering usage guidelines, do’s and don’ts, and implementation notes that engineers can actually build from
• Bake accessibility into the system from the ground up making compliance the default rather than an afterthought

Skills

UX design

Design systems

Tools

Figma

HTML/CSS

Job description

Ryan, LLC, a global leader in tax services and technology solutions, seeks a Senior UX Designer, Design Systems to own and evolve the design system powering our digital tax products.

You will ensure components remain sharp, patterns consistent, and the system scalable as products evolve. This craft-first role demands meticulous attention to token naming, component behavior, and documentation clarity.