Design Systems Designer

We need to separate schedule maybe into its own section. However the schedule sentence is part of that paragraph. Could keep it there, but we also need a Schedule section. The instruction: include a section ONLY when posting has real, specific content for it. We have schedule info, so we can make a Schedule section with that sentence. But we must not duplicate content. If we put schedule sentence in both About the role and Schedule, that's duplication. Better to split: About the role paragraph excludes schedule sentence, and schedule sentence goes to Schedule section. Thus we need to parse: The paragraph about role includes schedule sentence at end. We'll remove that sentence from About the role and put it in Schedule. Let's rewrite About the role without schedule sentence. About the role paragraph: "Genius AI is building technology to help local businesses run themselves. Genius AI products do the admin work that keeps practitioners from the work they love and the people they serve. From GlossGenius to Reception, its products work 24/7 on busywork like booking, marketing, client management, finances, staff and inventory management, and more. Genius AI technology has saved businesses 106M in admin hours, earned them $2.0B in additional revenue, and facilitated more than 624M client touch points. We’re looking for a Senior Design Systems Designer to join our growing design systems team. At this level, you’re not just maintaining the system, you’re driving its vision, raising the bar for craft, and becoming a force multiplier for every designer and engineer at Genius AI. As we scale, invest in AI across our product, and undergo a company-wide rebrand in partnership with Porto Rocha, the design system is more critical than ever. We’re looking for someone who can take real ownership, operate with minimal oversight, influence cross-functional partners, and help shape where design systems goes at Genius AI over the next several years." Now schedule section: "

You must be commutable to our NYC headquarters and will operate in a hybrid environment with 2 days per week in the office (Tuesdays & Thursdays).

" Now Responsibilities section:

Responsibilities

• ... each bullet

Requirements section: maybe combine Requirements and Qualifications? We have "What We’re Looking For" which includes experience, skills, etc. Could label as "Requirements". We'll put all bullets there. Pay section:

Pay

Compensation Range: $170K - $210K

We should not include Benefits section as none. Check for any other boilerplate: At Genius AI, we celebrate our differences... EEO etc. Remove. Now ensure we didn't invent or summarize away detail. Keep all details. Check that we didn't miss any bullet: Let's list all bullets from "What You’ll Do" and "What We’re Looking For". Ensure we captured all. What You’ll Do bullets (10): 1 Own the vision and execution of our design system, defining standards, driving adoption, and evolving the system as the product scales 2 Architect and maintain a robust component library with well-documented, reusable UI components that work seamlessly across mobile and web 3 Lead the development of design tokens, Figma libraries, variables, and naming conventions that support a scalable, consistent visual language 4 Drive the design-to-dev handoff process, partnering closely with engineering to bridge Figma and production and reduce friction in every release 5 Champion accessibility, quality, and craft standards across every component and pattern in the system 6 Own documentation and governance, making the system easy to understand, adopt, and contribute to across the org 7 Play a key role in our company-wide rebrand, ensuring the new visual language is systematized and applied consistently across the product 8 Identify and implement tooling efficiencies, including AI-powered workflows, to improve team velocity and output quality 9 Mentor and collaborate with other designers, raising the craft level of the broader team 10 Influence roadmap and prioritization for the design systems team, bringing a strategic point of view to what gets built and when What We’re Looking For bullets (11?): 1 4+ years of product design experience with significant, hands-on focus on design systems, component libraries