
MASTRA
Open-source TypeScript/JavaScript framework for production-grade AI agents
Last verified August 17, 2026 · Updated daily
What MASTRA is building
Eighteen months ago, Sam Bhagwat and his co-founders walked out of a New York AI hackathon bothered by the same question: why were developers building AI agents in Python notebooks when the web runs on JavaScript? LangChain, AutoGen, and CrewAI all started in Python. Their JS ports arrived later, as afterthoughts. The result was a fragmented, inconsistent experience for the hundreds of thousands of TypeScript developers who build the products that most people actually use. Mastra is built from scratch for that audience. It is an open-source TypeScript framework that gives developers the full primitive stack for building production AI agents: workflow orchestration for complex multi-step operations, agent memory across sessions, tool integration, RAG for knowledge, streaming responses, evals for quality measurement, traces for observability, and a Mastra Studio interface for interactive debugging. The architecture is designed for progressive disclosure, simple things are simple, complex things are possible, and everything works together rather than requiring developers to glue libraries from different ecosystems. As of the Series A, Mastra is simultaneously launching a platform layer (Mastra Studio, Mastra Server, Memory Gateway) for running agents at scale, extending from framework to infrastructure. Enterprise features (RBAC, SSO, ACL) require a commercial licence. The open-source core handles everything up to that tier.
Why this matters
The seed round story is exceptional and worth understanding as a hiring signal context. Over 120 investors participated, including Paul Graham personally, Guillermo Rauch (who built Vercel, the deployment infrastructure that runs most of the modern JS web), and Amjad Masad (Replit), alongside every major name from the Gatsby and Netlify ecosystems. That is not a cap table that forms around a pitch. It forms around a team's demonstrated ability to build things developers love. Gatsby at its peak was used by hundreds of thousands of developers and ran on essentially every major content website. The people who backed Mastra saw what Gatsby accomplished and bet that the same founder with the same co-founders and the same community instincts would achieve category definition in agent infrastructure. Spark leading the Series A confirms the thesis is tracking: Mastra has moved from a framework developers use to a platform that production engineering teams at scale-ups depend on. Brex, the fintech recently acquired by Capital One for $5.1B, used Mastra to build agents internally. MongoDB, Workday, and Salesforce are using it for DevOps and SRE automation. Replit is embedding it so users can build agents within the product. That breadth, both developer tooling and enterprise platform, is the sign of a framework that is genuinely becoming infrastructure.
Open roles at MASTRA
3 positions we're tracking. Roles are re-checked daily and removed when filled.
Know when MASTRA is hiring before anyone else
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching MASTRA
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+Hiring outlook
Very High. Series A with platform launch same day. One live role (Design Engineer, remote US). Explicitly inviting cold job creation: 'Mastra is looking to hire across all roles for talented individuals looking to join a fast-growing company focused on serving developers.'
Working at MASTRA
Since , MASTRA has built Open-source TypeScript/JavaScript framework for production-grade AI agents. The team is now <50 people. Working at a B2B, Engineering, Product and Design company at this stage means broad remit, direct access to founders, and equity that still means something if the company works out.
Most openings are based out of Remote.
How to actually get hired at MASTRA
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
Founding team
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.
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.
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
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.
Don't make these mistakes
Avoid sending generic applications without specific proof of work or understanding of the framework's unique value proposition.
Mistakes that kill MASTRA 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.
Applying to MASTRA? Get the contact, not the form.
The MASTRA interview process
3 stages · 7 days typical · take-home: no · modelled from similar companies
We don't yet have verified candidate reports for MASTRA. What follows is the typical process for a <50-person B2B, Engineering, Product and Design company — treat it as a model, not confirmed detail.
Interview stages
Intro Call
Video call · 30 min
Culture fit and role expectations
Founder or hiring manager
Technical Deep Dive
Video call or in-person · 60 min
Past projects and problem-solving approach
Technical founder or lead
Final Round
In-person or video · 45 min
Team fit and offer discussion
Founding team
MASTRA interview timeline
Timeline: ~ days. That's faster than the B2B, Engineering, Product and Design median (10 days at <50 people).
Interviewed at MASTRA?
Tell us how it went — stages, questions, timeline. Takes 90 seconds and it's how this page stays accurate for the next person.
Submit your MASTRA interview experience →MASTRA jobs, frequently asked questions
How many jobs does MASTRA have open?
As of April 2026, MASTRA has 3 open positions.
Does MASTRA hire remotely?
No remote roles right now — all positions are in Remote.
What roles is MASTRA hiring for?
MASTRA is hiring across Engineering. The most recent opening is Design Engineer.
How do I apply for a job at MASTRA?
Apply via the links above. For tips, read our guide on how to get hired at MASTRA.
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.
How many rounds is the MASTRA interview?
3 stages: Intro Call, Technical Deep Dive, Final Round.
Is the MASTRA interview hard?
Expect relevant experience and culture fit, not algorithm trivia. Candidates report Final Round as the toughest stage.
Does MASTRA give a take-home task?
No, MASTRA does not include a take-home stage.
How long does MASTRA take to get back to you?
Around 7 days across the full process.
What should I prepare for the MASTRA interview?
Focus on relevant experience and culture fit. At <50 people, they're testing whether you can operate without process, not whether you memorised algorithms.
Where is MASTRA based?
MASTRA is headquartered in Remote.
Get MASTRA roles before they're posted
A role stays uncontested for about four days. Here's the window — and where we put you in it.
From $9/month, cancel any time.
Watching MASTRA
0 applicantsRole spotted & verified
1You get the alert
1You've applied
~8Hits the job boards
250+