Community Lead (Discord / Reddit Community Operations)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must include sections only if posting has real specific content. The posting includes Position Summary (maybe About the role). It includes responsibilities (Community Build & Maintenance, Daily Moderation & Member Communication, Engagement Programs & Content, Operations Team Coordination, Reporting & Insights, Cross-Team Collaboration). It includes Requirements (list of bullet points). It includes Qualifications (Required and Preferred). It includes Benefits (some description). No Pay or Schedule info. So we should not include Pay or Schedule sections.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to preserve all substantive information. So we need to capture the Position Summary text as prose under About the role (or maybe we can call it About the role). The posting says "Position Summary". We'll map that to About the role.
Responsibilities: we have multiple sub-sections: Community Build & Maintenance, Daily Moderation & Member Communication, Engagement Programs & Content, Operations Team Coordination, Reporting & Insights, Cross-Team Collaboration. We can combine them into a single list under Responsibilities, each as
- with the description.
Requirements: The posting has a "Requirements" heading then bullet points (Community Build & Maintenance, Daily Moderation & Member Communication, Engagement Programs & Content, Operations Team Coordination, Reporting & Insights, Cross-Team Collaboration). Actually those are same as responsibilities? Wait reading: After Position Summary, there is a "Requirements" heading then bullet list that repeats the same categories as responsibilities? Let's examine: The text after Position Summary:
"Requirements Community Build & Maintenance Build and configure Discord servers and Reddit communities (subreddits) per the Community Management Manager's design. ..."
It seems they mislabeled: Actually they have "Requirements" then list of duty areas. Then later "QualificationsRequired". So we need to treat the "Requirements" section as duties/responsibilities? But we already have Responsibilities. The posting seems to have duplicated content: The "Requirements" section actually lists the same functional areas as responsibilities. Then "Qualifications" lists required and preferred qualifications.
Thus we need to extract substantive info: The "Requirements" section includes detailed descriptions of each duty area. We should treat that as Responsibilities (detailed). The "Qualifications" section includes Required and Preferred bullet points.
Thus we will have:
- About the role: Position Summary paragraph.
- Responsibilities: list items each with the detailed description from the Requirements section.
- Qualifications: maybe split into Required and Preferred? Could have two sub-sections? But we only have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Required under Qualifications, and Preferred under Skills? Or we could combine Required and Preferred under Qualifications as two lists. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and then inside we can have two maybe with headings? But we cannot add extra headings beyond those? Not prohibited but we should follow semantics. Could add inside? Safer to just have one list under Qualifications combining required and preferred? But we might lose distinction. However we can embed headings like inside? Not allowed? The instruction only says use for section headings (list). It doesn't forbid other headings, but to be safe we can just use
to label Required and Preferred.
Better: Use Qualifications section with two
paragraphs: one for Required, one for Preferred, each followed by
.
Similarly Skills: we could put any skills not covered? The posting includes some skills like "Native-level written English", "Reliable, detail-oriented", etc. Those are in Qualifications. Could also put under Skills. But we already have Qualifications covering them. We could leave Skills empty or omit. Since we should only include sections with real content, we can omit Skills if no distinct content beyond Qualifications. However the posting includes some skill-like items: "Basic graphic/video editing skills for community assets", "Japanese language ability". Those are in Preferred. So we can keep them under Qualifications Preferred.
Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we preserve all substantive info.
Let's extract the Position Summary paragraph:
"Position Summary The Community Lead is the hands-on operations lead for the official Discord servers and Reddit communities that 33 USA runs for Japanese anime, manga, and game IPs in the North American market. Reporting to the Community Management Manager, you will build and maintain communities, run day-to-day moderation, communicate with members, execute engagement programs, and coordinate the contractors and part-time moderators assigned to your communities. This is not a social media posting or account management role (X, Instagram, TikTok); it is the day-to-day operation of the community itself — the place where fans interact with each other on an ongoing basis. You will know every channel, role, bot, and rule in your communities and be responsible for keeping them healthy, active, and safe for fans to participate in. Working with the Social Media Marketing and Creative teams, you will support the Community Management Manager in preparing client reporting and in raising the operational quality of 33 USA's Community Management service."
We'll put that in under About the role.
Responsibilities: need to capture each bullet from Requirements section.
Let's extract each:
1. Community Build & Maintenance
- Build and configure Discord servers and Reddit communities (subreddits) per the Community Management Manager's design.
- On Discord: channels and categories, roles and permissions, onboarding and verification, bots, automod, and integrations.
- On Reddit: community settings, rules, flair, AutoModerator, and related tooling.
- Keep community settings, rules, FAQs, pinned content, and operating documentation up to date across assigned communities.
2. Daily Moderation & Member Communication
- Run day-to-day moderation: review channels and threads, apply community rules, handle reports, address spam and harmful content, and manage spoiler/leak control around release dates.
- Respond to member questions and welcome new members, creating a positive, on-brand community atmosphere in native-level English.
- Log incidents and escalate issues (harassment, ToS violations, PR-sensitive matters) to the Community Management Manager following the escalation flow.
3. Engagement Programs & Content
- Execute engagement programs planned with the Community Management Manager — release-linked activations, AMAs, watch parties, contests, polls, and creator/ambassador programs — including scheduling, announcements, and on-the-day operation.
- Draft community announcements and light content (Discord posts, event copy, Reddit posts) and coordinate visual assets with the Creative team.
4. Operations Team Coordination
- Coordinate the contractors and part-time moderators assigned to your communities: shift coordination, briefings, work direction, and first-line quality checks.
- Share training needs with the Community Management Manager.
5. Reporting & Insights
- Track community metrics (members, active rate, engagement, sentiment, incidents) and prepare inputs for weekly/monthly client reporting.
- Share member feedback, trends, and risks with the Community Management Manager and related teams to drive operational improvements.
6. Cross-Team Collaboration
- Align community activity with the Social Media Marketing team's content calendar and with IP release schedules and licensing constraints provided by clients and 33's Tokyo headquarters.
We'll put each as
- with the full description (maybe combine sub-bullets into one
- with line breaks? Could embed
inside - but simpler: each main bullet as
- and include the sub-points as separate sentences separated by semicolons or line breaks using
. But we can keep as plain text with line breaks.
Qualifications:
Required (list):
- 1–3+ years of hands-on experience operating or moderating a Discord server or Reddit community as an official community for a brand, IP, game title, or agency (required; experience on both platforms preferred).
- Personal fan communities or volunteer moderation alone do not qualify.
- Experience participating in the launch or initial build-out of an official community
- Working knowledge of Discord and Reddit administration (Discord: channels, roles and permissions, bots/automod; Reddit: community settings, AutoModerator, moderation tools; and both platforms' policies and Terms of Service)
- Experience handling moderation, reports, and incidents calmly and consistently, and following escalation flows
- Understanding of anime, manga, and/or game fandom culture and how North American fan communities behave online
- Native-level written English with a clear, friendly, on-brand community voice
- Reliable, detail-oriented, and comfortable with flexible hours around releases and live events
- Able to run day-to-day operations autonomously under the direction of the Community Management Manager
Preferred (list):
- Experience operating official communities for game or anime IPs (in-house or agency)
- Experience operating official communities on both Discord and Reddit
- Experience coordinating or scheduling moderators or contractors
- Familiarity with community analytics/reporting tools, Discord bot configuration, and Reddit AutoModerator setup
- Experience running AMAs, watch parties, contests, or similar live community events
- Basic graphic/video editing skills for community assets
- Japanese language ability, or experience working with Japanese clients or cross-border teams
- Experience on additional platforms (Twitch, YouTube community, Steam community, etc.)
We need to preserve all substantive info. Also note that the Required list includes a line "Experience participating in the launch or initial build-out of an official community" (no period). We'll keep as is.
Benefits section: extract:
"Benefits A number of programs cover all employees in the manner prescribed by law. Additionally, 33 USA Inc. provides several Company-designated benefit programs. Health Care Plan (Medical, Dental & Vision)Paid Time Off (Vacation, Sick & Public Holidays)Hybrid Work Model While we currently offer this hybrid arrangement, please note that our work model may evolve to meet changing business needs. The company reserves the right to modify work arrangements at its sole discretion. We appreciate your understanding and flexibility as we continually assess and optimize our work environment."
We need to format as prose maybe with . Could also list benefits as
items: Health Care Plan (Medical, Dental & Vision), Paid Time Off (Vacation, Sick & Public Holidays), Hybrid Work Model. Also note the statement about programs covering all employees per law, and company-designated benefit programs. We'll include that as prose.
We should not include Pay or Schedule.
Now produce HTML fragment:
About the role
...
Responsibilities
- Community Build & Maintenance: Build and configure Discord servers and Reddit communities (subreddits) per the Community Management Manager's design. On Discord: channels and categories, roles and permissions, onboarding and verification, bots, automod, and integrations. On Reddit: community settings, rules, flair, AutoModerator, and related tooling. Keep community settings, rules, FAQs, pinned content, and operating documentation up to date across assigned communities.
- Daily Moderation & Member Communication: Run day-to-day moderation: review channels and threads, apply community rules, handle reports, address spam and harmful content, and manage spoiler/leak control around release dates. Respond to member questions and welcome new members, creating a positive, on-brand community atmosphere in native-level English. Log incidents and escalate issues (harassment, ToS violations, PR-sensitive matters) to the Community Management Manager following
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive information. So we need to capture the Position Summary text as prose under About the role (or maybe we can call it About the role). The posting says "Position Summary". We'll map that to About the role. Responsibilities: we have multiple sub-sections: Community Build & Maintenance, Daily Moderation & Member Communication, Engagement Programs & Content, Operations Team Coordination, Reporting & Insights, Cross-Team Collaboration. We can combine them into a single list under Responsibilities, each as
- with the description.
Requirements: The posting has a "Requirements" heading then bullet points (Community Build & Maintenance, Daily Moderation & Member Communication, Engagement Programs & Content, Operations Team Coordination, Reporting & Insights, Cross-Team Collaboration). Actually those are same as responsibilities? Wait reading: After Position Summary, there is a "Requirements" heading then bullet list that repeats the same categories as responsibilities? Let's examine: The text after Position Summary:
"Requirements Community Build & Maintenance Build and configure Discord servers and Reddit communities (subreddits) per the Community Management Manager's design. ..."
It seems they mislabeled: Actually they have "Requirements" then list of duty areas. Then later "QualificationsRequired". So we need to treat the "Requirements" section as duties/responsibilities? But we already have Responsibilities. The posting seems to have duplicated content: The "Requirements" section actually lists the same functional areas as responsibilities. Then "Qualifications" lists required and preferred qualifications.
Thus we need to extract substantive info: The "Requirements" section includes detailed descriptions of each duty area. We should treat that as Responsibilities (detailed). The "Qualifications" section includes Required and Preferred bullet points.
Thus we will have:
- About the role: Position Summary paragraph.
- Responsibilities: list items each with the detailed description from the Requirements section.
- Qualifications: maybe split into Required and Preferred? Could have two sub-sections? But we only have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Required under Qualifications, and Preferred under Skills? Or we could combine Required and Preferred under Qualifications as two lists. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and then inside we can have two
- maybe with headings? But we cannot add extra headings beyond those? Not prohibited but we should follow semantics. Could add inside? Safer to just have one list under Qualifications combining required and preferred? But we might lose distinction. However we can embed headings like
- with the full description (maybe combine sub-bullets into one
- with line breaks? Could embed
- inside
- but simpler: each main bullet as
- and include the sub-points as separate sentences separated by semicolons or line breaks using
. But we can keep as plain text with line breaks. Qualifications: Required (list): - 1–3+ years of hands-on experience operating or moderating a Discord server or Reddit community as an official community for a brand, IP, game title, or agency (required; experience on both platforms preferred). - Personal fan communities or volunteer moderation alone do not qualify. - Experience participating in the launch or initial build-out of an official community - Working knowledge of Discord and Reddit administration (Discord: channels, roles and permissions, bots/automod; Reddit: community settings, AutoModerator, moderation tools; and both platforms' policies and Terms of Service) - Experience handling moderation, reports, and incidents calmly and consistently, and following escalation flows - Understanding of anime, manga, and/or game fandom culture and how North American fan communities behave online - Native-level written English with a clear, friendly, on-brand community voice - Reliable, detail-oriented, and comfortable with flexible hours around releases and live events - Able to run day-to-day operations autonomously under the direction of the Community Management Manager Preferred (list): - Experience operating official communities for game or anime IPs (in-house or agency) - Experience operating official communities on both Discord and Reddit - Experience coordinating or scheduling moderators or contractors - Familiarity with community analytics/reporting tools, Discord bot configuration, and Reddit AutoModerator setup - Experience running AMAs, watch parties, contests, or similar live community events - Basic graphic/video editing skills for community assets - Japanese language ability, or experience working with Japanese clients or cross-border teams - Experience on additional platforms (Twitch, YouTube community, Steam community, etc.) We need to preserve all substantive info. Also note that the Required list includes a line "Experience participating in the launch or initial build-out of an official community" (no period). We'll keep as is. Benefits section: extract: "Benefits A number of programs cover all employees in the manner prescribed by law. Additionally, 33 USA Inc. provides several Company-designated benefit programs. Health Care Plan (Medical, Dental & Vision)Paid Time Off (Vacation, Sick & Public Holidays)Hybrid Work Model While we currently offer this hybrid arrangement, please note that our work model may evolve to meet changing business needs. The company reserves the right to modify work arrangements at its sole discretion. We appreciate your understanding and flexibility as we continually assess and optimize our work environment." We need to format as prose maybe with. Could also list benefits as
- items: Health Care Plan (Medical, Dental & Vision), Paid Time Off (Vacation, Sick & Public Holidays), Hybrid Work Model. Also note the statement about programs covering all employees per law, and company-designated benefit programs. We'll include that as prose.
We should not include Pay or Schedule.
Now produce HTML fragment:
- Community Build & Maintenance: Build and configure Discord servers and Reddit communities (subreddits) per the Community Management Manager's design. On Discord: channels and categories, roles and permissions, onboarding and verification, bots, automod, and integrations. On Reddit: community settings, rules, flair, AutoModerator, and related tooling. Keep community settings, rules, FAQs, pinned content, and operating documentation up to date across assigned communities.
- Daily Moderation & Member Communication: Run day-to-day moderation: review channels and threads, apply community rules, handle reports, address spam and harmful content, and manage spoiler/leak control around release dates. Respond to member questions and welcome new members, creating a positive, on-brand community atmosphere in native-level English. Log incidents and escalate issues (harassment, ToS violations, PR-sensitive matters) to the Community Management Manager following
About the role
...
Responsibilities
inside? Not allowed? The instruction only says use
for section headings (list). It doesn't forbid other headings, but to be safe we can just use
to label Required and Preferred. Better: Use Qualifications section with two
paragraphs: one for Required, one for Preferred, each followed by
- .
Similarly Skills: we could put any skills not covered? The posting includes some skills like "Native-level written English", "Reliable, detail-oriented", etc. Those are in Qualifications. Could also put under Skills. But we already have Qualifications covering them. We could leave Skills empty or omit. Since we should only include sections with real content, we can omit Skills if no distinct content beyond Qualifications. However the posting includes some skill-like items: "Basic graphic/video editing skills for community assets", "Japanese language ability". Those are in Preferred. So we can keep them under Qualifications Preferred.
Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits.
We need to ensure we preserve all substantive info.
Let's extract the Position Summary paragraph:
"Position Summary The Community Lead is the hands-on operations lead for the official Discord servers and Reddit communities that 33 USA runs for Japanese anime, manga, and game IPs in the North American market. Reporting to the Community Management Manager, you will build and maintain communities, run day-to-day moderation, communicate with members, execute engagement programs, and coordinate the contractors and part-time moderators assigned to your communities. This is not a social media posting or account management role (X, Instagram, TikTok); it is the day-to-day operation of the community itself — the place where fans interact with each other on an ongoing basis. You will know every channel, role, bot, and rule in your communities and be responsible for keeping them healthy, active, and safe for fans to participate in. Working with the Social Media Marketing and Creative teams, you will support the Community Management Manager in preparing client reporting and in raising the operational quality of 33 USA's Community Management service."
We'll put that in
under About the role. Responsibilities: need to capture each bullet from Requirements section. Let's extract each: 1. Community Build & Maintenance - Build and configure Discord servers and Reddit communities (subreddits) per the Community Management Manager's design. - On Discord: channels and categories, roles and permissions, onboarding and verification, bots, automod, and integrations. - On Reddit: community settings, rules, flair, AutoModerator, and related tooling. - Keep community settings, rules, FAQs, pinned content, and operating documentation up to date across assigned communities. 2. Daily Moderation & Member Communication - Run day-to-day moderation: review channels and threads, apply community rules, handle reports, address spam and harmful content, and manage spoiler/leak control around release dates. - Respond to member questions and welcome new members, creating a positive, on-brand community atmosphere in native-level English. - Log incidents and escalate issues (harassment, ToS violations, PR-sensitive matters) to the Community Management Manager following the escalation flow. 3. Engagement Programs & Content - Execute engagement programs planned with the Community Management Manager — release-linked activations, AMAs, watch parties, contests, polls, and creator/ambassador programs — including scheduling, announcements, and on-the-day operation. - Draft community announcements and light content (Discord posts, event copy, Reddit posts) and coordinate visual assets with the Creative team. 4. Operations Team Coordination - Coordinate the contractors and part-time moderators assigned to your communities: shift coordination, briefings, work direction, and first-line quality checks. - Share training needs with the Community Management Manager. 5. Reporting & Insights - Track community metrics (members, active rate, engagement, sentiment, incidents) and prepare inputs for weekly/monthly client reporting. - Share member feedback, trends, and risks with the Community Management Manager and related teams to drive operational improvements. 6. Cross-Team Collaboration - Align community activity with the Social Media Marketing team's content calendar and with IP release schedules and licensing constraints provided by clients and 33's Tokyo headquarters. We'll put each as