We're at an inflection point for what it means to build for developers and agents. The way engineers discover, integrate, and work with APIs is changing fast, and we're actively building the infrastructure to meet that shift
Developers still integrate WorkOS, but increasingly their agents do it for them. This team owns every way into WorkOS that isn't the dashboard: SDKs in 9 languages, now generated from our API spec; an AI installer CLI that sets up AuthKit in any project; our MCP servers and agent skills; and other not released projects we're building in-house. You'd ship daily with agents as collaborators, and your code goes into other people's apps. The roadmap comes from watching real integrations: friction logs, shared customer Slack channels and telemetry
The goal is that when a developer (or their agent) needs enterprise-ready auth, WorkOS is the easiest path forward regardless of stack, language, or how they're building
Ship agent tools and skills so developers (and their agents) can integrate WorkOS without friction
Write evaluations to measure whether what you ship actually improves developer outcomes
Talk to customers, surface insights, and translate them into roadmap
Contribute to the architecture and tooling for fully generated, polyglot SDK pipelines — so a change to the API propagates cleanly across all languages
Own and evolve SDKs across our seven supported languages (Node/TypeScript, Python, Ruby, Go, Java, PHP, .NET) and framework libraries like our Next.js, Remix, and TanStack integrations
Build and extend AI-native documentation systems as structured context that makes WorkOS work well in Cursor, Claude, Copilot, and agentic workflows
Represent WorkOS publicly through docs, blog posts, OSS, and occasional conference appearances
Build developer tooling like the WorkOS CLI that make complex integrations feel trivial