Community Manager

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Must include only sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include sections with placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes compensation: "Compensation: The base salary range for this role is $60,000-$65,000 per year." So we can have Pay section with that. Benefits: they list Unlimited PTO + US holidays, Remote-First Culture, Health & Wellness, Finances, growth, and retirement (401k with match and profit-sharing), Parental Leave, Growth. So Benefits section can include those. Schedule: they mention "This role is based in New York, working US hours, with travel for events." Also "Available for evenings and launch weekends when the community is most active, and able to travel." So schedule: working US hours, evenings/weekends, travel. So we can include Schedule section. We need sections: About the role (the description after "About The Role") maybe also "What You'll Do" as Responsibilities. "What Good Looks Like At 90 Days" maybe as Expectations? Could be part of Responsibilities or Qualifications? But we need to follow allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have "About The Role" paragraph describing role. That's About the role. "What You'll Do" list of duties => Responsibilities. "What Good Looks Like At 90 Days" could be considered part of Responsibilities or maybe Qualifications? But we can include as a separate section? Not allowed headings besides those. Could incorporate into Responsibilities or maybe Qualifications? Probably better to put under Responsibilities as expected outcomes. "What We're Looking For" list => Requirements or Qualifications? Could be Requirements. Also "Bonus Points" could be Qualifications or Skills. We need to decide. We have "What It's Like to Work at Darkroom" includes culture, benefits etc. Benefits we already have separate. We have "Compensation" => Pay. We have schedule info. We need to avoid boilerplate: remove Equal Opportunity Statement, etc. We must preserve all substantive info. So we need to include all details from sections we keep. We must not repeat job title. We must not include Job ID etc. We must not include cookie/navigation/legal/EEO etc. We must output only HTML fragment. Let's extract content. About Darkroom intro: maybe not needed? The posting includes "About Darkroom" at top. That's company overview. Could be part of About the role? Probably not needed but it's substantive info about company. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include company overview maybe as a paragraph before sections? There's no heading for company overview, but we could include as a

before sections. The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other

content outside sections. So we can include a brief intro paragraph about Darkroom. Thus output:

About Darkroom ...

then

About the role

with paragraph(s). Then

Responsibilities

with

• ... etc. Then

  Requirements

  with list. Then

  Benefits

  with list. Then

  Pay

  with paragraph. Then

  Schedule

  with paragraph. We must not include sections like Qualifications, Skills if not needed. But we have "What We're Looking For" which includes both requirements and bonus points. Could split: Requirements = must-haves; Bonus Points = nice-to-haves (could be Skills). But we have allowed headings Skills. Could put bonus points under Skills. But we need to decide. Let's parse "What We're Looking For": - You have built and run an online community for a consumer product, ideally one that grew fast. This is the most important thing on this list. Running a Discord at thousands of members is a strong signal. Moderating someone else's community is not the same thing. - You know what makes people post. You can say why one post gets reshared and another does not, and turn that into a brief other people can use. - Fluent in creator culture across TikTok, Instagram, YouTube, and X, and comfortable with everyone from a college sophomore to a creator with a million followers. - Technical enough to own the setup yourself: roles, permissions, bots, onboarding flows, and automations. - You write like a person. You can hold one voice across a server, DMs, and a room. - Organized for volume: hundreds of people joining in a launch week, more than one community at a time, nothing dropped. - Calm when something goes wrong, like a product issue at launch or a creator complaining in public. You handle it and know what to escalate. - Comfortable with clients. You can explain what the community is doing for their business and push back when a request would hurt it. - AI-native. Our team works alongside AI for moderation, triage, analytics, and drafting, and you should be excited to build workflows with it. - Available for evenings and launch weekends when the community is most active, and able to travel. Bonus Points: - You launched a community or ambassador program for a consumer app, AI product, or DTC brand. - You ran a campus ambassador or student program. - You have built an audience of your own, on any platform. - Event production experience. - Agency experience, or experience working directly with a client's product team. - Familiarity with Notion, our operating layer. Thus we can treat Requirements as the bullet list under "What We're Looking For". Skills could be the Bonus Points? Or we could put Bonus Points under Skills. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Skills into one section? But we have headings for both. Could make Requirements include the must-haves, and Skills include the bonus points. That seems reasonable. Thus:

  Requirements

  with the must-haves bullets.

  Skills

  with bonus points bullets. Now Benefits: list from "What It's Like to Work at Darkroom": Unlimited PTO + US holidays, Remote-First Culture (many roles fully remote; employees based in or near New York or Lisbon HQs expected to work hybrid with weekly in-office time; hub locations include Brazil and Spain), Health & Wellness (company-sponsored medical, dental, and vision coverage), Finances, growth, and retirement (robust 401(k) program with company match and profit-sharing opportunities), Parental Leave (flexible parental leave), Growth (interdisciplinary model gives exposure beyond core role, grow skills, expand influence, stay at forefront). Also maybe "Unlimited PTO + US holidays: Rebooting is part of the work. Take the time you need to stay sharp." We'll capture. Pay: base salary range $60,000-$65,000 per year. Schedule: "This role is based in New York, working US hours, with travel for events." plus "Available for evenings and launch weekends when the community is most active, and able to travel." So schedule: US hours, evenings/weekends availability, travel for events. Now About the role: we need to include the paragraph(s) from "About The Role". Let's extract that section: "About The Role 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 already used schedule info; but we can keep that in About the role as well, but schedule section will also have it. Might duplicate but okay. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original. But we could keep schedule info only in schedule section and not repeat in About the role? But About the role includes that sentence; we could keep it there as part of description. It's fine. Now Responsibilities: from "What You'll Do". Need to break into bullet list. Let's extract bullet points: - 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 need to convert to