Most of your day is spent talking to people who don't work for your company. You run the forum, the Discord server or the customer Slack, and you turn what members say into something the product and marketing teams can use. It's part host, part moderator and part analyst, and the mix shifts every hour.
This day follows a community manager at a software company with an online member community. The company runs a Discord server for everyday chat, a Discourse forum for longer questions, and a monthly live session on Zoom. At a consumer brand, a nonprofit or a gaming studio the tools change, but the rhythm is close. You check the rooms, you answer and route, you plan something for members, and you report back to people inside the company who've never once logged into the server.
You open Discord and the forum before email. Members in other time zones posted while you slept, so there's a backlog: a bug report with screenshots, a heated thread about a pricing change, and a spam account that got past the verification bot. You ban the spammer, pin a holding reply on the pricing thread, and tag the bug report for support. Then coffee.
You join the weekly product meeting with a short doc in Notion. It lists the requests members raised most often this week, with links to the threads. Engineers push back on one of them. You don't argue the roadmap, you bring the member's own words and let them land. Getting product people to read that doc is half the job.
A popular member posts a screenshot claiming the company is quietly deleting accounts. It's wrong, but it's spreading. You drop the event prep, ping support and the comms lead in Slack, confirm what actually happened, and write a calm reply that says what you know and when you'll know more. You stay in the thread for the next hour answering follow-ups one by one.
Back to Thursday's live session. You confirm the guest speaker, schedule the reminder posts in Sprout Social, and message a few longtime members to ask if they'll share how they use the product on air. Most say yes, one ghosts you. You also approve a new volunteer moderator after a short call.
You pull a quick report from Discord's server insights and the forum admin panel: new members, posts, threads with no reply. You note which channels went quiet and flag the account rumor for tomorrow's check. Before you log off, you leave a note for the volunteer mods covering the evening, because the community doesn't close when you do.
The hardest part isn't the angry posts. It's being the person members trust while having no power over the product. You'll carry a request to the roadmap meeting for months and watch it slip, and the members will ask you, not the product manager, why nothing happened. Some people also burn out on being always reachable. The ones who last set clear moderation rules early, train volunteers, and write down what counts as an emergency so not every ping is one.
This is the route you'll see most. Support reps already know the product, the common complaints and the tone that calms people down. Volunteering to answer forum threads or host office hours is the usual bridge.
Social media coordinators and content writers move over when a company wants conversation, not just posts. You'll need to show you can run a space with rules and regulars, not only schedule updates on Instagram or LinkedIn.
Plenty of community managers started as the most helpful person in a Discord server, a subreddit or a user group, then got hired by the company behind it. A moderator history with real examples of disputes you handled is a strong portfolio.
7% of openings are fully remote.
$80,000 – $90,000
Typical range in the 28 of the newest 60 postings that list pay.
Not quite. A social media manager mostly publishes to channels the company doesn't own and measures reach. A community manager runs a space where members talk to each other, like a forum or Discord server, and cares more about whether people come back and help one another. Some small companies roll both into one job, so read the posting closely.
Usually not. Postings often mention a degree in marketing or communications, but hiring managers weigh proof that you've run a real community much more. Moderation history, events you hosted and a writing sample tend to matter more than the diploma.
It depends on the company. Common ones are active members, how fast questions get answered, how many answers come from other members, and how much the community feeds product ideas or deflects support tickets. Ask in the interview which ones your boss reports upward, because that shapes your whole week.
HeroApply applies to them for you, so you can keep doing the job you have.