## Summary Community teams manage the day-to-day work of building a user community so members get value and the business grows. They're cross-functional by nature, acting as quarterbacks across marketing, product, and customer success. The piece frames an effective team around five personas — scientist, strategist, champion, technician, and captain — and argues hiring should weight overall qualities and values fit over a checklist of task skills. ## Key Points - Community work covers responding to inquiries, facilitating interactions, creating content, welcome messages and surveys, running events, sharing insights internally, and reporting on impact. - The team sits across departments rather than in one box, collaborating with marketing (content, events, leads), product (champions, roadmap feedback), and customer success (community-sourced solutions). - Five personas form a complete team: the scientist (data-driven, tests hypotheses, proves ROI), the strategist (structure, goals, long-term vision), the champion (recognizes and amplifies members), the technician (community ops and tech stack), and the captain (serves the team, sets shared goals). - A single person can carry more than one persona; the model is about coverage, not headcount. - Hire for strengths that complement the team, passion for growing in the space, and willingness to embrace ambiguity and move with velocity. ## Claim Atoms - **Community teams are cross-team quarterbacks** — they coordinate initiatives spanning marketing, product, and customer success rather than sitting in one department. - **Hire for qualities, not task lists** — strengths, learning appetite, and comfort with ambiguity matter more than a fixed skill checklist. ## Links - Connects to DevRel community-building and the persona/role-coverage framing used when staffing developer programs. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: Joins the cluster on building and running community programs.