Question 1

Tell me about a community you've built or grown. What did it look like when you started and when you left?

Accepted Answer

They want a real before and after, told by someone who knows what changed and why. This question sorts people who ran a community from people who posted in one. Name the platform and the audience, like a Discourse forum for customers or a Slack group for partners Describe the starting state in plain terms: quiet, noisy, run by one loud power user Walk through the few moves you made, such as a welcome thread, a weekly office hour, a member spotlight Say what changed in behavior, like members answering each other before staff did Admit one thing that didn't work and what you dropped

Question 2

How do you decide what counts as success for a community?

Accepted Answer

Leadership will ask this about your work every quarter. They need to know you can tie the community to something the business cares about, not just activity. Start from the company's goal: fewer support tickets, better retention, product feedback, word of mouth Pick signals that match it, like threads solved by members or active members who renew Explain where you'd pull the data, such as the platform's admin analytics, a CRM like HubSpot or a tagging system Say which vanity signals you'd report but not steer by

Question 3

A thread blows up with angry members after a price change or outage. Walk me through your first hour.

Accepted Answer

This happens in every community sooner or later. They're checking whether you stay calm, get facts first and avoid making promises you can't keep. Acknowledge the thread quickly with a short, human reply so members know someone's there Get the facts from support, engineering or leadership before saying anything specific Keep the conversation in one place instead of deleting or scattering it Post a real update when you have one, and say when the next one is coming Afterward, share what members said with the team that made the call

Question 4

How do you write and enforce community guidelines?

Accepted Answer

Moderation is where community managers win or lose trust. They want to know you can be fair, consistent and not heavy-handed. Keep the rules short and written in plain language members will actually read Use a ladder: a friendly nudge, a warning, a timeout, then a ban Log actions so decisions are consistent across moderators Explain how you handle a well-liked member who breaks a rule

Question 5

How do you work with volunteer moderators or superusers?

Accepted Answer

Most communities can't be run by one person. They want to see you can recruit, guide and keep volunteers without burning them out or letting them go rogue. Describe how you spot candidates: helpful, patient, already answering questions Give them a clear role, a private channel and a short playbook Thank them in ways that matter, like early access, swag or a direct line to the product team Say how you'd handle a moderator who starts abusing their role

Question 6

How do you get product feedback from the community to the people who build the product?

Accepted Answer

A lot of companies fund a community partly for this. They want to know feedback won't die in a thread. Tag and group requests instead of forwarding every post Bring a short summary to a regular product meeting, with links to real threads Log requests where the product team already works, like Jira or Productboard Close the loop publicly when something ships or gets turned down

Question 7

What's a piece of community programming you ran that worked, and one that flopped?

Accepted Answer

Programming is the part of the job that keeps a space alive between launches. They want someone who tests ideas and drops the ones that don't land. Name the format: an AMA with an engineer, a monthly challenge, a local meetup, a livestream Explain why the good one worked in terms of what members got out of it Be honest about the flop and what you think went wrong Say what you'd change next time

Question 8

How would you spend your first few weeks here?

Accepted Answer

They're checking whether you'll listen before you change things. New community managers who launch a rebrand in week one tend to upset the regulars. Read old threads and lurk in the channels to learn the norms Meet the most active members and the internal teams who rely on the community Find the loudest pain points and the easy fixes Share a short plan with your manager before making big changes

Question 9

Tell me about a time you had to push back on a request from marketing or leadership.

Accepted Answer

Other teams will want to use the community as an ad channel. They need someone who protects members' trust without being difficult. Describe the request, like a sales push posted as if it came from a member Explain the risk in terms the other team cares about Offer an alternative that still gets them something Say how it ended and whether the relationship held up

Question 10

How do you keep from burning out in a job where people can message you at any hour?

Accepted Answer

This is the part of the job people hate most. Hiring managers have watched good community managers quit from exhaustion. Set posted hours and say when members can expect a reply Use scheduling and saved replies in tools like Sprout Social or the platform's own tools Share coverage with moderators or support on weekends Admit a time you didn't manage it well and what you changed

Question 11

Write a reply to this frustrated post.

Accepted Answer

Tone is the job. A live writing test shows in minutes whether you sound human, stay on brand and actually help. Open by showing you read what they wrote, in your own words Give a real next step or a real answer, not a policy quote Keep it short and skip the corporate apology language Invite them to a direct message if details are private

Community Manager interview questions and how to answer them

The 8 questions you will almost certainly get

A forgettable answer, and a better one

"Tell me about a community you've built or grown. What did it look like when you started and when you left?"

"How do you decide what counts as success for a community?"

Questions to ask them

Need more Community Manager interviews to prep for?

The question	What they want to know	Your angle
Tell me about a community you've built or grown. What did it look like when you started and when you left?	They want a real before and after, told by someone who knows what changed and why. This question sorts people who ran a community from people who posted in one.	Name the platform and the audience, like a Discourse forum for customers or a Slack group for partners
How do you decide what counts as success for a community?	Leadership will ask this about your work every quarter. They need to know you can tie the community to something the business cares about, not just activity.	Start from the company's goal: fewer support tickets, better retention, product feedback, word of mouth
A thread blows up with angry members after a price change or outage. Walk me through your first hour.	This happens in every community sooner or later. They're checking whether you stay calm, get facts first and avoid making promises you can't keep.	Acknowledge the thread quickly with a short, human reply so members know someone's there
How do you write and enforce community guidelines?	Moderation is where community managers win or lose trust. They want to know you can be fair, consistent and not heavy-handed.	Keep the rules short and written in plain language members will actually read
How do you work with volunteer moderators or superusers?	Most communities can't be run by one person. They want to see you can recruit, guide and keep volunteers without burning them out or letting them go rogue.	Describe how you spot candidates: helpful, patient, already answering questions
How do you get product feedback from the community to the people who build the product?	A lot of companies fund a community partly for this. They want to know feedback won't die in a thread.	Tag and group requests instead of forwarding every post
What's a piece of community programming you ran that worked, and one that flopped?	Programming is the part of the job that keeps a space alive between launches. They want someone who tests ideas and drops the ones that don't land.	Name the format: an AMA with an engineer, a monthly challenge, a local meetup, a livestream
How would you spend your first few weeks here?	They're checking whether you'll listen before you change things. New community managers who launch a rebrand in week one tend to upset the regulars.	Read old threads and lurk in the channels to learn the norms