Director of Product, IT

We need to output HTML fragment with sections: About the role (but we already have "About The Role" heading in source). Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - About Rippling (company description) – maybe not needed as a section? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections if there is real specific content. We have "About The Role" which is basically description of role. Could map to "About the role". Then we have "What You Will Do" – responsibilities. Then "What You Will Need" – requirements/qualifications. Then "Nice to have" – maybe skills or additional qualifications. Then "Additional Information" includes salary/benefits/equity statement, office policy, accommodation, EEO, etc. We need to strip EEO boilerplate, accommodation request line? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement and accommodation request? The accommodation request is part of EEO? It's a request for accommodation; might be considered legal boilerplate. Probably remove. Also "Rippling highly values having employees working in-office..." is about schedule? It mentions office-based employees must work in office at least three days a week. That's schedule info (maybe schedule). Also "This role will receive a competitive salary + benefits + equity." That's benefits and pay info. Also "The salary for US-based employees will be aligned with one of the ranges below based on location; see which tier applies to your location here." That's pay info but no actual ranges given. Since we don't have actual numbers, we cannot create Pay section with placeholder like "not specified". The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive salary + benefits + equity" and mentions schedule (office at least three days a week). So we can include Benefits and Schedule sections? But we need actual content. For Benefits: we have "competitive salary + benefits + equity." That's vague but it's stating benefits exist. Could we include a Benefits section with that statement? It's not placeholder like "not specified". It's a statement that benefits are provided. That's substantive enough? Probably yes. For Pay: we have "competitive salary + benefits + equity." and mention salary ranges based on location but not actual numbers. That's still vague but it's stating salary is competitive and based on location. Might be considered substantive? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive salary" is somewhat vague but not exactly placeholder like "commensurate with experience". It's a statement that salary is competitive. Might be okay. However they also say "Prefer a few substantive sections over many thin ones." So maybe we combine Pay and Benefits into a single "Compensation" section? But they only allow headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could choose to include Benefits and Pay sections if we have content. But we might avoid Pay because it's vague. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (competitive salary + benefits + equity). So we can include them. Schedule: "Rippling highly values having employees working in-office to foster a collaborative work environment and company culture. For office-based employees (employees who live within a defined radius of a Rippling office), Rippling considers working in the office, at least three days a week under current policy, to be an essential function of the employee's role." That's schedule info: at least three days a week in office. So we can include Schedule section. Now we need to remove duplicated lines, boilerplate. Also remove "About Rippling" maybe not needed as a section? Could be considered company overview but not in allowed headings. Could we include as a

  before sections? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. It doesn't forbid other headings, but suggests using those for sections. We could include a brief intro paragraph about Rippling as a

    before the sections. That's okay. We must not repeat the job title as a heading. The job title is "Director of Product". Not used. We must not put Job ID/requisition numbers as headings – none present. Now we need to extract substantive content: - About the role: The paragraph after "About The Role": "We’re hiring a Director of Product to help lead Rippling’s IT business: device management, identity & access management, AI governance, ITSM, automated compliance, and inventory management. You’ll own strategy and execution across a broad product surface, hire and develop exceptional PMs, and partner directly with engineering, design, sales, marketing, and customer-facing teams to build products that define the next generation of IT. The world of IT has changed. Employees now work across a sprawling set of devices, apps, permissions, data, AI tools, and automated agents. The old IT stack — MDM, identity, ticketing, inventory, compliance, and access governance as separate systems — creates fragmentation exactly where companies need control. Rippling IT is the IT infrastructure for the AI era: one platform that unifies identity, devices, inventory, support, AI governance, and compliance on a single data graph, so policy is set once and enforced everywhere. This is one of Rippling’s most strategic and fastest-growing businesses, and we’re looking for a product leader who can scale both the product and the team behind it." That's the role description. We'll put that in

    under

    About the role

    . - Responsibilities: "What You Will Do" bullet points (though they are not bullet list but sentences separated by line breaks). We need to convert to
    • . The content: Own product strategy and execution for major parts of Rippling’s IT suite across device management, identity & access management, AI governance, ITSM, automated compliance, and inventory management Hire, develop, and lead a high-performing team of product managers, raising the bar for product judgment, customer empathy, velocity, and craft Define the next generation of IT products for a world shaped by AI, automation, distributed work, and increasing security and compliance expectations Partner deeply with engineering and design to build products that solve complex customer problems with simple, powerful workflows Work closely with GTM teams to understand customer needs, sharpen positioning, drive adoption, and scale the business Be a thought partner to the IT GM and senior leadership on product strategy, org design, sequencing, and long-term platform bets Develop a clear point of view on how AI will change IT, security, governance, and the way companies manage their workforce systems We'll make each a
    • . - Requirements/Qualifications: "What You Will Need": Deep product leadership experience building and scaling complex products; A track record of hiring, growing, and leading high-performing product teams; Excellent product taste and systems thinking: you can turn complex workflows, edge cases, and platform constraints into elegant customer experiences; High clock speed, strong ownership, and a bias toward action. We could put under

      Requirements

      or

      Qualifications

      . The instruction lists both. We need to decide which to use. Since the content is about experience and skills, maybe "Requirements". We'll use Requirements. - Nice to have: "Strong IT, infrastructure, security, or compliance buyer empathy. You understand the world of IT admins, CIOs, CISOs, and the teams who operate mission-critical systems". This could be under

      Skills

      or maybe "Nice to have" as additional qualifications. We'll put under

      Skills

      . - Benefits: "This role will receive a competitive salary + benefits + equity." Also maybe mention equity. We'll put under

      Benefits

      as a

      that says "Competitive salary, benefits, and equity." - Pay: "The salary for US-based employees will be aligned with one of the ranges below based on location; see which tier applies to your location here. A variety of factors are considered when determining someone’s compensation–including a candidate’s professional background, experience, and location. Final offer amounts may vary from the amounts listed below. Commission is not guaranteed". This is somewhat vague but we can include as

      Pay

      with a

      summarizing: Salary is based on location-based ranges; final offer may vary; commission not guaranteed. But we need to avoid filler like "not specified". This is not filler; it's stating that salary is based on location ranges, etc. It's okay. - Schedule: "Rippling highly values having employees working in-office to foster a collaborative work environment and company culture. For office-based employees (employees who live within a defined radius of a Rippling office), Rippling considers working in the office, at least three days a week under current policy, to be an essential function of the employee's role." We'll put under

      Schedule

      as a

      . We should also include a brief intro about Rippling maybe as a

      before sections. Not required but okay. We must remove EEO boilerplate: The paragraph starting "Additional Information Rippling is an equal opportunity employer..." and the accommodation request line. Remove those. Also remove duplicated lines: I don't see duplicates. Now produce HTML fragment: no or , no markdown fences. We'll output something like:

      About Rippling: Rippling gives businesses one place to run HR, IT, and Finance. It brings together all of the workforce systems that are normally scattered across a company, like payroll, expenses, benefits, and computers. For the first time ever, you can manage and automate every part of the employee lifecycle in a single system. Take onboarding, for example. With Rippling, you can hire a new employee anywhere in the world and set up their payroll, corporate card, computer, benefits, and even third-party apps like Slack and Microsoft 365—all within 90 seconds. Based in San Francisco, CA, Rippling has raised $1.4B+ from the world’s top investors—including Kleiner Perkins, Founders Fund, Sequoia, Greenoaks, and Bedrock—and was named one of America's best startup employers by Forbes.

      Then sections. But the instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills