Dir, Product Design

We need to output HTML fragment with sections: About the role? Actually description includes mission statement etc. We need to parse the posting and produce sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections that have real specific content. No filler. No job title heading. No Job ID. Remove boilerplate (EEO etc). Also remove application instructions. We need to preserve all substantive info. Let's extract content: First paragraph: "Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance. Are you a design systems expert with a strategic, consumer-first mindset? Are you looking to be the driving force in creating world-class experiences that help people find and enjoy a home of their own — not just executing a roadmap, but helping shape it? If you want to expand your professional goals at Avail by Realtor.com®, this is the role for you!" That's like an intro; could be "About the role". We'll put that in a

under

About the role

. Next: "This role will immerse themselves in the market and our industry, partnering closely with senior leaders in Product and Engineering to define, create, and execute our bold vision for transforming the real estate industry — not simply implement a strategy set by others. You will be responsible for design decisions and patterns for multiple products and ensuring the adoption thereof by product designers who work in those areas. You’ll also build on the design system foundation by enhancing toolchain connections between design files and code, promoting education and advocacy, and collaborating closely with cross-functional teams across all platforms. A team of designers will report to this role, and you will closely partner with a sibling engineering team. You will also collaborate with cross functional leaders on team capacity and skills. And work with other design leaders to drive the strategy and execution of Design Ops tools and processes to create a more scalable and efficient design practice. This role reports to the Head of Avail." That's responsibilities. We'll put under

Responsibilities

with

• items. Then "What You’ll Do" list: bullet points each starting with bold? Actually they are sentences. We'll treat as responsibilities as well, but they are more detailed. Could combine. Better to treat "What You’ll Do" as responsibilities. Then "How We Work": paragraph about in-person collaboration, four or more days in offices. That's maybe "Work Environment" but not a required heading; we could put under "About the role" or separate "How We Work". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "How We Work" could be part of About the role or maybe Skills? Not exactly. Probably we can include as part of About the role. Then "What You’ll Bring": list of requirements (experience, skills). That's Requirements/Qualifications/Skills. We'll need to decide. We have: "10+ years of experience working in the design industry", "3+ years of working in a product-led organization", "5+ years of providing design direction and mentoring to junior colleagues in a leadership role", "3+ years leading a design systems and product design team", "3+ years shaping product strategy and vision — partnering with Product, Engineering, and executive leaders to define where a consumer product should go next, informed by market and industry immersion", "A strong visual aesthetic and design point of view, exampled in a rich portfolio", "Demonstrated thought leadership in B2C product workflows (or B2B workflows operating at consumer scale), with a consumer funnel/conversion mindset that goes beyond design systems craft", "Experience delivering multiple projects simultaneously with cross-disciplined teams", "Experience with capacity planning and workload management", "Knowledge of Figma, JIRA, and project management tools", "Working knowledge of usability best practices, including experience scoping and running usability testing where warranted", "Informed and strong opinions, loosely held", "A practitioner of user-centric processes and design thinking, with hands-on experience identifying consumer pain points and market opportunities through product discovery — not solely executing a roadmap defined by others", "Exemplifies a We, Not Me attitude". Also "Nice To Have Experience designing for a two-sided marketplace (e.g., buyer/seller, renter/landlord, host/guest)". That's a nice-to-have. We can put these under Requirements (maybe Qualifications). Since they are experience requirements. Could separate "Qualifications" for education? Not present. Could put under "Skills" for tools and abilities. But we need to avoid thin sections. Perhaps combine Requirements and Skills into one section "Requirements". But instruction says we can use those headings; we can include multiple if they have substantive content. Let's decide: We'll have "About the role", "Responsibilities", "Requirements", "Benefits". Pay and Schedule not present, so omit. Benefits: list under "How We Reward You": Inclusive and Competitive medical, Rx, dental, and vision coverage; Family forming benefits; 13 Paid Holidays; Flexible Time Off; 8 hours of paid Volunteer Time off; Immediate eligibility into Company 401(k) plan with 3.5% company match; Tuition Reimbursement program for degreed and non-degreed programs; 1:1 personalized Financial Planning Sessions; Student Debt Retirement Savings Match program; Free snacks and refreshments in each office location. We'll put under

  Benefits

  with
  . We must not include boilerplate like EEO etc. Remove that. Now produce HTML fragment. Structure:

  About the role

  Join us on our mission to empower more people to find their way home by breaking barriers to entry, making the right connections, and building confidence through expert guidance. Are you a design systems expert with a strategic, consumer-first mindset? Are you looking to be the driving force in creating world-class experiences that help people find and enjoy a home of their own — not just executing a roadmap, but helping shape it? If you want to expand your professional goals at Avail by Realtor.com®, this is the role for you! This role will immerse themselves in the market and our industry, partnering closely with senior leaders in Product and Engineering to define, create, and execute our bold vision for transforming the real estate industry — not simply implement a strategy set by others. You will be responsible for design decisions and patterns for multiple products and ensuring the adoption thereof by product designers who work in those areas. You’ll also build on the design system foundation by enhancing toolchain connections between design files and code, promoting education and advocacy, and collaborating closely with cross-functional teams across all platforms. A team of designers will report to this role, and you will closely partner with a sibling engineering team. You will also collaborate with cross functional leaders on team capacity and skills. And work with other design leaders to drive the strategy and execution of Design Ops tools and processes to create a more scalable and efficient design practice. This role reports to the Head of Avail. We balance creativity and innovation on a foundation of in-person collaboration. For most roles, our employees work four or more days in our offices, where they have the opportunity to collaborate in-person, adding richness to our culture and knitting us closer together.

  But we might split responsibilities separate. Better: Keep About the role as intro mission and maybe how we work. Then Responsibilities separate. Let's craft: About the role: mission statement + maybe brief. Responsibilities: list from "This role will immerse themselves..." plus "What You’ll Do" bullet points. We'll need to convert each bullet into
  • . The "What You’ll Do" section includes sentences each starting with a bold verb? Actually they are sentences: "Own the Avail design system. Define and evolve the components, patterns, and tokens powering Avail’s Renter, Landlord, and Public surfaces, and drive their adoption across the design team." etc. We'll split each sentence as separate
  • . Let's extract bullet points: - Own the Avail design system. Define and evolve the components, patterns, and tokens powering Avail’s Renter, Landlord, and Public surfaces, and drive their adoption across the design team. - Bring a consumer funnel mindset. Apply design thought leadership across full B2C workflows (or B2B workflows operating at consumer scale/complexity) — acquisition through conversion through retention — so the design system serves real user journeys and business outcomes, not just visual and component consistency. - Drive product discovery, then raise the bar on execution. Identify consumer pain points and market opportunities yourself — through research, data, and direct engagement with renters and landlords — rather than working solely from a roadmap handed to you. Set the quality standard for end-to-end product design across Avail, reviewing and guiding feature work so the experience stays cohesive as the product grows. - Make accessibility the default. Build accessible patterns and tokens into the system itself, and grow the team’s fluency so a11y is designed in from the start rather than retrofitted. - Champion usability. Bring rigor to usability best practices across the system and key workflows, and scope and run usability testing where it’s warranted — recognizing not every product or workflow justifies a formal study. - Keep design and code in lockstep. Partner with your engineering counterpart to align components across design and code, and advance a connected toolchain between Figma and the codebase. - Document so the system scales. Maintain clear, accessible documentation and contribution processes for every component, so designers and engineers can move without you in the room. - Make the case for the system. Translate the value of design systems and accessibility into language Product, Engineering, and executive partners care about, grounded in business and quality metrics. - Shape strategy, then plan a roadmap that ships. Immerse yourself in the market and our industry, and partner with cross-functional peers to define and navigate Avail’s long-term product strategy and vision. Translate that strategy — and the systems/accessibility work it requires — into a prioritized roadmap that maps to engineering’s release pipeline and Avail’s product timelines. - Extend the system to the brand. Partner with Brand and Marketing on consistency across external-facing assets, and maintain the icon and illustration libraries. - Grow the team. Mentor and manage a team of product designers, supporting their craft and career development and ensuring healthy coverage across projects. - Run a lean design practice. Partner with wider RDC design leadership on capacity, tooling, and process. You’ll be keeping workflows healthy in Jira and Confluence without letting ops become overhead. Now responsibilities also include earlier paragraph about immersing etc. We could incorporate that as part of responsibilities as well, maybe as introductory paragraph before list. But we can just include that paragraph as a

    under Responsibilities before the list. Now Requirements: list of experience and skills. We'll create

    with each item. Items: - 10+ years of experience working in the design industry - 3+ years of working in a product-led organization - 5+ years of providing design direction and mentoring to junior colleagues in a leadership role - 3+ years leading a design systems and product design team - 3+ years shaping product strategy and vision — partnering with Product, Engineering, and executive leaders to define where a consumer product should go next, informed by market and industry immersion - A strong visual aesthetic and design point of view, exampled in a rich portfolio - Demonstrated thought leadership in B2C product workflows (or B2B workflows operating at consumer scale), with a consumer funnel/conversion mindset that goes beyond design systems craft - Experience delivering multiple projects simultaneously with cross-disciplined teams - Experience with capacity planning and workload management - Knowledge of Figma, JIRA, and project management tools - Working knowledge of usability best practices, including experience scoping and running usability testing where warranted - Informed