Get hired atMASTRA×The Anti Job Board

How to Actually Get Hired

Who reads applications, which channel gets a reply, and what they screen for.

<50 peopleRemoteB2B, Engineering, Product and Design

Don't make these mistakes

Avoid sending generic applications without specific proof of work or understanding of the framework's unique value proposition.

What gets their attention

Spark Capital's portfolio tells you what they're betting on: Twitter, Slack, Airtable: tools that became the default infrastructure of their category. Leading this round is a specific thesis that Mastra becomes the TypeScript agent runtime the way React became the frontend default, not just a popular framework. The seed syndicate sharpens that read: Guillermo Rauch (Vercel) understands that developer experience at the deployment layer creates structural lock-in; Amjad Masad (Replit) is already a production customer, meaning Mastra's hiring needs are shaped by the demands of embedding agents inside other companies' products; Gradient Ventures (Google's AI fund) signals this is an intelligence infrastructure bet, not just a JS community play. The practical outcome: $22M just landed, the platform layer launched the same day as the announcement, and the engineering roadmap is public - heartbeat, channels, browser access, web data as upcoming primitives, plus RBAC, SSO, and ACL in Mastra Studio. There are roughly 26 people to execute all of it. One live role exists (Design Engineer, remote US). Mastra explicitly invites you to create your own: "Mastra is looking to hire across all roles for talented individuals looking to join a fast-growing company focused on serving developers." Email: careers@mastra.ai.

Why applying the normal way doesn't work

MASTRA is <50 people. No recruiter, no HR. Your application goes to a founder juggling everything. Cold outreach is how you actually get seen.

Who to contact at MASTRA

Who decides:a founder or department head
Best channel:LinkedIn or direct email

Founding team

SB
Sam Bhagwat
Co-Founder and CEO

Sam is one of the most credentialled developer tools founders in the JavaScript ecosystem, and the lineage from Gatsby to Mastra is not a pivot, it is a continuous extension of the same core conviction: that framework design is a craft, and that getting it right creates outsized leverage for the developers who use it. He studied Economics at Stanford (BA, class of 2011) after beginning his studies in 2005, including a two-year break for missionary work, an unusual biographical detail that speaks to the same person who later describes framework design in almost philosophical terms. After Stanford he worked as an associate consultant at Mars & Company briefly, then as CFO at Blueseed (the startup seasteading project), before pivoting fully into engineering at Boingo Wireless, then early-stage engineering roles at Zenefits (YC W13) and PlanGrid (YC W12), both high-growth San Francisco enterprise companies where he was among the first 20 engineers. He co-founded Gatsby in 2018 and served as co-founder until 2023, scaling it from an open-source React site generator to a product used by hundreds of thousands of developers, raising $50M in venture funding and growing to $5M ARR before acquisition by Netlify. He then served briefly as Principal Engineer at Netlify post-acquisition before leaving to start Mastra in July 2024, within months of leaving, the company was in YC and raising $13M. He authored 'Principles of Building AI Agents' in 2025, which he describes as 'the most popular book in SF right now,' and which has become a community artefact in the Mastra ecosystem. His public writing on X (@calcsam) and the Mastra blog consistently returns to the craft of API design: the naming choices, the progressive disclosure decisions, the interoperability principles that determine whether a framework becomes the default or the also-ran.

AA
Abhi Aiyer
Co-Founder and CTO

Abhi is the infrastructure half of Mastra's founding trio and the person most directly responsible for the reliability properties that make Mastra viable as enterprise infrastructure rather than just a developer toy. His role at Netlify as Principal Engineer and lead of a 100+ person engineering organisation is the credential that matters most: he built the Gatsby Cloud infrastructure, tens of thousands of build nodes, billions of files served, hundreds of terabytes of monthly bandwidth, which means he understands at first-hand what it takes to go from an open-source framework with great developer experience to a cloud platform that enterprise teams can actually depend on. That transition is exactly what Mastra is executing now with the Series A platform launch. His role as CTO at Mastra means he is making the architectural decisions about Mastra Server, the Memory Gateway, and the enterprise tier features that determine whether the platform can support the Bx and Workday-scale deployments already in production.

ST
Shane Thomas
Co-Founder and CPO

Shane is the product and community half of the founding team, and his background is the piece that explains why Mastra's developer experience feels as deliberate as it does. He served as Staff Engineer and Head of Product at Gatsby, giving him both engineering depth and product ownership experience across the same framework's growth arc that Sam led commercially. He previously built Audiofeed, an AI podcasting product, which means he has direct experience as a solo product builder shipping AI-native consumer products before Mastra existed as a concept. The YC profile adds one biographical detail that is worth noting in the context of recruiting: 'state wrestling champion.' That is the background of someone with a competitive drive and discipline orientation that shows up in how he talks about open-source, his public writing on 15+ years in open source is oriented around craft and community, not individual recognition.

What to show them

Design Engineers at developer tools companies sit at the intersection of product design and engineering, owning the visual language, documentation UX, and interactive examples that determine whether a framework feels like magic or feels like work. At Mastra, this means owning the developer experience surface: the interactive playground in Mastra Studio, the documentation, the onboarding flows, and the API design aesthetics that make the framework feel coherent and intuitive. Proof of work: Fork the Mastra open-source repo, build a small example agent using the framework, and write a one-page design critique of the current Mastra Studio interface, specifically identifying the three places where a new developer is most likely to get confused and proposing a specific UX change for each. The exercise demonstrates both framework fluency and design engineering thinking in the same artefact. Share it with careers@mastra.ai.

A cold email that works at MASTRA

Subject: Design Engineer, [your one-line proof]
Hi Sam, I built a small agent using Mastra, wrote a design critique of Studio focusing on the three highest-friction onboarding moments, and have a proposal for each. The one that surprised me most was the mental model gap between the workflow and agent primitives on first encounter. Happy to share the writeup, I'd be interested in talking about the Design Engineer role.

What MASTRA screens for

Spark Capital's portfolio tells you what they're betting on: Twitter, Slack, Airtable: tools that became the default infrastructure of their category. Leading this round is a specific thesis that Mastra becomes the TypeScript agent runtime the way React became the frontend default, not just a popular framework. The seed syndicate sharpens that read: Guillermo Rauch (Vercel) understands that developer experience at the deployment layer creates structural lock-in; Amjad Masad (Replit) is already a production customer, meaning Mastra's hiring needs are shaped by the demands of embedding agents inside other companies' products; Gradient Ventures (Google's AI fund) signals this is an intelligence infrastructure bet, not just a JS community play. The practical outcome: $22M just landed, the platform layer launched the same day as the announcement, and the engineering roadmap is public - heartbeat, channels, browser access, web data as upcoming primitives, plus RBAC, SSO, and ACL in Mastra Studio. There are roughly 26 people to execute all of it. One live role exists (Design Engineer, remote US). Mastra explicitly invites you to create your own: "Mastra is looking to hire across all roles for talented individuals looking to join a fast-growing company focused on serving developers." Email: careers@mastra.ai.

A tailored CV beats a generic one. Use MASTRA's job description language to clear filters.

Mistakes that kill applications

Generic CVs stand out at a <50-person company — and not in a good way. Fastest path to rejection.

Don't open with what you want. Open with what MASTRA is dealing with right now — The seed round story is exceptional and worth understanding as a hiring signal context, and what you'd do about it.

Applying and waiting = silence. Follow up at day five — it roughly doubles your odds of a reply.

Frequently asked questions

How do I apply to MASTRA?

Through the roles on our MASTRA jobs page, or directly to a founder or department head if you can reach them. At <50 people, direct outreach outperforms the form.

Does MASTRA respond to cold emails?

Response rate data for MASTRA not yet confirmed.

Who is the hiring manager at MASTRA?

At this size, hiring is usually run by a founder or department head.

How competitive is it to get hired at MASTRA?

Typical applicant count for B2B, Engineering, Product and Design roles (<50 people): 50-100 in two weeks. Apply fast.

Have your application sent for you

We find roles at companies like MASTRA within 48 hours of them appearing, build a CV tailored to the posting, and send it while you're still applicant number ten.

Get early access →

Related