Job Description
At Mastra, every week is launch week. We ship 3–4 minor releases and one feature launch every week, plus platform announcements and major launches every few months. We need you to own that. Think about this role as the product release cannon. This is a writing and building job, we mean both literally. About 80% of your time is producing content for developers. The rest is website messaging and light sales enablement. But you'll also build: agents that coordinate parts of our release pipeline, workflows that make the whole system faster. We use Mastra to run Mastra. This is a high-impact role. We're open on seniority. The team ships fast and a lot. You get to represent the work of 20+ long-time open-source builders to the world. If you want to get a sense of how the product works, you should play around with Mastra: npx [email removed] . If you want to get a sense of how we release, read through our code releases on Github , feature releases , or larger announcements . What you'll do #1, and it's the most important: own the launch pipeline. We have a weekly narrative tracker in Notion. You'll live in it. Figuring out what we're shipping, what story it tells, and how to get it in front of developers fast. The role of product marketing is changing. Sitting down with engineers who shipped a feature, understanding how it evolved, listening on AI Twitter/X to how functionality is being described in the market still matters a lot. Sure, the specific details to how to set up or use a feature are a Claude Code-able materialized view of commits. But in a world where teams are shipping faster, the overall narrative and messaging matters more than ever, as does the feeling that they are crafted with love and care for their users. You’ll write for engineers. Our readers build agents and workflows in TypeScript. They'll notice you hand-waving. They have that finely-honed BS detector only engineers do. You’ll need to understand (or learn quickly) the components of an agent loop, w
