Open Source Community Manager, Strands Agents

About the role

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.
• 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.
• 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.

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.

Basic Qualifications

• Experience writing for developer and technical audiences: blog, product documentation, technical information
• 5+ years of experience in developer education, developer experience, developer relations, technical content leadership, or related roles.
• Deep technical fluency — you understand developer workflows, can read/write code, and can explain technical concepts clearly.
• Experience building or operating with agent frameworks, LLM tooling, or the broader AI/ML ecosystem.
• Familiarity with LLM APIs, tool/function calling, and model providers.
• Experience running structured community programs (ambassadors, champions, user groups, governance) at scale.
• Existing relationships across the AI developer community and with model or platform providers.
• Hands-on familiarity with Strands Agents or a comparable agent SDK.

Preferred Qualifications

• Experience building or managing a developer or open-source community (Discord, Slack, forums, GitHub), with a feel for what makes one welcoming, active, and self-sustaining.
• Hands-on coding ability, with working proficiency in Python and TypeScript. You can read and run the codebase, follow and review pull requests, build and debug a sample agent, and talk shop credibly with builders.
• Comfortable with Git and GitHub workflows.
• Demonstrable involvement in open source, whether as a contributor, maintainer, or community organizer.
• A self-starter who takes full ownership and is comfortable with ambiguity.
• You set your own priorities, spot what needs doing, and act without waiting for direction.
• A marketing-minded approach to growth, with a track record of finding the right channels to reach developers and the initiative to propose and run campaigns, content, and experiments.