Senior UX Designer, Design System
About Us
with paragraph.The Role
with paragraph.Responsibilities
with- from "How You'll Contribute" bullet points.
Experience
with paragraph from "What We're Looking For".Skills
with paragraph from "Skills" bullet list.Benefits
combine the benefits list: include bullet points from early benefits and perks & culture.Pay
with paragraph containing compensation ranges.Schedule
with paragraph about hybrid work. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, etc. Also remove "The Fine Print" maybe but keep schedule info. Remove "Locations preferred: Dallas, Austin, or Burlington (MA)"? That's location info; maybe we can include as part of schedule? Not required but could be omitted as not a section. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep location info somewhere. Could embed in a paragraph under About Us or maybe a separate section? There's no heading for location; we could add a short paragraph under About Us or maybe under The Role? Better to add a short paragraph after About Us? But we must not create new headings unless content. Could add aunder About Us that includes location? But About Us already has paragraph about company; we could append location info there. However location is not about us but about role. Could add a separate short paragraph under The Role? Might be okay. We also need to include "Hybrid Work Options" as schedule. We must not include duplicated lines. Ensure we capture all bullet points. Let's extract content. First block: "Why Ryan? Hybrid Work OptionsAward-Winning CultureGenerous Personal Time Off (PTO) Benefits14-Weeks of 100% Paid Leave for New Parents (Adoption Included)Monthly Gym Membership Reimbursement OR Gym Equipment ReimbursementBenefits Eligibility Effective Day One401K with Employer MatchTuition Reimbursement After One Year of ServiceFertility Assistance ProgramFour-Week Company-Paid Sabbatical Eligibility After Five Years of Service" Interpret as list: - Hybrid Work Options - Award-Winning Culture - Generous Personal Time Off (PTO) Benefits - 14-Weeks of 100% Paid Leave for New Parents (Adoption Included) - Monthly Gym Membership Reimbursement OR Gym Equipment Reimbursement - Benefits Eligibility Effective Day One - 401K with Employer Match - Tuition Reimbursement After One Year of Service - Fertility Assistance Program - Four-Week Company-Paid Sabbatical Eligibility After Five Years of Service Later "Perks & Culture Unlimited PTO, robust 401(k) match, and comprehensive benefitsGrowth opportunities within a collaborative, forward-thinking UX teamFlexible work environment with ample opportunities for professional development" Add: - Unlimited PTO - robust 401(k) match - comprehensive benefits - Growth opportunities within a collaborative, forward-thinking UX team - Flexible work environment with ample opportunities for professional development Note some overlap with earlier benefits (PTO, 401k). We'll combine unique items. Now "About Us" paragraph: "Ryan, LLC is a global leader in tax services and technology solutions, recognized consistently as one of the Best Places to Work by Fortune and Glassdoor. We help clients unlock capital, enabling growth, investment, and innovation." "The Role" paragraph: "We’re seeking a Senior UX Designer, Design Systems to own and evolve the design system that powers our suite of digital tax products. You’ll be the person who keeps our components sharp, our patterns consistent, and our system scalable as the product grows. This is a craft-first individual contributor role for a designer who obsesses over the details others overlook: token naming, component behavior, documentation clarity, and the kind of systematic thinking that makes a design system usable at scale. You have UX breadth to understand how the system serves the products built on top of it, and technical curiosity to collaborate fluently with the engineers who consume it. *All candidates must include a digital portfolio or link in their application.*" We need to keep the note about portfolio. It's substantive. Now "How You'll Contribute" bullet points: - Influence Be the go-to authority for our design system, setting and maintaining the standard for how components are built, named, documented, and used across the team - Educate and support designers across the team on system usage, contributing to a culture where the design system is understood, trusted, and consistently applied - Identify gaps, inconsistencies, and debt within the system, prioritizing and advocating for improvements that have the highest impact across the product suite - Collaborate Work closely with Engineering to ensure design system components translate accurately into code, maintaining a tight feedback loop between what’s designed and what’s built - Partner with product designers to understand how the system is being used in practice, incorporating real-world feedback into how components and patterns evolve - Engage with Product and Visual Design to ensure new patterns are grounded in real product needs and aligned with our visual standards before they enter the system - Serve as a critical partner in design system governance, bringing the design and craft perspective to all governance discussions - Deliver 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 with confidence - 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 (i.e. you know WCAG, ARIA, contrast ratios, and more) We need to split into
- items. Some lines have missing punctuation; we can keep as is.
Now "Experience What We’re Looking For" paragraph:
"5–8 years of product/UX design experience, with meaningful time spent owning or significantly contributing to a enterprise-level design system used by multiple productsProven track record of building, maintaining, and scaling component libraries that are adopted and trusted by product teamsFinancial, enterprise, or B2B background is a plusDemonstrated ability with AI tools and processes that accelerate design and research (e.g., Claude, Figma Make, Lovable etc)"
We need to separate sentences: maybe combine into paragraph.
Now "Skills" bullet list:
- Portfolio or work samples that demonstrate design system thinking and execution
- Deep Figma expertise in variables, tokens, component properties, auto-layout, and library management
- Solid understanding of how design systems translate into code, with working knowledge of HTML, CSS, and component-based frameworks (React, etc.) being a meaningful plus
- Mindset Detail-obsessed in a way that extends beyond aesthetics: You care about naming conventions, component states, edge cases, and the consistency of things most people never notice
- Thinks in systems: Able to see how a single component decision ripples across an entire product suite, and disciplined enough to make the right call even when the easy one is tempting
- Comfortable sitting at the intersection of design and engineering, able to speak both languages and build trust on both sides
Now "Perks & Culture" we already captured benefits.
Now "Compensation Pay Transparency" list of ranges per state. We need to include that as Pay section. Should we list all? Yes preserve all substantive information. So we will output a paragraph with all ranges.
Now schedule: "To help new team members get off to a strong start, this role will work in a Ryan office three days per week during their first 60 days. After that, it will adapt to a minimum of one day per week based on the needs of the role, team, and individual". Also earlier "Hybrid Work Options" maybe just note.
We'll combine schedule paragraph.
Now location: "Locations preferred: Dallas, Austin, or Burlington (MA)". We'll add as a paragraph maybe under About Us or separate short paragraph. Since no heading, we can add a
after About Us maybe. We must not include boilerplate: "The Fine Print", "Ryan is an Equal Opportunity Employer", etc. Remove those. Now produce HTML fragment. Structure:
About Us
Ryan, LLC is a global leader in tax services and technology solutions, recognized consistently as one of the Best Places to Work by Fortune and Glassdoor. We help clients unlock capital, enabling growth, investment, and innovation. Locations preferred: Dallas, Austin, or Burlington (MA).
The Role
We’re seeking a Senior UX Designer, Design Systems to own and evolve the design system that powers our suite of digital tax products. You’ll be the person who keeps our components sharp, our patterns consistent, and our system scalable as the product grows. This is a craft-first individual contributor role for a designer who obsesses over the details others overlook: token naming, component behavior, documentation clarity, and the kind of systematic thinking that makes a design system usable at scale. You have UX breadth to understand how the system serves the products built on top of it, and technical curiosity to collaborate fluently with the engineers who consume it. *All candidates must include a digital portfolio or link in their application.*
Responsibilities
- Influence Be the go-to authority for our design system, setting and maintaining the standard for how components are built, named, documented, and used across the team
- Educate and support designers across the team on system usage, contributing to a culture where the design system is understood, trusted, and consistently applied
- Identify gaps, inconsistencies, and debt within the system, prioritizing and advocating for improvements that have the highest impact across the product suite
- Collaborate Work closely with Engineering to ensure design system components translate accurately into code, maintaining a tight feedback loop between what’s designed and what’s built
- Partner with product designers to understand how the system is being used in practice, incorporating real-world feedback into how components and patterns evolve
- Engage with Product and Visual Design to ensure new patterns are grounded in real product needs and aligned with our visual standards before they enter the system
- Serve as a critical partner