Back to portfolio
Community & GrowthSimulated project
Community Moderator portfolio brief
A simulated community & growth exercise for Community Moderator. Treat it as realistic practice, not real client or protocol work.
5 deliverables5 tools referenced3 linked interview questions
Objective
Moderate a real community under clear supervision
Expected deliverables
Moderation logEscalation ticketIncident summaryUpdated FAQ or macroShift handoff note
Recommended workflow
- Moderate a real community under clear supervision
- Write an escalation matrix for scams, bugs, account issues, and policy disputes
- Turn three anonymized incidents into short case studies explaining the decision and outcome
- Review the result against the rubric, then package it as a case study.
Constraints and safety
- Use only public sources or clearly simulated data.
- Never include seed phrases, private keys, or wallet secrets.
- Redact private user, company, security, legal, or compensation information.
- State every assumption you make.
Tools in practice
- Discord
- Monitor reports, apply channel rules, answer from approved sources, and leave a clean handoff for the next shift.
- Telegram
- Monitor reports, apply channel rules, answer from approved sources, and leave a clean handoff for the next shift.
- Notion
- Draft, review, and maintain moderation log and escalation ticket, with owners, source links, and change history.
- Google Sheets
- Structure the records behind moderation log and escalation ticket and make review status visible.
- Zendesk or Linear
- Track decisions, dependencies, bugs, and owners connected to moderation log and escalation ticket; the ticket is a coordination record, not the work itself.
What a strong submission shows
- A moderation SOP with escalation levels
- An anonymized incident log
- A phishing-response flow
- A launch coverage plan
Weak submission patterns
- Screenshots showing high message volume with no explanation of decisions
- Claims that being active in Discord equals moderation skill
- Generic community growth charts
Review rubric
- Accuracy of claims and sources
- Relevance to the target role
- Decision quality and trade-offs
- Completeness of the deliverable
- Clarity of communication
- Honest limitations and next steps
Present it as a case study
- Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
- Show the final artifact before the process notes.
- State what you owned and what belonged to other people.
- Label the work as simulated, and keep any real contribution clearly separate.
Interview questions this project helps you answer
A scam link appears during a token launch. What do you do in the first five minutes?
When should a moderator answer directly, and when should the issue move to support, security, or leadership?
How would you keep enforcement consistent across several moderators and time zones?