Original listing text, shown exactly as published by the company.
The role
Getting a model into production still takes real expertise — choosing a serving engine, sizing hardware, tuning it, wiring it into an app. We want a developer to go from "it runs on my laptop" to "it's serving production traffic" in minutes, on their own. You'll own the entire experience a developer touches to deploy and iterate: the CLI and SDKs, the console, onboarding, model discovery, deployment configuration, truss, and the increasingly agent-driven ways developers build. Your job is to make Baseten synonymous with Great DevEx and make it effortless to drive and self-serve deploy models on Baseten for far more developers than it is today.
Impact and outcomes you'll drive
- You will collapse time-to-production — take a developer from first sign-up to a running, maintained production deployment, and drive down the time it takes to get there.
- You will make the CLI and SDKs the primary way developers and their AI agents build on Baseten — and the authoring surfaces (CLI, console, truss, config.yml / model.py / chains.py) converged into one coherent path.
- You will make a developer's first run effortless — onboarding, model discovery and deploy via the Model Library, and a first deploy where errors surface and builds show progress.
- You will own the deployment lifecycle that lets teams ship safely — environment promotion (dev → staging → prod), version history and an artifact/model registry, reproducible deployments, and the progressive-delivery controls developers set and read: canary, shadow, A/B, scheduled promotion, and one-gesture rollback.
- You will define how developers compose multi-model apps — Chains and the DevEx for developers building multi-modal agents and applications.
- You will grow self-serve deployment across FDEs and customers — you live in customer conversations and turn deploy-and-operate friction into roadmap, so work that needs an FDE today becomes something a developer does alone.
What we're looking for
- You’ve built dev tools as an engineer before you became a PM. You've shipped SDKs, CLIs, APIs, or platform surfaces with your own hands.
- You take great pride in dev tooling and dev products that you’ve shipped with proof
- 5+ years building developer-facing or technical products - as a product manager, or as a product-minded engineer.
- Genuine taste for developer experience across both local (CLI) and UI - you've made something complex feel simple, and can point to where.
- Strong opinions on CLI, API first and agent-first design - you treat the coding agent as a first-class user, not a feature.
- Technical enough to earn engineers' trust and reason about what's under the hood — because you've been under it.
- A rigorous researcher who lets customer reality drive the call and a relentless shipper.
Bonus: experience with ML infrastructure, developer tools, or API products, you've deployed and served models yourself.
Not for You if
- You don't like getting technical.
- You prefer only strategy, UX, or writing great docs over doing whatever it takes to ship great products for customers.
- You want a mature design system and established patterns to work within, rather than defining them from scratch.
- You’re not obsessed with improving your Product craft with AI
