How to recruit Discord moderators: from the first post to the first week
Recruiting Discord moderators is a short process with a few steps that people tend to skip: decide what you need, post where the right people are, ask the same questions of everyone, review with someone else, and start with a trial. A common mistake is to pick the most active member and call it done. This guide takes you from the first post to the end of the first week.
Decide what you actually need
Before you post anything, write down why you're recruiting. "We need more mods" isn't a reason. These are:
- Coverage: nobody is online between midnight and 8 am UTC.
- Volume: reports stay unanswered for hours.
- A skill: nobody knows how to set up your automod.
- A language: a growing part of your members speak Spanish.
Your answer tells you how many people you need, in which time zones, and what the role involves. It also gives you an honest job description: hours per week, what they can and can't do, and who they report to. Writing it down takes ten minutes and saves weeks.
When to open applications
Open them when you have the time to read them. A recruitment post followed by two weeks of silence does more harm than no post at all.
Use a window, such as seven days, or a fixed number of spots. That gets you more applications at once, makes it easier to compare people, and gives you a natural moment to answer everyone. When the window ends, close the form. In Toscio, closing it from the dashboard shows that applications are closed on the panel, and reopening takes one click.
Where to post
Start inside your server, because the people who already know your rules are your best candidates:
- an announcement with what you're looking for, and when applications close;
- a pinned message or a panel in a dedicated channel;
- a direct word to two or three members you've noticed. Don't promise them anything: they should still apply.
If you need to look outside, a link works where an invite can't. Toscio's web form gives each form a public page, and your server gets a recruitment page you can post anywhere. In the dashboard, make one link for each place you post, and you'll see which one brought applicants.
What to ask
Keep the written application short and practical. You want facts, and one situation that shows how they think. The staff application questions go through each question and what a good answer looks like. At a minimum, ask about:
- availability, in hours and time zones;
- past experience, if any. No experience isn't a no;
- why they want the role;
- a real situation from your server: two members arguing, a friend breaking a rule.
A quiz on your rules is a quick first filter. It catches people who never read them, without anyone having to read an application.
Review as a team
Don't decide alone, and don't decide in a hurry. Read the applications in a private channel, and write down why, not only what. If a friend of yours applies, let someone else review them.
Use the same three questions for every candidate: are they fair, are they calm, are they available? It keeps the discussion on the job, not on who is most popular. For a team of more than four or five, staff votes give you a clear rule for when a decision is final.
Look at the person's history on your server too. Someone who's been there for months with no warnings is a known quantity. Toscio shows the account age, the time on the server and past applications on the card.
Interview the shortlist
An interview shows what an application can't: how someone reasons on the spot, and how they talk to you. Fifteen minutes is enough. The moderator interview questions include a scoring grid, so that two reviewers can compare notes.
Answer every candidate who didn't make it. A short, honest message keeps them in your community, and they might be your next moderator. The rejection message templates give you something to start from.
Start with a trial
Nobody knows how a moderator will act until they're acting. A trial period lowers the stakes for you and for them: limited permissions, a mentor, and a clear end date. Two to four weeks is a good starting point.
The trial moderator guide covers it in detail. With a stage in Toscio, the first Accept gives @Trial Mod and the second gives the full role. Set an end date, and your staff are alerted two days before it arrives.
The first week
A new moderator who doesn't know what to do soon stops doing anything. In the first week:
- Give them the basics: the staff rules, the penalty ladder, where to log actions, who to ask.
- Pair them with someone they can message without feeling silly.
- Have them watch first. Let them see a few cases handled before they act alone.
- Check in at the end of the week. Ask what's unclear, and listen.
- Introduce them to the community, so that members know who they are.
After the trial
Decide on the date you promised. If it went well, say so and give the full role. If it didn't, end it kindly and tell them why. Then look back at where your good moderators came from, so that the next recruitment is easier. And if someone leaves the team, follow the staff offboarding checklist, so that no access stays behind.
Questions
How many moderators does a Discord server need?
There's no fixed ratio. Look at when messages go unread and which hours have nobody on duty. Two moderators in different time zones help more than five in the same evening.
Should I recruit from my members or from outside?
From your members first. They know the culture, and you've seen how they behave. Look outside only for a skill nobody has, such as running bots, or when the server is new.
Should moderators be paid?
Community moderators are usually volunteers. If you have a budget, say so in the post. If not, be open about what you offer in its place: trust, access, a voice in decisions.
How old should a moderator be?
Your rules decide, within Discord's minimum age. Judge maturity from answers and behavior, and be careful about which private data you ask for, since many applicants are minors.


