Engineering Manager, Growth

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Minimum Qualifications and Preferred Qualifications?), Benefits, Pay, Schedule. Must only include sections if real specific content present. We need to extract content from posting. First, remove boilerplate: About Anthropic, How We're Different, Guidance on Candidates' AI Usage, etc. Also remove cookie/navigation/legal/EEO etc. The posting includes sections: About The Role, Key Responsibilities, Minimum Qualifications, Preferred Qualifications, The annual compensation range..., Logistics (Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship, etc.), We encourage you to apply... (that's boilerplate), Your safety matters... (scam warning), How We're Different (boilerplate), Come work with us! (benefits description). Also there is a paragraph about benefits: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." We need to include sections: About the role (maybe from "About The Role" paragraph). Responsibilities (Key Responsibilities). Requirements (Minimum Qualifications and Preferred Qualifications maybe combined? Could separate but better to have Requirements section containing both? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate? But we can choose to include only those with content. We have Minimum Qualifications and Preferred Qualifications; could put them under Requirements (or Qualifications). Since we have both, maybe we create a Requirements section for Minimum Qualifications and a Qualifications section for Preferred Qualifications. Or combine. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Minimum and Preferred into one Requirements section. But we have separate headings allowed: Requirements, Qualifications. Could do both if they have content. However they'd be thin? Minimum Qualifications is a list of bullet points; Preferred Qualifications also list. Both are substantive. Could have two sections: Requirements (Minimum Qualifications) and Qualifications (Preferred Qualifications). That seems okay. Pay: we have annual compensation range: $405,000—$485,000 USD. So include Pay section. Schedule: we have Location-based hybrid policy: "Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." That's schedule info. So include Schedule section. Benefits: we have benefits description: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." Also maybe other benefits mentioned earlier? Not much. So include Benefits section. About the role: we have paragraph under About The Role: "We're looking for an experienced growth engineering leader to build and lead our Growth Engineering team as founding members of our growth initiative. This key leadership role requires deep expertise in driving user acquisition, engagement, and retention through data-driven strategies and technical implementations. Having led growth engineering teams before, you'll be responsible for identifying and executing on growth opportunities across our product surface area, developing experimentation frameworks, and scaling our impact through technical solutions." We can put that as About the role. Responsibilities: list under Key Responsibilities bullet points. Now we need to format as HTML: use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate like "We encourage you to apply..." etc. Also remove "Your safety matters..." etc. Also remove "How We're Different" etc. Also remove "Come work with us!" maybe part of benefits but we already captured benefits. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all bullet points exactly as given (maybe rephrase? No, preserve). We must not omit any bullet points. Let's extract bullet points. Key Responsibilities: - Build and lead a high-performing team of growth engineers focused on user acquisition, activation, and retention - Define and execute the technical strategy for growth initiatives, including A/B testing frameworks and measurement systems - Create clarity and direction for the team in a fast-moving, ambiguous environment - Collaborate cross-functionally with product, marketing, and data science teams to identify and prioritize growth opportunities - Take an inclusive, equitable approach to hiring and coaching technical talent - Drive the development of scalable systems for experimentation, personalization, and optimization Minimum Qualifications: - Strong technical background in full-stack development with proven success building and shipping growth initiatives - Track record of leading teams in growth experimentation, A/B testing, and data-driven product optimization - Experience recruiting, scaling, and retaining engineering talent in a high-growth environment - Excellent leadership and communication skills, with ability to work effectively across functions - Demonstrated success in building a culture of belonging and engineering excellence Preferred Qualifications: - 5+ years of experience as an product minded engineering manager, with at least 2 years leading growth engineering teams - Experience applying machine learning and AI technologies to growth challenges - Demonstrated success implementing product-led growth strategies and viral loops at scale - Expertise in modern web development stacks and experimentation frameworks - Experience with user segmentation and cohort analysis tools - Startup experience, particularly in scaling products from zero to one Logistics (we need to extract specifics for Schedule and maybe other metadata like Minimum education etc. But we only need Schedule section; we can include other logistics as short p? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short p for logistics like Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship. But we already have Schedule section for location-based hybrid policy. The other logistics (minimum education, field of study, years of experience) could be minor metadata; we could include them in a short p under maybe a generic "Logistics" but we don't have a heading for Logistics unless we want to. The instruction says prefer a few substantive sections over many thin ones. So maybe we just include Schedule section and drop other logistics (minimum education etc.) as they are minor metadata. However we must preserve ALL substantive information; is minimum education substantive? It's a requirement but maybe considered minor metadata. The instruction says fold minor metadata into a short

  or drop it. So we could include a short p after the sections maybe under a heading? But we cannot create a heading for minor metadata unless it's substantive. Safer to include a short p after the sections (maybe after Benefits) that includes those details. But we need to decide where to put it. Could add a

  with that info after Benefits before closing. However the instruction says output ONLY the HTML fragment; we can include multiple

  elements not under headings? Probably okay. But we must not invent or summarize away detail. So we need to include the exact text for Minimum education, Required field of study, Minimum years of experience, Location-based hybrid policy, Visa sponsorship. However we already used Location-based hybrid policy for Schedule section; we should not duplicate. So we can put the Schedule section with that policy text. For the other logistics, we can include a short p maybe under a heading "Logistics" but that might be considered thin. Better to just include them as a

  without heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says prefer a few substantive sections over many thin ones. So we could add a

  Logistics and then list those items as

  . But that would be another section; maybe okay if it's substantive. However the items are: Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience; Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience; Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position; Visa sponsorship: We do sponsor visas! However, we aren't able to successfully sponsor visas for every role and every candidate. But if we make you an offer, we will make every reasonable effort to get you a visa, and we retain an immigration lawyer to help with this. These are somewhat generic but still substantive. Could include them. But we already have Requirements and Qualifications sections covering experience etc. The Minimum years of experience is vague; maybe we can drop as minor metadata. The instruction says fold minor metadata into a short

  or drop it. So we could drop Minimum years of education etc. However we must preserve ALL substantive information; if we drop it, we might be violating. But the instruction allows dropping minor metadata if we fold into short p or drop it. So we can drop them? It says "fold minor metadata into a short

  or drop it." So we can either include them in a short p or drop them. To be safe, include them in a short p after the sections (maybe under a heading "Logistics" but that would be a heading). But we could just include a

  without heading containing that info. However the instruction says use

  for section headings (list). It doesn't say we cannot have other headings, but we should follow the pattern. Safer to include a

  Logistics and then a

  with those items. That would be another section but maybe okay. But we already have many sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Adding Logistics makes 8 sections. The instruction says prefer a few substantive sections over many thin ones. Logistics might be thin but still substantive. However we could incorporate those logistics into existing sections: Minimum education could go under Requirements (maybe as a bullet). Required field of study could also go under Requirements. Minimum years of experience is vague; maybe we can drop. Visa sponsorship could go under Benefits? Not really. Could be its own short p. Given the instruction to prefer few sections, maybe we just include Schedule and Benefits and Pay and drop other logistics as minor metadata (fold into short p or drop). I'd lean to drop them because they are generic and not specific to the role. The instruction says "fold minor metadata into a short

  or drop it." So we can drop them entirely. That seems acceptable. Thus we will output sections: About the role, Responsibilities, Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Benefits, Pay, Schedule. Now we need to format. About the role: prose paragraph(s). There's one paragraph. We'll put

  with that text. Responsibilities:

  • each bullet. Requirements:
    • each bullet from Minimum Qualifications. Qualifications:
      • each bullet from Preferred Qualifications. Benefits: prose: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." Pay: prose: "The annual compensation range for this role is $405,000—$485,000 USD." Might need to include the note about OTE? The posting says: "The annual compensation range for this role is listed below. For sales roles, the range provided is the role’s On Target Earnings ("OTE") range, meaning that the range includes both the sales commissions/sales bonuses target and annual base salary for the role. Annual Salary $405,000—$485,000 USD". Since this is not a sales role, we can just state the range. We'll include the sentence: "Annual Salary $405,000—$485,000 USD." Schedule: prose: "