Software Engineer (AI Developer Productivity)

• Baseten’s engineers want to work in an AI-first way
• What’s missing isn’t enthusiasm — it’s the platform underneath it
• Today everyone assembles their own agent config, context files, and MCP servers, so the good patterns stay trapped in individual setups instead of becoming defaults everyone inherits
• You’ll build that platform: the agent configurations tuned to our monorepo, the context and tooling layer that makes agents competent in our codebase, the evals that tell us which approaches actually work, and the rollout mechanics that get a new engineer productive with agents in week one
• You are not here to mandate how engineers use AI — you’re here to make the good path the easy path
• Success looks like teams adopting what you build because it beats what they’d cobble together themselves, not because a policy requires it
• Platform engineer, not AI evangelist
• Ship infrastructure, measure it, kill what doesn’t work, let adoption be the referee
• The playbook for AI-first SDLC doesn’t exist at any company yet
• You’ll write ours
• Agent substrate — Repo-level context infrastructure that makes agents competent in our codebase (CLAUDE.md/AGENTS.md conventions, architecture and domain context, and the tooling to keep it accurate as code moves). Internal MCP servers giving agents scoped access to CI, observability, incident tooling, deployment state, and docs. Shared skills, subagents, and hooks that encode Baseten workflows. Sandboxed environments where agents can build and test safely
• The golden path — Project templates and onboarding that ship with AI tooling configured and working. Self-serve infrastructure so teams build their own agents without you as the bottleneck. Gateway, auth, cost controls, and audit logging for internal model access
• The feedback loop — Eval harnesses that answer “is this config better than that one” against real Baseten tasks, not vibes. Instrumentation of AI tool usage and its downstream effects on cycle time, review latency, and change failure rate. Honest reporting, including on what you built that didn’t pan out
• Agents in the SDLC — Automation where agents earn their keep: PR review triage, test gap-filling, incident context assembly, migrations and refactors, codebase Q&A. Integrating agents into CI/CD with guardrails that make it trustworthy
• Own the internal AI developer platform end to end — architecture, build, rollout, operation, measurement
• Evaluate and integrate third-party AI coding tools (Claude Code, Cursor, Codex, and whatever ships next quarter), and build the context layer that makes them work against our monorepo
• Build frameworks that let other engineers create their own agents without deep LLM expertise
• Establish the evaluation practice for AI-assisted development at Baseten, and use it to drive investment decisions
• Drive adoption through developer experience — good defaults, clear docs, low friction — not mandate
• Embed with teams to find where AI genuinely unblocks them, then generalize those wins into platform capabilities
• Own the safety layer: permissions, secrets handling, audit trails, cost management

Benefits

• Remote-first work environment. The Baseten team is welcome to work from wherever they want; fully remote, in our San Francisco office, or a mix of both. Today, our team (including our founding team) is spread across the United States, Canada, and Armenia. We provide a $1,000 stipend for you to make your home-office comfortable and productive
• Regular in-person team summits. We get together as a team three times a year to plan, workshop, and most importantly, get to know each other better
• Unlimited PTO. We ask that everyone take at least 4 weeks of vacation. And we have a company-wide break between Christmas and New Year’s Day
• Full healthcare coverage. Medical, dental and vision insurance for you and your family
• Paid parental leave. 16-weeks fully paid parental leave (adoptive and non-birth parents included) and flexibility with schedules while returning to work
• Company-sponsored 401(k) for you to contribute to
• Learning and development budget. We encourage you to take classes, attend conferences, and invest in your craft and we’ll cover expenses to make it happen- Deep personal fluency with AI coding tools and well-formed opinions about where they break down
• Platform mindset: you build for adoption and self-service, treat internal engineers as customers, and would rather ship a good default than write a style guide
• Developer tooling, CI/CD, and Kubernetes/Docker fundamentals
• Hands-on experience with LLMs and agent frameworks — tool calling, MCP, context management, orchestration, failure handling. You’ve shipped something agentic that real people used, not just prototyped
• Comfort with ambiguity — this space invalidates its own best practices every few months
• Excellent written communication. Much of your leverage is docs, templates, and examples that scale beyond conversations you’re in
• Have 4+ years of relevant industry experience building and enabling AI native SDLC
• Strong proficiency in Python and/or Go, building tools other engineers depend on daily