About the company
Building on a great API is one of the best feelings in software — every interface you want is right there, and it all just works. Building on a bad one is the opposite: out-of-date docs, no SDK in your language, no MCP server. We started Scalar to fix that.
We're a small team (around ten engineers and designers) who wear a lot of hats and obsess over our craft. We think every company deserves Stripe-level docs, SDKs, and MCP servers from day zero — not just the ones with a platform team to build them. Open-source is in our DNA: our whole team contributes to and maintains repositories across the API ecosystem, including the standards everyone relies on, like OpenAPI.
Responsibilities
- Technical wins — live demos and hands-on POCs against a prospect's real API, not a sandbox. Scoping calls, architecture questions, and the security and compliance reviews nobody else wants to answer
- Docs migrations — getting teams off Redocly, Mintlify, Stoplight, ReadMe, and homegrown docs sites, including the unglamorous part: cleaning up OpenAPI documents that have drifted from reality for three years, and rebuilding their Markdown/MDX and two-way Git sync so nothing breaks in the cut-over
- SDK generation — showing an engineering team what their spec produces across TypeScript, Python, Go, PHP, Java, and Ruby, explaining why a oneOf or a missing discriminator makes their SDK ugly, and fixing the spec so it doesn't
- Agent Scalar — standing up secure MCP servers against a prospect's API and demonstrating what an agent can do with a well-described interface, which is still a new enough argument that you'll be making it for the first time in most rooms
- Building the motion with Marc — turning founder-led selling into something repeatable: qualification criteria, demo environments, POC scoping that doesn't take three weeks, and the answers to the objections we hear more than twice
- Building, actually building — sample apps, custom themes, integration glue, reproduction cases, and fixes to our own repos. You'll open PRs against Scalar, not just tickets
- Onboarding and support — owning the first 90 days of a new customer, and being the technical escalation when an SDK generates something wrong or a CI sync breaks at 5pm
- Product feedback with evidence — you'll see every gap before anyone else does. We expect you to say so loudly, with a reproduction, and sometimes with a patch
- The function after you — as we grow the team, you'll set the technical bar for who joins it and train the people who follow you into this role
Requirements
- You've done customer-facing technical work — solutions or sales engineering, forward-deployed, developer relations, or consulting — and you can hold your own with a skeptical staff engineer
- You actually write code. TypeScript is our stack; you should be comfortable enough to build a working integration live on a call without rehearsing it