Senior UX Designer, Design System

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. We need to parse the posting. First, there is a header: "Why Ryan? 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" That's benefits list. Then "About Us Ryan, LLC is a global leader..." That's about the company, not role. Could be "About the role"? Actually "About Us" is about company. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role (maybe from "The Role" paragraph). Responsibilities (from "How You’ll Contribute" bullet points). Requirements/Qualifications (maybe from "Experience What We’re Looking For" and "Skills" and "Mindset"). Skills (maybe separate). Benefits (from the benefits list). Pay (from compensation ranges). Schedule (from hybrid work options and office days). Also maybe "Perks & Culture" could be part of Benefits. We must not create sections with filler. So we need to include sections only if there is real specific content. Let's extract content. **About the role**: The paragraph after "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.*" We should keep that as prose in

. The asterisk note about portfolio is part of role description; we keep. **Responsibilities**: The "How You’ll Contribute" section with subheadings Influence, Collaborate, Deliver each with bullet points. We need to combine into a list of duties. Probably each bullet is a responsibility. We'll create

• for each bullet. Let's extract bullet points: Under 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 Under 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 Under 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'll list all these as
• . **Requirements / Qualifications**: The "Experience What We’re Looking For" paragraph plus maybe "Skills" and "Mindset". We need to decide sections: Requirements (maybe experience), Qualifications (maybe skills), Skills (maybe separate). The instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid duplication. Let's map: Experience What We’re Looking For: - 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 products - Proven track record of building, maintaining, and scaling component libraries that are adopted and trusted by product teams - 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) Skills: - 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 We could combine Experience as Requirements, Skills as Skills, Mindset as Qualifications (or vice versa). But we need to avoid filler. All content is substantive. We'll create sections:

  Requirements

  with
  of the experience bullet points.

  Skills

  with
  of skills bullet points.

  Qualifications

  with
  of mindset bullet points. Alternatively, we could merge Skills and Qualifications into one, but instruction says prefer few substantive sections over many thin ones. Having three sections may be okay if each has substantive content. Could also combine Skills and Qualifications into one "Skills & Qualifications". But we have predefined headings list; we can choose to use only those that have content. Using all three is fine. **Benefits**: The list at top: 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, 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. Also "Perks & Culture" includes Unlimited PTO, robust 401(k) match, comprehensive benefits, Growth opportunities..., Flexible work environment... We need to avoid duplication. Let's compile unique benefits: - 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 - Unlimited PTO (note maybe same as Generous PTO? but we keep both? Might be duplicate; but we can keep as separate if distinct. However "Generous Personal Time Off (PTO) Benefits" and "Unlimited PTO" may overlap. We'll keep both as they appear.) - Comprehensive benefits (maybe redundant) - Growth opportunities within a collaborative, forward-thinking UX team - Flexible work environment with ample opportunities for professional development We should avoid filler like "comprehensive benefits" maybe vague but it's stated. It's okay. We'll output as
  • each. **Pay**: The compensation ranges for various states. We need to include that as a section. The posting includes multiple ranges based on location. We should preserve all. Could present as a

    summarizing: "Pay transparency: For certain California based roles, the base salary hiring range is $124,000.00 - $163,020.00; for other California based roles, $114,000.00 - $149,490.00; for Colorado based roles, $109,000.00 - $142,670.00; for Illinois based roles, $114,000.00 - $149,490.00; for other Illinois based roles, $109,000.00 - $142,670.00; for Maryland based roles, $109,000.00 - $142,670.00; for Massachusetts based roles, $114,000.00 - $149,490.00; for other Massachusetts based roles, $109,000.00 - $142,670.00; for New Jersey based roles, $124,000.00 - $163,020.00; for New York based roles, $124,000.00 - $163,020.00; for other New York based roles, $103,000.00 - $135,850.00; for Washington based roles, $114,000.00 - $149,490.00." We'll keep as a

    . **Schedule**: The hybrid work options and office days: "Hybrid Work Options" already in benefits but also schedule specifics: "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 generic. We'll create Schedule section with that prose. We must not include boilerplate like EEO, Equal Opportunity Employer, locations preferred, etc. Also remove "The Fine Print" etc? The Fine Print includes supervisory responsibilities, work primarily computer-based, occasional travel up to 10%, EEO, locations preferred, office days. We already captured office days in Schedule. The rest (supervisory responsibilities, travel, EEO, locations) are boilerplate; we should remove. Also remove "#DICE" at end. Now construct HTML. We'll output:

    About the role

    We’re seeking a Senior UX Designer, Design Systems to own and evolve the design system that powers our