Module 10: Find a Job
Employed community roles have grown up: brands, SaaS companies, and gaming studios now hire people specifically to keep members active and renewing. The pay bands are real, the screening is evidence-based, and the interview is often a live problem talked through out loud. This module walks the employed track end to end: where the roles are, how to apply with proof, how to handle the scenario interview, and how to negotiate and land the first 30 days.
Employed paths: brand, SaaS, and gaming
Know the ladder before you apply to it. At the bottom sit moderator and community associate roles — coverage, first responses, escalation — paying roughly $38,000–52,000. The mid-market is the community manager proper: owning onboarding, programming, and retention for one community. A live 2026 posting for a Discord community manager at a sports brand listed $60,000–75,000 plus equity, which is a fair picture of where a solid mid-level role lands. Above that, leads and heads of community run moderator teams and own the retention number across products; one web3-sector example puts those roles at $80,000–110,000 — treat that as one sector's top end, not a universal band, but it shows where the ladder tops out.
The employers differ in what they're really buying. Brands and creator businesses want a host — someone whose daily presence makes a paid group feel worth the subscription. SaaS companies run user communities that deflect support tickets and feed product feedback, so they screen for reporting and cross-team communication. Gaming studios run the largest, fastest Discords and screen hardest for moderation judgment under pressure, often across time zones and weekends.
Read postings for the hidden job description. "Grow our community" with no mention of retention usually means the company hasn't figured out the role yet — not automatically a no, but your interview questions need to find out who owns churn. Posts that name metrics, a moderator team, and a community platform by name are the ones written by people who know what they're hiring.
Two postings land in your inbox. Role A: "Community Manager, $45K — grow our Discord to 100,000 members!" Role B: "Community Manager, $68K — own onboarding and retention for our paid member community; monthly churn reporting; manage two part-time moderators." Which is the stronger opportunity, and why?
Applications: evidence, not enthusiasm
Community job posts get flooded with applications that say some version of "I'm passionate about community and I'm in a lot of Discords." Hiring managers screen those out in seconds. What survives the screen is evidence: communities you have actually run, moderated, or measurably improved. Your audit, spec launch plan, and case studies from Module 8 are the application, and the résumé is just the cover sheet that points at them.
Write résumé bullets as outcomes with numbers: "Moderated a 1,200-member Discord for an indie game; cut unanswered-question threads from most days to near zero by building a reply rota." "Rebuilt onboarding for a paid course community; first-week intro-post rate rose and the owner reported steadier renewals the following quarter." If your experience is freelance or volunteer so far, say so plainly and let the numbers carry it — a small community you genuinely improved beats a famous server you merely hung out in.
Tailor the proof to the post. Applying to a SaaS role? Lead with the case that shows reporting and member-journey mapping. Gaming? Lead with the moderation story — the conflict you handled well, told with the ladder: nudge, DM, documented step. And include the link to your portfolio in the first three lines of every application. The evidence only works if it's one click away when the screener decides.
You're applying for a gaming studio's community role. Your background: two years moderating a mid-size Discord for a streamer, plus freelance work for one course community. Which lead for your application does the most work?
The scenario interview: think out loud
Community roles are screened with scenarios because the job is scenarios. Expect some version of: "It's 9 p.m., a popular member is publicly accusing the company of scamming people, the thread is moving fast, and your manager is offline. Walk me through what you do." There is rarely one right answer. There is a right order, and they are listening for it: slow the thread down, follow the moderation ladder, move the person to a private channel, document everything, escalate with facts — never improvise policy in public at speed.
Talk out loud in the same structure you'd write a case study. State what you'd check first ("Is this a first offense? What's their history? Is any of the complaint true?"), then your first move and why, then what happens next, then what you'd hand your manager in the morning. Naming the trade-offs out loud — "I could lock the thread, but that reads as silencing, so I'd slow-mode it and post one calm reply first" — is what separates a manager's answer from a moderator's. Moderators reach for the ban button in scenario answers. Managers reach for the record, the relationship, and the ladder.
Prepare three true stories before any interview: a conflict you handled, a quiet community you woke up, and a member problem you caught early through the numbers. Every scenario they invent will rhyme with one of your three, and a real story told in order — baseline, moves, outcome — will always beat a hypothetical answered perfectly.
Interview scenario: a long-time, well-liked member posts a furious public thread saying the newest course module is "a scam," and other members are piling on. The hiring manager asks what you'd do. What's the strongest answer?
Negotiating pay and your first 30 days
Negotiate from the bands, not from hope. Associate and moderator roles cluster around $38,000–52,000; proven mid-level managers land where that sports-brand Discord posting sat, $60,000–75,000, sometimes with equity at startups. If an offer prices manager-level scope — owning onboarding, programming, and retention — at associate money, name the gap with the evidence in front of you: "This scope matches the mid-level postings at $60–75K; here's the portfolio that shows I've done that scope." If salary is truly capped, negotiate the edges: the title (manager over associate follows you for years), a six-month review tied to retention targets, coverage-hour boundaries, and a training budget.
Then earn the number in the first 30 days. Days 1–7: listen. Read the history, learn the superusers' names, take the member journey yourself, change nothing visible yet. Days 8–14: baseline. Pull the numbers — active members, posts per active member, churn if it's a paid group — and write them down somewhere your manager sees. Days 15–30: one fix, shipped. Pick the clearest leak from your baseline (it's usually onboarding or unanswered first posts), fix it, and report the early movement in the format from Module 7: health, risks, one recommendation.
The pattern underneath all of it: the managers who get promoted are the ones whose work shows up as a retention number in someone else's report. Make your first month produce that sentence, and the six-month review conversation mostly conducts itself.
A SaaS company offers you a community manager role at $46,000. The job, as described in interviews, is owning onboarding and retention for their paid user community and reporting churn monthly. What's the strongest negotiation move?
What you can now do
- Place any job post on the employed ladder — associate coverage money versus manager-level scope — before you spend an application on it.
- Apply with evidence: your community audit, spec launch plan, and framed case numbers up front, not a claim that you're passionate about community.
- Talk a scenario interview out loud in the right order — slow the thread down, work the moderation ladder, escalate — and negotiate inside the real pay bands for the rung.