Director of Product Design

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract from posting. We have sections: "Who we are", "Your Impact", "About The Role", "About You", "Who you'll work with", "Company Values", "Benefits And Perks", "Hiring Guidelines", "Compensation Range". Also note: "Note: This role is open to US-based applicants only." That's location requirement. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we have "About The Role" paragraph describing lead product design team, player/coach, etc. That's content. - Responsibilities: we can extract from "About The Role" bullet-like sentences describing duties: lead team, manage, develop, stay close, set expectations, own design principles, own design system, own AI, evolve design operating model, help shape product direction, decide design capacity, partner with brand design. Those are responsibilities. So we can create a Responsibilities section with list items. - Requirements: maybe from "About You": experience, 10+ years product design, 3+ years managing designers, accountable for experience, exceptional product judgment, etc. Also "Note: This role is open to US-based applicants only." That's a requirement (location). Also maybe "You have a strong point of view on AI..." etc. Those are qualifications/skills. We need to separate Requirements vs Qualifications vs Skills. The instruction says use headings for those categories if content exists. We can decide to put experience and location under Requirements, and specific abilities under Qualifications or Skills. But we need to avoid thin sections. Perhaps combine into one "Requirements" covering experience, location, etc. Or we could have "Qualifications" for the experiential and skill-based, and "Skills" for specific abilities like AI, design system, communication. However we risk creating many thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we should maybe have only About the role, Responsibilities, Requirements (which includes qualifications/skills), Benefits, Pay. Schedule not present, so omit. We need to include Benefits: we have "Benefits And Perks" list: competitive salary and internal transparent salary formula, flexible time off, 12 weeks fully paid parental leave, home office stipend, co-working stipend up to $300/month, yearly professional development stipend $1,800, top tier health insurance for US/Canada. Also maybe note about remote work. So we can list those. Pay: we have "Compensation Range: $226K - $242K". That's specific. So we can create Pay section with that. Schedule: not mentioned, omit. We must not include boilerplate like EEO, legal, scam warning, hiring guidelines (visa, equal opportunity). Also remove duplicated lines. We must preserve all substantive information. So we need to include all details from About The Role, About You, Benefits, Compensation. We must not repeat job title as heading. Not needed. We must not include Job ID/requisition numbers. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... prose summarizing? But we should preserve all substantive information; we can keep the original paragraphs but maybe break into

for prose and

• for list of duties. We can keep the "About The Role" paragraph as

  . Then responsibilities as

  . Similarly, About You can be part of Requirements section: we can have

  summarizing experience etc, but we need to preserve all specifics: 10+ years product design, 3+ years managing designers, accountable for experience, exceptional product judgment, craft details, ability to articulate why experience works, experience making complex B2B software simple, built/meaningfully evolved a design system adopted, point of view on AI, use AI in own practice, led senior ICs, managed principal/staff-level designers, cross-functional, technically fluent, comfortable with data/research, exceptional communicator, remote leader, clear writing, direct feedback, trust building, etc. Also location: US-based only. We could put all that in a

  under Requirements. But we need to avoid filler like "commensurate with experience" etc. Not present. Thus:

  Requirements

  • 10+ years of product design experience
  • 3+ years managing designers
  • Accountable for the end‑to‑end experience of a product and the team creating it
  • Exceptional product and design judgment, with an eye for detail and ability to articulate why an experience works
  • Experience making complex B2B software feel simple and intuitive
  • Proven track record building or meaningfully evolving a design system that teams genuinely adopted
  • Strong point of view on AI and the future of product design; uses AI in own design practice and thinks about trustworthy AI experiences
  • Experience leading senior individual contributors (principal or staff‑level designers), giving them real scope and increasing their effectiveness without competing for the work
  • Deeply cross‑functional product leader: technically fluent enough to earn engineers’ trust, comfortable using data and customer research to inform decisions, skilled at partnering with Product and Engineering on difficult trade‑offs
  • Exceptional communicator and remote leader: makes thinking visible through clear writing and direct feedback, treats words as part of the product experience, builds trust, alignment, and a strong design culture on a distributed team
  • US‑based applicants only (role open to US‑based applicants)
  But we also need to include "Who you'll work with" maybe not needed as separate section; could be part of About the role? Might be considered responsibilities? It's about reporting lines and partners. Could be included in About the role paragraph. But we already have About the role paragraph; we could incorporate that info there. However we must preserve all substantive information; we can add a sentence in About the role paragraph about reporting to CPO, partnering with CRO, VP of Engineering, Principal Designer, etc. That is part of role description. Thus About the role paragraph can be expanded to include that. Now Benefits: we need list.

  Benefits

  • Competitive salary with an internal, transparent salary formula based on market data
  • Flexible time off – choose the holidays and vacations that make sense for you
  • 12 weeks of fully paid parental leave for all new parents, including adoption and foster care
  • Home office stipend to help you get set up and productive
  • Co‑working stipend up to $300 per month if you choose to work out of a coworking space
  • Yearly professional development stipend of $1,800 to help you grow in your craft
  • Top‑tier health insurance for you and your dependents (if you’re in the U.S. or Canada)
  Pay:

  Pay

  Compensation range: $226K – $242K

  We should not include Schedule. Now ensure we don't repeat content. The About the role paragraph should capture the role description, including leadership, design system, AI, operating model, product direction, partnership with brand design, reporting lines. Let's craft About the role paragraph: "Lead our product design team as a player/coach. Manage and develop a small team of experienced product designers and stay close to the work through critique, design reviews, and occasional projects of your own. Your most senior individual contributors carry the most complex design problems; your job is to make sure the whole team's work meets the bar. Set clear expectations for craft and ownership and build a culture where critique and feedback make the work better. Turn great design judgment into something that scales. Own the design principles, standards, guardrails, and decision record that make a Help Scout experience feel like Help Scout, so designers, engineers, and AI agents can create high‑quality experiences with more speed and autonomy. Your most senior designers author the interaction models and product patterns that sit underneath them. Be accountable for our design system as a product. Set the priorities and resourcing for the Help Scout Design System (HSDS), drive its adoption across Product and Engineering, and make it useful and legible to both people and machines, working with the designer who serves as its technical lead for architecture, patterns, and Figma/code parity. Own how AI shows up in our product. AI is every designer's job, not one person's. You are accountable for Help Scout's point of view on trustworthy AI experiences: how AI communicates, gives people control, handles mistakes, and moves from assisting customers to acting on their behalf. Your most senior designers lead the design direction and patterns; you make sure that point of view is adopted and applied consistently by every designer, and that it evolves with the product. Evolve how design gets done as AI accelerates delivery. Own the operating model: workflows, tooling standards, design debt, how design works with Product and Engineering, and how the capacity AI frees up gets reinvested. Decide which of the practices the team pilots (code prototyping, AI‑assisted workflows) become the standard way we work. Your most senior designers shape how AI fits into the design process itself; you make sure that guidance becomes how the team actually works. Help shape product direction alongside Product and Engineering. As a member of our Experience Leadership Team (XLT), bring design judgment, customer understanding, and a clear view of where design investment will have the greatest roadmap impact. Carry business context, constraints, and initiative outcomes back to the design team, and bring designers into the forums where direction for their work is being set. Decide where design capacity goes. Match designers to workstreams based on business priority. Decide who is embedded where, when someone shifts to a higher‑priority problem, and when designers move from horizontal work to a deep, time‑bound embed in a single workstream. Partner with the Brand Design team in our GTM organization to help ensure design cohesion between marketing and in‑app product experiences. You report to the Chief Product Officer and partner closely with them; you also partner with the Chief Revenue Officer on design cohesion between marketing and product, and collaborate with the VP of Engineering on the design system, engineering collaboration, and AI‑assisted delivery. The Principal Designer, our most senior individual contributor, reports to you and leads product design direction across workstreams, the design direction for AI experiences, and the technical shape of HSDS." That's a long paragraph but preserves all. Now we need to ensure we didn't include any boilerplate like "Note: This role is open to US-based applicants only." We included that in Requirements. We also need to ensure we didn't include any duplicated lines. Now output HTML fragment. We'll wrap sections in order: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

  for each section heading. Let's craft Responsibilities list: we can extract from About the role but we already have About the role paragraph covering many responsibilities. To avoid duplication, we could keep About the role as a brief overview and Responsibilities as list of specific duties. But the instruction: "Prefer a few substantive sections over many thin ones." Having both About the role and Responsibilities may be okay if both have substantive content. However About the role currently is a long paragraph covering many responsibilities; if we also list responsibilities we may duplicate. Perhaps we can merge: About the role paragraph can be a short summary, and Responsibilities list the detailed duties. But we need to preserve all substantive info; we can split. Let's think: The posting has a section "About The Role" which is a narrative. We could keep that as About the role paragraph (the narrative). Then we