Community Manager

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements/Qualifications (What We're Looking For), Benefits (What It's Like to Work at Darkroom includes benefits), Pay (Compensation), maybe Schedule? Not present. Also About Darkroom is company description; we might include as "About the company"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title. We need to include sections only when posting has real specific content. We have About Darkroom (company overview) - could be "About the company" but not listed; maybe we can include as a

before sections? 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 we should follow that pattern. Probably we should include About the role (the description after "About The Role") as a section. Then Responsibilities (What You'll Do). Then Requirements/Qualifications/Skills (What We're Looking For). Then Benefits (What It's Like to Work at Darkroom). Then Pay (Compensation). Possibly Schedule not present, so omit. Also we might include About Darkroom as a brief intro paragraph before sections (no heading). The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid having a heading like "About Darkroom". But they gave examples of headings; we could still use

for About Darkroom if we want, but not in list. Safer to just include a

for company overview. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is Equal Opportunity Statement; we should remove that. Also "What It's Like to Work at Darkroom" includes benefits etc; we keep that. We need to preserve all substantive information. So we need to include details about role, responsibilities, qualifications, benefits, pay. Let's extract: About Darkroom: paragraphs describing company. About The Role: description of role responsibilities high-level. What You'll Do: detailed bullet list (but in prose). We need to convert to

• for any list of duties/requirements/benefits. The "What You'll Do" section is a list of duties; we should turn each bullet into
• . The text includes multiple paragraphs with semicolons; we can split into logical items. We need to identify list items: "Build new communities", "Choose the platform...", "Set the entry rules...", "Build a proof channel...", "Run it every week", "Launches and drops", "In person", "Measure it". Each of these has subdetails. We could keep subdetails as part of the li content (maybe using

  inside li? but spec says use

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

    for prose. Likely they want each duty as

  • containing the description (maybe as plain text). We'll keep subdetails as part of the li text. Similarly "What Good Looks Like At 90 Days" maybe could be part of responsibilities? Not a list; could be prose. "What We're Looking For": list of qualifications; we should turn each bullet into
  • . "What It's Like to Work at Darkroom": benefits etc; we should turn each benefit into
  • under Benefits section. "Compensation": Pay section. We need to avoid headings with filler. Ensure we don't create empty sections. Let's craft HTML: Start with a

    for company overview (About Darkroom). Then

    About the role

    with

    containing the role description paragraph (the "About The Role" paragraph). Then

    Responsibilities

    with
    • items for each duty. Then

      Requirements

      (or Qualifications) with
      • items for each qualification. Then

        Benefits

        with
        • items for each benefit. Then

          Pay

          with

          containing compensation range. We should not include Schedule. We need to ensure we don't include duplicated lines. Let's extract details precisely. Company overview (About Darkroom): "Darkroom is the leading next-generation growth marketing firm engineering the brands of tomorrow. Founded in 2017, we set out to redefine what a modern agency could be, by replacing the inertia of legacy advertising behemoths with a model built for speed, intelligence, and measurable impact. At our core, Darkroom is a human services company powered by Shadow, a universal AI commerce layer that integrates executive-level strategy with proprietary agentic technology. This fusion enables our teams to deliver outsized returns by enhancing creative output, operational efficiency, and revenue generation across every stage of the customer journey. Our track record speaks for itself: billions in attributable revenue driven across e-commerce marketplaces, media networks, DTC ecosystems, and social commerce platforms. Every engagement feeds into our proprietary data infrastructure, enabling a continuous feedback loop that accelerates growth, improves margins, and compounds results across our client portfolio. What began as a boutique design studio has evolved into one of the fastest-growing private companies in America (Inc. 5000) and among the most effective performance media agencies of the 2020s (Varos). Our founders were recognized by Forbes 30 Under 30 for advancing the intersection of technology, marketing, and advertising, cementing Darkroom's role as a defining player in the future of media innovation." We'll put that in a

          . About The Role paragraph: "Darkroom owns creator strategy for the brands we work with, and more of them now want a community behind it: creators, customers, and fans who post because they want to, not because a brief told them to. This role builds those communities from zero and runs them as a growth channel. A community here is measured on what it produces outside itself: posts, content, referrals, and signups or sales. Most of our communities are tiered. A small inner circle of top creators gets money, early access, and a direct line to the brand. A larger ambassador tier gets access, perks, and first look at launches. Program tiers, like campus leaders or customer champions, run their own threads. And the open community is where everyone else joins. You decide how people get in, what each tier gets, what happens every week, and how activity turns into output. This is a consumer role. The people in these communities are students, parents, professionals, and fans, and a community run like a support forum or a developer channel will not work here. You report to a Director and work alongside the creator leads, the social team, paid media, and each client's product and brand teams. This role is based in New York, working US hours, with travel for events." We'll put that in

          under About the role. Responsibilities (What You'll Do) items: Let's parse: - Build new communities - Choose the platform for each community (usually Discord, sometimes Slack, WhatsApp, Geneva, Circle, or a subreddit) and stand it up: channel architecture, roles and permissions, bots, onboarding, tier assignment, and moderation rules. - Set the entry rules and the offer for each tier with the creator leads and the client, such as free product for creators over a follower threshold, student access, or referral perks. - Build a proof channel before launch, where members show what the product did for them. It is the flex wall, and the best posts get reposted by the brand. - Run it every week - Welcome new members, assign tiers, and post open briefs in #briefs with a clear view of who claimed what and when it is due. - Run the 1-in-20 triage: find the post that popped, work out why, and brief the rest of the roster on it the same week. - Repost the top receipts and hand the best ones to the social and paid teams. - Give members a real line to the brand. Route product questions, feedback, and bug reports to the client's team and bring the answers back. - Monthly: an AMA with someone from the brand, program leaderboards, and a roster health check (who is posting, who has gone quiet, and what you do about it). - Launches and drops - Every launch lands in the community first. You run the sequence: inner circle, then ambassadors and program tiers, then everyone else, in step with the social team. - Get real conversation going in the first two hours. No copy-paste. - In person - Co-run creator events with the creator leads, such as pre-launch dinners, launch parties, and campus or pop-up activations. - Recruit into the community on the spot, and make sure every event produces content. - Measure it - Report on each community as a growth channel: members by tier, weekly active share, proof posts per week, the share of ambassadors posting, and signups or sales attributed through community links and codes. - Write the SOPs as you go, so each program scales, transfers, and makes the next build faster. We could combine each top-level bullet as an

        • containing the subdetails as text (maybe using commas). To keep readability, we could keep sub-bullets as separate
        • but that would be nested lists; spec didn't forbid nested lists but said use
          • for any list of duties/requirements/benefits. Could do nested
            inside
            • . That's acceptable. We'll produce:

              Responsibilities

              • Build new communities
                • Choose the platform for each community (usually Discord, sometimes Slack, WhatsApp, Geneva, Circle, or a subreddit) and stand it up: channel architecture, roles and permissions, bots, onboarding, tier assignment, and moderation rules.
                • Set the entry rules and the offer for each tier with the creator leads and the client, such as free product for creators over a follower threshold, student access, or referral perks.
                • Build a proof channel before launch, where members show what the product did for them. It is the flex wall, and the best posts get reposted by the brand.
              • Run it every week
                • Welcome new members, assign tiers, and post open briefs in #briefs with a clear view of who claimed what and when it is due.
                • Run the 1-in-20 triage: find the post that popped, work out why, and brief the rest of the roster on it the same week.
                • Repost the top receipts and hand the best ones to the social and paid teams.
                • Give members a real line to the brand. Route product questions, feedback, and bug reports to the client's team and bring the answers back.
                • Monthly: an AMA with someone from the brand, program leaderboards, and a roster health check (who is posting, who has gone quiet, and what you do about it).
              • Launches and drops
                • Every launch lands in the community first. You run the sequence: inner circle, then ambassadors and program tiers, then everyone else, in step with the social team.
                • Get real conversation going in the first two hours. No copy-paste.
              • In person
                • Co-run creator events with the creator leads, such as pre-launch dinners, launch parties, and campus or pop-up activations.
                • Recruit into the community