Founding Solutions Engineer

About Scalar : 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. We keep things lean and move without layers of process — engineers pick up problems, talk to each other, and ship. We're looking for owners with high agency: people who see what needs doing and do it. If you do your best work with a lot of autonomy and very little ego, you'll feel at home here.

Right now, sales at Scalar is Marc, our CEO, doing every part of it himself. Sourcing the account, running the first call, going deep on the technical evaluation, answering the security review, negotiating the contract, onboarding the team, and picking up the Slack message when something breaks at 5pm. That's founder-led sales end to end, and it's worked — it's how we got Zoom, Clerk, Warp, and Profound. It also doesn't scale, which is why this role exists. You'll be our first Solutions Engineer and one of the first three people on the sales team, joining alongside two SDRs starting at the same time. You'll sit next to Marc in our San Francisco office, learn the motion from the person who built it, and then take the technical half of it off his plate — the demos, the proofs of concept, the migrations, and the first ninety days of every customer who signs. There is a motion here and it works — but it's Marc's, it lives largely in his head, and it has never had a technical counterpart. The demo environments, the POC scoping, the technical qualification bar, the answers to the objection you'll hear for the fourth time: none of that exists yet. You'll build it, and what you build is what the next five people on this team will use. If you've been waiting for the job where you shape how a company sells rather than execute how it already does, this is that job. Who we sell to Our buyers are engineers, and the product is the proof. Zoom's developer documentation runs on Scalar. So does Clerk's — a company whose docs were already a competitive advantage, which makes them exactly the kind of customer with no reason to switch unless the thing is genuinely better. Warp and Profound ship SDKs we generate from their OpenAPI documents, in every language their users ask for. Those are the rooms you'll be in: platform teams, API teams, and the staff engineer who has strong opinions about their spec and is not going to be charmed. They don't want a deck. They want to see their own API rendered in Scalar Docs, their SDK generated in their language, and MCP servers available so agents can do real work against their API. Your job is to make that happen fast enough that the decision makes itself. This is a genuinely technical job, not a sales job with a technical veneer. You'll be writing TypeScript against a prospect's OpenAPI document live on a call, and opening a PR against scalar/scalar the next morning to fix whatever made it hard. The same product surface our platform team runs — Docs, SDK generation, and Agent Scalar — is the surface you'll demo, migrate customers onto, and file reproductions against.

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