Community Lead-Muse

Muse is Meta's personal AI agent — a consumer product with a character, not a faceless platform. It's scaling toward hundreds of millions of people across the US and international markets, on mobile, desktop, wearables, and inside WhatsApp, Instagram, and Messenger. Something unusual is already happening around it. Users coined "Muse Cases" and built "Musebook" entirely on their own. A community-run Musebook talent show drew 365 live viewers and 8,000 views on X with no involvement from us. People are naming their avatars, trading what their agents pulled off overnight, and building a culture around this product faster than we are. We're hiring a Community Lead to meet that energy — to build the official home for it, steward the parts we don't control, and turn an emerging fandom into Muse's most durable engine for advocacy, insight, and growth. Muse the AI product people feel ownership of, and turn that ownership into advocacy, insight, and growth. You're not starting from zero. There's a vetted alpha community on Discord with a full channel architecture, a custom engagement bot (a custom engagement bot) running points, tiers, and recurring challenges, a recruitment and vetting pipeline, and retention data showing community members stick with Muse more than comparable users do. Your job is to take that from an invite-only alpha to a consumer community at launch scale — across multiple surfaces, multiple markets, and in public.

Responsibilities

Scale the community from alpha to consumer scale
Grow Discord from a vetted alpha cohort into the primary home for Muse power users, with channel architecture, roles, and moderation that hold up at 10x and 100x
Extend EggBot from a points-and-challenges bot into a full moderation, triage, and engagement layer, to prepare for the point where manual review stops scaling
Build discovery paths from the product itself: in-app prompts, onboarding, welcome emails, help center
Stand-up community in international markets as Muse expands, adapting its programming rather than translating it
Muse has a personality. The community voice has to match it
Be in the conversation, not announce into it. Most of the cultural energy around AI agents lives on X and moves in hours, not weeks. This role is expected to play their fluently and fast
Partner with social, brand, and our creative partners on community-sourced content, while keeping every piece inside communications and legal review
The steward of organic fandom
Engage with Musebook, Muse Cases, and the community properties users built themselves. Decide what we officially adopt, what we amplify, and what we keep at arm's length — some third-party properties carry real brand and legal exposure
Build the official version of what the community wants before someone else builds a worse one
Develop the proto-social surfaces unique to a product like this: agents interacting with each other in public, anonymized fleet-learning feeds, forums where people compare what their muse figured out
Own a standing tester cohort as a permanent function rather than a one-off call: recruiting, vetting, gating access, and routing every pre-release connector and feature through it
Solve the signal problem. Large dogfooding pools produce surprisingly little usable feedback. Design for feedback quality, not headcount
Manage confidentiality expectations for people testing unreleased features that touch third-party data
Turn the community into a growth loop
Partner with growth on referral and invite mechanics: two-sided incentives, scarcity framing, Muse itself prompts users to bring people in
Identify, recruit, and support the creators and evangelists already making the best Muse content, and give them reasons to keep going
Feed hero use cases into marketing continuously, not on request
Close the loop back to the product
Deliver a regular synthesis of themes, use cases, connector requests, and roadblocks directly to Product and Engineering. Community should sit as close to the product team as possible
Maintain the health framework: activity, retention, sentiment, top advocates, and the funnel from product into the community
Keep the community out of the support path. Bugs and support requests route through existing flows

Qualifications

BA/BS degree in a relevant field (e.g., Marketing, Business, Communications, or related field)
10+ years of full-time experience building communities, partnering closely with Product teams
5+ years across community, social, developer relations, or creator programs, including at least one consumer product at meaningful scale
You use agents every day and have opinions about them. You'd be a Muse power user whether or not we hired you. Deep understanding and/or active use of consumer AI products
Experience managing a large-scale Discord community, including bot automation, role management, and escalation path design
Experience working with product, marketing, communications and growth teams at all levels of management, both internally and externally
Experience driving presentations with executives and cross functional teams
Experience with 0-to-1 products in ambiguous, fast-paced environments
Strong written and verbal communication skills
Project management experience Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements)
Experience writing in a distinctive, engaging brand voice for social and community channels, with demonstrated cultural fluency across platforms like X, Reddit, and Discord. You can hold a character's voice, read a room on X, and know exactly where the line is
Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies
Comfortable with an organic community you don't control, and steady when it goes somewhere you didn't plan for
Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)
Able to operate inside real constraints: legal and comms review, Meta's Electronic Communications Policy for third-party platforms, and the privacy requirements that come with a product holding deep personal context