Community Management Manager

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes Position Summary (which could be About the role). It includes Responsibilities (the bullet points under Position Summary? Actually the Position Summary describes responsibilities). Then there is a "Requirements" section with many bullet points. There's also "Preferred Experience" which could be Qualifications or Skills? The posting includes "Benefits" section. No Pay or Schedule mentioned. So we should include sections: About the role (or maybe "Position Summary" as About the role), Responsibilities, Requirements, Qualifications (maybe Preferred Experience), Benefits. We must not repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. The posting includes a Benefits paragraph with bullet-like sentences but not actual list; we can turn into

  • . The Benefits paragraph: "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 parse that into list items: Health Care Plan (Medical, Dental & Vision), Paid Time Off (Vacation, Sick & Public Holidays), Hybrid Work Model (with note). Could also include the statement about programs covering all employees per law. Might be better to keep as prose? The instruction: Use
    • for any list of duties/requirements/benefits. So we should list benefits as list items. We need to avoid repeating job title. No mention of Pay or Schedule, so omit those sections. We need to ensure we don't create sections with filler text. All sections have content. Now we need to extract responsibilities from Position Summary and the bullet-like paragraphs under Requirements? Actually the Position Summary includes responsibilities: designing community structure, rules, moderation frameworks, etc. Also includes managing contractors, reporting to CEO, etc. We'll capture those as list items under Responsibilities. The Requirements section includes many bullet-like sentences (some are required, some preferred). We need to separate Required vs Preferred? The instruction: Use sections like Requirements, Qualifications, Skills. We could put required experience under Requirements, and preferred experience under Qualifications or Skills. But we need to decide. The posting has "Required Education and Experience Requirements:" then a list of required items (some with sub-items). Then "Preferred Experience:" list. Thus we can make:

      Requirements

      with
      • for each required bullet.

        Qualifications

        for preferred experience. Alternatively we could put Skills section for specific skills like Deep understanding of Discord and Reddit mechanics etc. But those are also in required list. Might be better to keep as Requirements (required) and Qualifications (preferred). We'll not duplicate. Now we need to preserve all substantive information, not invent or summarize away detail. So we must include each required bullet exactly as given (maybe rephrase slightly but keep meaning). Must not omit any. Let's list required bullets: - 3+ years of hands-on experience designing, launching, and operating BOTH Discord servers and Reddit communities as official communities for a brand, IP, or game title (required). Personal fan communities or volunteer moderator participation alone do not qualify. - A track record of launching multiple official communities from scratch and operating them on an ongoing basis (required) - One of the following (required; (a) is weighted most heavily): (a) agency-side experience running Discord/Reddit community operations for game clients, (b) in-house community operations (Discord/Reddit) at a game company, or (c) experience at an agency specializing in Discord/Reddit community operations - Experience personally establishing community rules, moderation policies, and escalation flows, and leading incident and crisis response - Experience building a team of moderators, contractors, or part-time staff and providing direction, training, review, and quality control - Deep understanding of Discord and Reddit mechanics and tooling (Discord: roles and permissions, bots and automation, verification; Reddit: subreddit configuration, AutoModerator, moderation tools; and both platforms' policies and Terms of Service) - Experience designing KPIs and delivering data-based community evaluation and reporting - Deep understanding of anime, manga, and/or game fandom culture and how North American fan communities form and behave - Native-level English, including public-facing community communication and client proposals and reporting - Ability to work autonomously as a founding member of a new service line and build processes and structures from zero Now preferred experience bullets: - Experience launching a community management service or team inside an agency (service design, packaging, pricing, playbooks) - Experience operating official communities for Japanese anime, manga, or game IPs in North America - Experience participating in client proposals and sales meetings, and serving as the primary client contact after award - Business-level Japanese, or experience working with Japanese clients and cross-border teams - Experience collaborating with platform partner contacts or Trust & Safety teams at Discord, Reddit, etc. - Experience with community analytics/reporting tools, Discord bot development/configuration, and advanced Reddit AutoModerator setup - Familiarity with Japanese IP licensing and approval workflows - Experience operating additional community platforms (Twitch, YouTube community, Steam community, etc.) Now responsibilities from Position Summary: Let's extract bullet-like responsibilities: - Builds from the ground up and leads 33 USA's new Community Management service — the operation of official Discord servers and Reddit communities for Japanese anime, manga, and game IPs in the North American market. - Designing and running the community itself — the place where fans interact with each other on an ongoing basis. - Designing community structure and rules, building moderation and governance frameworks, creating an environment where fandoms can participate and interact safely, and planning and executing ongoing engagement programs. - As a founding member of this function, you will define the service offering, operating playbooks, moderation policies, quality standards, and reporting methods, and you will grow into the lead accountable for all community management engagements. - Part of the day-to-day moderation and community operations will be handled by contractors and part-time moderators. In addition to understanding and being able to perform the work yourself, you will need the management skills to direct, review, and develop less-experienced team members and to build a team and system capable of running multiple communities at a consistent level of quality. - Reporting directly to the CEO, you will work closely with the Business Development, Social Media Marketing, and Creative teams in both the US and Japan, and serve as 33 USA's subject-matter expert in community management — connecting Japanese IP holders, platforms such as Discord and Reddit, and North American fan communities. We could also include Japan–US Collaboration responsibilities? That's under a heading "Japan–US Collaboration" which is part of responsibilities. It includes: - Work with 33's Tokyo headquarters and Japanese clients to understand IP marketing strategies, release schedules, promotion plans, and licensing/rights constraints, and reflect them in North American community strategy and operating plans. - Using interpreter/bilingual staff support as needed, accurately understand the intent and requirements of the Japan side and bridge them with the culture and norms of North American fandoms and platforms. - Coordinate with the Business Development, Social Media Marketing, Creative, and other related teams in both the US and Japan so that community initiatives are consistent with the client's overall marketing activities. Also there is "Service Development & Client Management" responsibilities: - Lead the launch and development of 33 USA's Community Management service. Working with the Business Development team and leadership, build the service scope, delivery structure, operating processes, packages, pricing inputs, proposal materials, and case studies. - Support the Business Development team in proposing Community Management services to anime, manga, and game IP clients. - Join sales meetings and pitch presentations as needed, contributing strategic and operational recommendations as the community subject-matter expert. - After award, act as the client's primary point of contact for community matters, providing regular reporting, sharing issues, and proposing improvements to build lasting client relationships. - Work to build and maintain relationships with platform contacts at Discord, Reddit, and others; continuously track new features, policy changes, Trust & Safety developments, and community operations best practices, and reflect them in 33 USA's services. - Continuously study leading examples across the entertainment industry — particularly the game industry, where community management is most advanced — and evaluate their applicability to anime and manga IPs. Also "Engagement Programs & Fandom Initiatives": - Plan and execute ongoing community programs that drive fan participation and interaction, such as launch events, AMAs, watch parties, contests, release-linked activations, and creator/ambassador programs. - Partner with the Social Media Marketing and Creative teams to design initiatives that effectively connect social media communications with fan engagement inside the community. - Accurately understand the brand intent, worldview, and guidelines of Japanese IP holders, and translate them into experiences suited to North American fandom culture and community dynamics. Also "Community Strategy & Design" responsibilities (some overlapping). But we can combine all responsibilities into a list. We must not invent or summarize away detail; we need to preserve all substantive information. So we need to include each of these points as list items. Now Benefits: we need to list as list items. Let's parse Benefits paragraph into list items: - 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. But the last two sentences are more like statements; still we can include them as list items. Now we need to output HTML fragment only, no markdown fences. We'll structure:

        About the role

        ... maybe a short prose summarizing the position summary? But we already have responsibilities list; we could keep a short paragraph summarizing the role then list responsibilities. However the instruction: Use

        for prose. We can include a short paragraph about the role (the Position Summary) then

        for responsibilities. But we must not repeat job title as heading. That's fine. We need to preserve all substantive information; we can put the Position Summary prose in

        and then responsibilities in

        . However the Position Summary includes many details that are also in responsibilities; we risk duplication. But we can keep the summary as a short paragraph and then list responsibilities in detail. That would preserve all info (some duplicated but okay). However we must avoid inventing or summarizing away detail; duplication is okay as long as we don't lose detail. Alternatively we could skip the prose and just have responsibilities list; but then we might lose some nuance like "builds from the ground up and leads 33 USA's new Community Management service". That's captured in responsibilities list anyway. So we could just have responsibilities list and no prose. But the instruction says use

        for prose; not required to have prose. It's okay to have only lists. Thus we can output:

        Responsibilities

        • ...
        ...

        Requirements

        • ...
        ...

        Qualifications