Job Opportunities API

At Mastra, we make moves. That means we ship a lot and quickly http://github.com/mastra-ai/mastra/releases, but more importantly, it means we keep asking ourselves "What's the most important thing?" and then we go do that thing. That's the heart of product engineering: shipping the thing that makes a customer happy and the business successful, now, rather than after it's been through ten rounds of committee review. WHAT A PRODUCT ENGINEER IS HERE A decent amount of digital ink has been spilled already on what a product engineer is, but we think that a product engineer focuses on outcomes (and speed towards outcomes) rather than on implementation and process. By contrast, great platform engineers do tend to think about implementation and process (and keeping production up and running requires both). It takes both to ship great software, but we’re looking specifically for a product engineer to join our team. This is a high-agency role. We expect that a product engineer can take a vague problem and a clear one alike and get a feature shipped.Our product engineers ship open-source features in our framework. They stand up new services on the platform. They triage incoming issues. They move fast and they're willing to break things (but they have the judgment to keep the blast radius small and quickly fix what they break). It shouldn't surprise you that we lean hard on agent-driven development; we even built our own coding harness. We're constantly trying the newest tools and workflows to see what actually moves velocity and quality, and we're not shy about dropping the ones that don't. If you want to see the kind of work this role does, look at recent releases like Automatic Deploys https://mastra.ai/blog/introducing-auto-deployment-platform, Agent Builder https://mastra.ai/blog/announcing-agent-builder, and Observability https://mastra.ai/blog/announcing-mastra-observability. Better yet, build an agent with Mastra and deploy it, and get a sense of the product for yourself. WHAT YOU'LL DO The most important thing you'll do here is ship features, fixes, and improvements that make the product better. Full stop. You'll work with founders, customers, and teammates to find the shape of the most important problems, and then you'll get as many of them shipped, tested, and launched as you can. You'll point a fleet of agents at the biggest problems and guide them through to working software. You'll open a code editor when the work calls for it. You'll be a (great) teammate. You'll review PRs, give feedback on plans and architecture sketches, and share your best tricks for squeezing more quality out of the latest (and probably already degraded) model. You'll help shape the team's weekly priorities and bring your ideas to our org-wide retros. And you'll take ownership without being asked. You'll plan your own projects, address the bot's review feedback before you ask a human for theirs, jump into customer channels to solve a problem before anyone links the message internally, and bring a pile of demos to Friday demo day. ABOUT YOU Some things that are probably true about you: - You've own features end-to-end and love hearing from customers - You're a full-stack engineer, as comfortable shipping a V0 frontend as you are writing a database migration. You're comfortable enough in a cloud environment (we run on Google Cloud and Railway) to ship a feature that touches Kubernetes - You're not afraid to move quickly and break things (but you're really quick to fix them). - While we’re open to a range experience, you've definitely shipped production code and owned the outcome. Our stack, if it helps you picture it: TypeScript and Node throughout, Postgres, Redis, ClickHouse, on Google Cloud and Railway. NOT A GOOD FIT IF - You need a full spec handed to you before you'll start. - Your reflex when a decision is unclear is "that's a product decision" and then you wait. - You're pessimistic about how AI is chang