Director of growth marketing

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job posting content. Content: - Who We Are (description) - Role Overview (description) - Who You Are (list of traits) - What You'll Do (list of responsibilities) - What You'll Need (requirements) - Nice to Have (nice-to-have) - The Details (reporting line, salary range, start date, location, benefits/perks) - Benefits and Perks (list) - Then EEO statement etc (boilerplate to remove) We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: Could be "Who We Are" + "Role Overview". That's about the role/company. So we can have an

  About the role

  with prose summarizing who we are and role overview. - Responsibilities: "What You'll Do" list. - Requirements: "What You'll Need" list (must-have). Also maybe "Nice to Have" could be qualifications/skills? But we should not create thin sections. Could combine Requirements and Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple if substantive. We need to avoid filler. We have specific content for Requirements (must-have). Also we have Nice to Have (could be Qualifications or Skills). We have Benefits and Perks (list). We have Pay (salary range). We have Schedule (When: November 1st 2026, Where: San Francisco, 3x/week in office). That's schedule info. Thus we can include sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Benefits, Pay, Schedule. We must not include sections with placeholder/filler. All have real content. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for each section heading. Use

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

    for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "7+ years in marketing at high-growth startups, with real ownership of retention, lifecycle, or growth somewhere in that time." etc. We need to avoid repeating job title as heading (not needed). No Job ID. We need to remove boilerplate: EEO statement, diversity statement, Fair Chance Ordinance, etc. Also remove duplicated lines. We need to ensure we don't include navigation etc. Let's extract substantive content. From "Who We Are": "Cambium is a modern American wood manufacturer, distributor, and technology company connecting and modernizing the wood economy. We work with architects, builders, and leading brands across the built environment, including Amazon, Room & Board, and Equinox. Our work has been recognized by Time's Best Inventions and Fast Company's Innovation by Design Awards. Technology is how we match supply to demand across a fragmented industry. The American hardwood industry has lost more than half its sawmills in the last two decades. Quality trees go to waste, and the US imports more lumber than it produces, even though domestic capacity could meet nearly all of our needs. Until now, this industry forced a choice: local relationships or national scale, meaningful materials or modern efficiency. We don't think those are real tradeoffs. We're building the infrastructure to prove it, with modern software, better supply chains, and a clear view of what comes next: a wood economy that's local, efficient, and built to last." From "Role Overview": "An architect specs our material on one project, a builder installs it, and every one of them has a next project. The gap between the first order and the second, and between the one product a customer knows us for and the full range we supply, is our biggest lever. Nobody owns it today. You'll own lifecycle for Cambium end to end, reporting to the VP Marketing and working closely with Sales and Supply. Some quarters the most interesting problem won't look like lifecycle at all. If that sounds like the fun part, this is your role." From "Who You Are": bullet points (generalist, taste, technology default, systems thinker, high ownership, high slope). We'll need to capture them as list? It's a list of traits. Could be under Requirements or Qualifications? Probably under Requirements? But they are more like desired attributes. Could be under Qualifications or Skills. We'll decide later. From "What You'll Do": list of responsibilities: - Own lifecycle for Cambium: you build the strategy and ultimately own the results, including retention, expansion, and how customers move across our product range and our brands. - Partner with Sales and Supply on the customer experience: Build the programs, pressure-test them in live accounts, and change them the moment a customer tells you they're wrong. - Define and run our customer marketing playbook for acquisitions: M&A is a big part of how Cambium grows, and every company we buy comes with its own customers. You own how they're brought into Cambium and what they hear from us, and you run the playbook for the next deal. - Scale from the 10k foot view down to the minutiae: what share of customers come back within a year, and what's the number we plan against? Why did this account go quiet in March? Why is this HubSpot workflow firing twice, and what's the fix? From "What You'll Need": requirements: - 7+ years in marketing at high-growth startups, with real ownership of retention, lifecycle, or growth somewhere in that time. - Something you can point to that didn't exist before you: a function, a program, a system, built from close to nothing, as a team lead or a senior IC. - Experience at a high-growth startup, where you built things before there was a process for them. - Deep proficiency in HubSpot or an equivalent customer engagement tool (Braze, Iterable, Klaviyo) and hands-on with AI and automation tools. You build it yourself. From "Nice to Have": - Experience in physical products, construction, or building materials, or any industry where the buyer is a professional with a project. - Experience integrating an acquired company's customers or CRM. - Early-stage experience where you built the lifecycle stack rather than inheriting one. From "The Details": - This role will report to: VP Marketing - Salary Range: $160-190K - When: November 1st 2026 - Where: San Francisco, 3x/week in our beautiful office in the Presidio! - Benefits and Perks list: - Equity options package - Flexible PTO - 401k matching - Comprehensive medical, dental & vision insurance - Work with an incredibly smart, diverse, climate mission-driven team - An opportunity to play a core role in defining our fast-growing company - Volunteer tree planting days We need to map these to sections. Potential sections: - About the role: combine Who We Are + Role Overview (maybe also Who You Are? but that's more about candidate). We'll keep About the role as description of company and role. - Responsibilities: What You'll Do list. - Requirements: What You'll Need list (must-have). - Qualifications: Nice to Have list (maybe also include Who You Are traits? but we can treat Who You Are as Qualifications/Skills). However we need to avoid thin sections. Could combine Who You Are traits into Qualifications as a list of desired attributes. But we already have Nice to Have list. Could we make Qualifications include both Who You Are and Nice to Have? That would be substantive. - Skills: maybe not needed separately if we have Qualifications. - Benefits: Benefits and Perks list. - Pay: Salary Range. - Schedule: When and Where (start date and location/hybrid schedule). We need to avoid creating sections with placeholder text. All have content. We need to output HTML with headings

    and appropriate

    or

    • . We must not repeat job title as heading. We must not include any boilerplate like EEO etc. Let's craft. First, About the role: combine Who We Are and Role Overview into prose. Could be two paragraphs. We'll put

      About the role

      then

      ...

      containing both. We need to preserve all substantive info; we can combine but must not lose any detail. We'll include both paragraphs. Next, Responsibilities:

      Responsibilities

      then
      • each responsibility. Next, Requirements:

        Requirements

        then
        • each requirement. Next, Qualifications:

          Qualifications

          then
          • each nice-to-have plus maybe Who You Are traits? Let's include Who You Are traits as part of Qualifications as they are desired attributes. But we need to ensure we don't duplicate. We'll list them. Who You Are traits: - A generalist: Range and judgment. You've built across the marketing stack, and you can tell the difference between the problem that's loud and the one that's important. - You have taste: In a world where anyone can generate anything, you pride yourself on curation: knowing what's worth sending, what's worth building, and what a customer will actually notice. - Technology is your default: When you hit a problem, your first move is to find a creative way to solve it with tools, whether that's an automation, an enrichment workflow, or something you stitch together yourself. You see it, you take action, you figure it out, and you're excited by that. - A systems thinker: You see the customer relationship as one connected system, from first inquiry to fifth project, and you build the infrastructure that holds it together. - High ownership, high slope: You ask questions before you answer, you're comfortable being handed a problem with no clear owner, and when more customers come back for a second project, you want it to be because of something you built. We can turn each into a list item. Nice to Have list: - Experience in physical products, construction, or building materials, or any industry where the buyer is a professional with a project. - Experience integrating an acquired company's customers or CRM. - Early-stage experience where you built the lifecycle stack rather than inheriting one. We'll combine them under Qualifications. Next, Benefits:

            Benefits

            then
            • each benefit. Next, Pay:

              Pay

              then

              Salary Range: $160-190K

              Next, Schedule:

              Schedule

              then

              Start date: November 1st 2026. Location: San Francisco, 3x/week in office (Presidio).

              We need to preserve the exact wording: "When: November 1st 2026" and "Where: San Francisco, 3x/week in our beautiful office in the Presidio!" We'll combine. Make sure not to include any extra fluff. Now ensure we didn't miss any substantive info: The "The Details"