Head of Growth Marketing (Remote, Jacksonville)

We need to output HTML fragment with sections: About the role, Responsibilities? The posting includes sections: About The Role, What You Own, What You Need, Process, How To Apply. Also maybe Benefits? Not present. Pay? Not present. Schedule? Not present. So we include only sections with real content. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. So we need to capture the content. Let's parse the posting: - Intro line: "Blacksmith Agency Marketing Full time Remote (USA, Canada or South Africa)" - This is maybe metadata (job type, location). Should we include? It's not a heading; we can put in a short

  maybe. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location and employment type in a

  . - About The Role: paragraph(s). We'll put

  About the Role

  then

  with the prose. - What You Own: list of bullet points? It's a series of sentences each starting with a bold? Actually it's a list: "The PPC strategist and the SEO strategist: their quality bar, their development, their reviews, and the call when someone is not going to get there.The standard the work is held to. What a good audit looks like, what gets checked before work leaves the agency, how an account is reported. You write it and you hold two specialists to it.Client results across the whole function, including whether our reporting is honest. Nobody here is auditing attribution and GA4 accuracy today.The escalation when an account is at risk. You diagnose it, you direct the strategist who fixes it, and you are on the call with the client.Channel strategy and where budget goes as accounts scale.What we tell sales we can credibly deliver, before it gets sold.The hiring plan for the department, and first-round interviews for your own team, within about a quarter." We can treat each sentence as a bullet? Or we can keep as prose. The instruction: Use

  • for any list of duties/requirements/benefits. This is a list of responsibilities/duties. So we should make a
    with
    • items. We need to split into logical items. Let's break: - The PPC strategist and the SEO strategist: their quality bar, their development, their reviews, and the call when someone is not going to get there. - The standard the work is held to. What a good audit looks like, what gets checked before work leaves the agency, how an account is reported. You write it and you hold two specialists to it. - Client results across the whole function, including whether our reporting is honest. Nobody here is auditing attribution and GA4 accuracy today. - The escalation when an account is at risk. You diagnose it, you direct the strategist who fixes it, and you are on the call with the client. - Channel strategy and where budget goes as accounts scale. - What we tell sales we can credibly deliver, before it gets sold. - The hiring plan for the department, and first-round interviews for your own team, within about a quarter. That seems reasonable. - What You Need: list of requirements. We'll make
      with items. Breakdown: - Strategists or specialists who have reported to you, where their reviews, their development and the decision when someone was not working out were yours. Managing accounts is not this. - 7+ years across paid media and SEO. Owning one channel while sitting beside the other does not count here. - Enough depth in Google Ads, GA4, Search Console, Meta and Microsoft Ads to tell good work from work that merely looks good. That is a lower bar than doing it and a higher bar than reading a report. - One account you turned around that you can talk through: the metric, the figure before, the figure after, and why the change worked. Whose hands were on the keyboard matters far less than whether the diagnosis was yours. - Comfortable being the client-facing owner when an account is underperforming. That call comes to you, not to the strategist. - Agency experience carrying many accounts at once. - Please do not apply if: - Nobody has ever reported to you, or you have never owned someone's review or had to performance-manage anyone. - You have only ever run one channel. - All of your experience is in-house on a single brand. - What you actually want is to keep building campaigns yourself. That is not a lesser ambition, it is a different job, and this is not it. - None of these are preferences we bend on. They are how we screen, so applying anyway costs you an hour and gets you a no. We can include these as bullet points. - Process: description: "Three conversations, then a decision. A thirty minute screen with our recruiter, a first round with the founder this seat reports to, and a final. No take-home project and no panel interview." We'll put as

      or maybe

      but it's prose. - How To Apply: "Four fields at the link, then a short 6 minute Predictive Index assessment. Use the same email throughout. No cover letter." We'll put as

      . We also need to include the location/employment type maybe as a

      before sections. Let's craft HTML. We must not include or . Just fragment. We'll start with a

      for location: "Blacksmith Agency Marketing – Full‑time Remote (USA, Canada or South Africa)". Then sections. Make sure headings are exactly as per examples: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we can use any of those headings if content matches. The instruction: use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. For "About the role" we have About The Role. So heading:

      About the role

      . For responsibilities we have What You Own (which is responsibilities). So we can use

      Responsibilities

      . For requirements we have What You Need. Could map to

      Requirements

      or

      Qualifications

      . Since it's about qualifications, we can use

      Qualifications

      . Process maybe not a standard heading; but we could use

      Process

      though not in list. The instruction says use those examples but not limited? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can still use other headings but better to stick to those. Process could be considered part of "About the role"? But we have separate section. Could we put Process under Responsibilities? Not ideal. Maybe we can omit Process heading and just include as a

      under Responsibilities? But the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Process is real content. So we need a heading. The examples are not exhaustive; we can use

      Process

      . Similarly How To Apply could be

      How to apply

      but not in examples. Might be okay. However to be safe, we could treat "Process" as part of "About the role"? But it's distinct. I'd rather include headings Process and How to apply as

      . The instruction didn't forbid other headings; just gave examples. So fine. Let's craft. We need to ensure we use

      • for any list of duties/requirements/benefits. For Responsibilities we have list; for Qualifications we have list; maybe also for Benefits? none. We'll output:

        Blacksmith Agency Marketing – Full‑time Remote (USA, Canada or South Africa)

        About the role

        Blacksmith Agency runs PPC and SEO for clients across multifamily, B2B and technical verticals. As Head of Growth Marketing you lead that department. The PPC strategist and the SEO strategist report to you and they are the specialists in their channels. Right now nobody owns this function, which is the whole reason this seat is open. This is a management seat, not a senior individual contributor one. You will not be building campaigns, and on technical SEO your strategist will know more than you do. That is the arrangement, not a gap. You carry channel strategy and where budget goes as accounts scale. The strategists carry the execution of it, and you carry whether the department delivers.

        Responsibilities

        • The PPC strategist and the SEO strategist: their quality bar, their development, their reviews, and the call when someone is not going to get there.
        • The standard the work is held to. What a good audit looks like, what gets checked before work leaves the agency, how an account is reported. You write it and you hold two specialists to it.
        • Client results across the whole function, including whether our reporting is honest. Nobody here is auditing attribution and GA4 accuracy today.
        • The escalation when an account is at risk. You diagnose it, you direct the strategist who fixes it, and you are on the call with the client.
        • Channel strategy and where budget goes as accounts scale.
        • What we tell sales we can credibly deliver, before it gets sold.
        • The hiring plan for the department, and first‑round interviews for your own team, within about a quarter.

        Qualifications

        • Strategists or specialists who have reported to you, where their reviews, their development and the decision when someone was not working out were yours. Managing accounts is not this.
        • 7+ years across paid media and SEO. Owning one channel while sitting beside the other does not count here.
        • Enough depth in Google Ads, GA4, Search Console, Meta and Microsoft Ads to tell good work from work that merely looks good. That is a lower bar than doing it and a higher bar than reading a report.
        • One account you turned around that you can talk through: the metric, the figure before, the figure after, and why the change worked. Whose hands were on the keyboard matters far less than whether the diagnosis was yours.
        • Comfortable being the client‑facing owner when an account is underperforming. That call comes to you, not to the strategist.
        • Agency experience carrying many accounts at once.
        • Please do not apply if:
        • Nobody has ever reported to you, or you have never owned someone's review or had to performance‑manage anyone.
        • You have only ever run one channel.
        • All of your experience is in‑house on a single brand.
        • What you actually want is to keep building campaigns yourself. That is not a lesser ambition, it is a different job, and this is not it.
        • None of these are preferences we bend on. They are how we screen, so applying anyway costs you an hour and gets you a no.
        But note nested
        inside
        • is not valid HTML. Better to keep as separate
          items without nesting. We can flatten: each bullet as a separate
          • . The "Please do not apply if:" could be a heading?