About this role
Strands Agents is an open-source SDK for building AI agents, from simple chat assistants to complex multi-agent systems. It ships Python and TypeScript libraries and works with every major model provider. The project lives in the open on GitHub, with an active Discord where builders ask questions, contribute code, and help shape where it goes next. That community is what drives the project’s growth, and right now nobody owns it. We’re looking for our first Community Manager to change that. Today the engineering team squeezes community work in around shipping the SDK, which means questions sit unanswered, newcomers don’t always find their way to a first contribution, and great releases go under-publicized. You’ll take ownership of all of it: making the community welcoming and well-run, growing the base of contributors, and keeping builders engaged with the project over time. This is a role to shape, not just fill. The community function is brand new, so you won’t be handed a playbook. You’ll write it. If you’re developer-minded, genuinely excited about AI agents, and the kind of person who spots what needs doing and just does it, this is a rare chance to define what a great open-source community looks like from the ground up. Key job responsibilities • Run the community day to day. Own the health of Discord and GitHub: triage issues and discussions, answer and route questions, set the tone, moderate, and keep response times low so the community always feels staffed and responsive. • Build the newcomer journey. Design how someone goes from first visit to first contribution, with welcome flows, starter docs, good first issues, and mentorship. Run the recurring rituals (community calls, office hours, AMAs, challenges) that turn one-time visitors into regulars. • Grow contributors. Shepherd external contributions from first pull request to merge. Unblock people, pair them with maintainers, and build a pipeline of repeat contributors who grow into trusted reviewers across both the Python and TypeScript SDKs. • Stand up a champions program. Identify your most active members, recognize their work, and create leadership paths that keep engaged builders invested for the long haul. • Show up at events and create content. Represent the project at meetups, hackathons, and conferences. Run hands-on workshops, support community-led events, and publish blogs, samples, and videos that help builders get from a first agent to production. • Amplify every release. Partner with engineering and the developer relations folks to turn changelogs into launch stories that land across Discord, social, and the blog, so builders actually hear about what shipped. • Drive audience growth like a marketer. Figure out which channels reach the right builders (social, newsletters, dev communities, sponsorships, content series, partnerships, docs discoverability), run campaigns and experiments, measure what brings people who stay and contribute, and double down on what works. • Build ecosystem relationships. Cultivate connections with model providers, framework maintainers, and platform partners through integrations, joint content, and co-marketing. • Be the voice of the community inside the team. Track sentiment, surface recurring pain points and feature requests to product and engineering, and close the loop back to the community on what shipped. • Set the strategy. Define how and where the project shows up, what a healthy community looks like, and which metrics matter. Propose experiments, report on community health, and evolve the playbook as the project grows. A day in the life There’s no template day, which is part of the appeal. You might start by clearing the overnight Discord backlog and unblocking a contributor whose first pull request is stuck, then hop into a quick sync with an engineer to make sure a tricky fix gets the review it deserves. Mid-morning you’re drafting the launch narrative for this week’s release, lining up posts across Discord, social, and the blog so the new capability doesn’t go unnoticed. After lunch you host office hours, walk a newcomer through building their first agent live, and notice a regular who keeps showing up with thoughtful answers, so you flag them for the champions program. Later you’re sketching out an experiment to test whether a new channel actually brings in builders who stick around, and pulling together the week’s community health numbers to share back with the team. Some weeks you’re on the road running a workshop at a conference or supporting a community-led hackathon. Through all of it, you’re listening for the patterns: the questions that keep coming up, the rough edges builders hit, the feature requests worth carrying back to product and engineering. About the team You’ll own the community function and run it autonomously. You set the direction for how the community operates and bring proposals rather than wait for assignments, while partnering closely with the engineering and product teams to keep community needs aligned with the roadmap. It’s a real two-way exchange. You lean on engineering for technical depth and where the project is headed, and in return you bring them community signal, ecosystem context, and amplification that gets their work in front of the broader builder audience. You’ll also coordinate with the developer advocacy and solutions folks on events, content, and partner work, and align travel and event priorities with the team each quarter. If you like ownership, dislike waiting for permission, and want to build something from scratch alongside a team that ships fast, you’ll feel at home here.