Manager, DTC Analytics

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 must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. First, there is an "About Harry’s" description (company overview). Should we include that? The instruction says use headings for sections like About the role, Responsibilities, etc. The company overview is not one of those headings. Should we include it? Possibly as a

before sections? The instruction: "You reformat a job posting into clean, well-structured semantic HTML. Rules: 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. Do NOT repeat the job title as a heading (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences." Thus we need to include sections only if they have real content. The posting includes "About The Role" (which we can map to "About the role" heading). Then there is a list of responsibilities under "Here's what you'll accomplish:" with bullet points. Then there is "This may describe you:" which includes qualifications/requirements/skills. Then "Benefits And Perks" with list. Then salary range info (Pay). There's also schedule info: "The Mammoth Brands' working model is in-office Tuesday, Wednesday, and Thursday." That's schedule. Also mention office location etc. We need to decide which sections to include: About the role, Responsibilities, Requirements (maybe combine qualifications/skills), Benefits, Pay, Schedule. Possibly also Skills separate? The "This may describe you:" includes technical skill, BI tool fluency, AI-forward, business acumen, engaged thought partner, clear communicator, optimistic, etc. That's a mix of qualifications and skills. We could split into Requirements (experience, years) and Skills (technical). But instruction says prefer few substantive sections over many thin ones. Could combine into one "Requirements" section that includes both experience and skills. Or we could have "Qualifications" and "Skills". But we need to avoid thin sections. Let's see content: There's explicit "5+ years in data analytics or a similarly analytical field..." that's experience requirement. Then "Proficient Technical Skill – Fluent in SQL (Python or R a plus)..." that's skill. Then "BI Tool Fluency – Hands-on experience building and maintaining dashboards..." skill. Then "AI-Forward – You use AI tools..." skill/behavior. Then "Business Acumen & Judgment..." skill. Then "Engaged Thought Partner..." skill. Then "Clear, Confident Communicator..." skill. Then "You thrive on direct, honest, and supportive communication..." skill. Then "You are infectiously optimistic and curious..." skill. Thus we could have a "Requirements" section with experience and maybe combine skills. Or we could have "Qualifications" for experience and "Skills" for technical/behavioral. But that might be many sections. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine into one "Requirements" section that includes both experience and skills. Or we could have "About the role", "Responsibilities", "Requirements", "Benefits", "Pay", "Schedule". That's six sections, each substantive. Let's extract content. About the role: The paragraph starting "As the Analytics Manager for DTC, you'll build and drive the reporting and diagnostic analytics..." That's the role description. We'll put that in

  . Responsibilities: The bullet list under "Here's what you'll accomplish:" each line starts with a verb. We'll make

  • for each. Requirements: Combine experience and skills. We'll list items: 5+ years in data analytics or similarly analytical field, using data to drive decision-making... Proficient Technical Skill – Fluent in SQL (Python or R a plus), ability to query, manipulate, analyze data end-to-end. BI Tool Fluency – Hands-on experience building/maintaining dashboards/models in modern BI platform (Omni; prior experience with Looker, Tableau, Power BI enabler). AI-Forward – You use AI tools to speed up analysis, comfortable helping others build fluency. Business Acumen & Judgment – Connect dots across data sources, business priorities, customer signal, nose for which questions worth chasing. Engaged Thought Partner – When someone brings you a question, they leave with recommendation and POV, not just analysis plan; can point to specific insights that changed a real decision. Clear, Confident Communicator – Explain complex ideas simply, comfortable challenging senior stakeholders. You thrive on direct, honest, supportive communication and feedback. You are infectiously optimistic and curious – excited about new challenges, hard things are hard but you don't let that get in the way. We could also include "You will report to the Sr. Director of Omnichannel Analytics, with a dotted line to our VP of DTC" maybe as part of About the role or Responsibilities? It's reporting line; could be part of About the role. We'll include in About the role paragraph. Benefits: List from "Benefits And Perks": Medical, dental, and vision coverage; 401k match; Equity in Mammoth Brands; Flexible time off and working hours; L&D stipend; 4 weeks sabbatical after 5 years, 6 weeks after 10 years, and 8 weeks after 15 years; 20 fully paid weeks off for parents who give birth, or 16 fully paid weeks off for all other paths to parenthood; Fun IRL and virtual events including happy hours, team building events, and parties on our rooftop; Free products from our family of brands; The Mammoth Brands' working model is in-office Tuesday, Wednesday, and Thursday. Our beautiful 70,000 square foot SoHo office is decked out with bagels on Wednesdays and lunch on Thursdays, and fully stocked kitchens with snacks, coffee, and drinks everyday. Can’t forget the free products and the opportunity to have some meetings without Zoom! We can’t quantify all of the intangible things we think you’ll love about working at Mammoth Brands, like the exciting challenges we tackle, the smart and humble team you’ll get to work with, and our supportive and inclusive culture. We need to separate schedule from benefits? Schedule is "The Mammoth Brands' working model is in-office Tuesday, Wednesday, and Thursday." That's schedule. Also mention office details maybe not schedule but could be part of benefits. However schedule section should be included if posting states it. It does state working model. So we can create a Schedule section with that sentence. The rest of office description could be part of Benefits (maybe as a perk). But we need to avoid duplication. We'll put schedule line in Schedule section. The rest of office description (bagels Wednesdays, lunch Thursdays, stocked kitchens, free products, meetings without Zoom) could be considered benefits/perks. We'll include them in Benefits. Pay: Salary range: "The base salary hiring range for this position is $132,000-$150,000, but the final compensation offer will ultimately be based on the candidate’s location, skill level and experience." We'll put that in Pay section as a

    . Now we need to remove boilerplate: EEO statements, visa sponsorship, etc. Also remove "About Harry’s" company overview? It's substantive but not under a heading we are using. Should we include it? The instruction says use headings for sections like About the role, Responsibilities, etc. It didn't forbid other content outside those headings. It says "include a section ONLY when the posting has real, specific content for it". It doesn't say we cannot have other

    content before sections. However typical job posting reformatting might include a brief company overview as a

    before sections. The instruction didn't forbid that. It said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include a short

    for company overview. But we need to preserve ALL substantive information. The "About Harry’s" paragraph is substantive. We'll include it as a

    before the sections. Also "About The Team" paragraph is substantive. We'll include that as a

    as well. Thus final HTML: start with maybe a

    for company overview, then a

    for team description, then

    About the role

    with

    content, then

    Responsibilities

    with
    , then

    Requirements

    with
    (or

    ?), but we have list of items; better to use

    • . Then

      Benefits

      with
      , then

      Pay

      with

      , then

      Schedule

      with

      . We must not include sections with filler. All have content. Check for any duplicated lines: Ensure we don't repeat. Now craft HTML. We'll need to escape any HTML special characters like apostrophes? It's fine. Let's write. Company overview paragraph: "Harry’s is a men’s grooming brand that offers high quality shave, body, hair, and skin care products at an exceptional value. Launched in 2013, Harry’s redefined the shaving experience and helped pioneer the earliest era of direct to consumer in the process. Since then, the brand has become the #2 shave brand globally and expanded to offer products for every step in its customer’s routine. Harry’s is also on a mission to ensure guys have access to quality mental health care. To date, the brand has helped connect over 2 million men to quality mental health resources. Harry’s is part of Mammoth Brands, the modern CPG company behind category-leading brands Harry’s, Flamingo, Lume, Mando, and Coterie. Driven by a mission to “Create Things People Like More,” the company is creating a new model—and home—for brands, founders, and talent looking to solve unmet needs, improve peoples’ lives and ultimately change the status quo. Even as we grow, we take extra care to maintain the small, scrappy, entrepreneurial culture that helped to get us where we are today: a company that people like more, that better serves its customers, employees, and community. Mammoth Brands is committed to making a positive impact and donated over $20 million through our network of nonprofit partners to date. We build brands that move fast and think big — and we hire people who are curious about AI, willing to experiment with it in their day-to-day work, and excited to accelerate what's possible. We prioritize giving our team the tools, training, and space to build real fluency, so you grow alongside the technology and help shape how we use it." Team paragraph: "The Centralized Insights &