Staff Engineer | Auth0 FGA Developer Platform and SDKs

Fine grained authorisation is the problem of deciding not just who someone is but exactly what they can touch, and Auth0 FGA is Okta's product for it. This staff role owns the developer experience around it across both the open source project and the commercial service: SDKs, the CLI, IDE integrations and developer automation. The team maintains SDKs in Go, JavaScript, .NET and Python among others, so this is genuinely multi language work and you would be setting the architectural direction across all of them. Working in the open matters here, since part of the surface is open source and has an external contributor community. Stated bar is eight or more years as a software engineer, with significant experience building developer facing tooling.

Stated requirement is 8+ years of experience as a software engineer, with significant experience building developer tooling and platforms. Role overview as published: a highly experienced staff engineer to join the FGA Developer Tooling team and lead the evolution of the end to end developer experience across both open source and SaaS. Responsibilities: define and drive the technical direction for FGA SDKs, the CLI, IDE integrations and developer automation across both the open source project and the commercial service; and lead architectural decisions for multi language SDKs. The team owns SDKs in Go, JavaScript, .NET and Python among other languages, so breadth across language ecosystems matters more here than depth in one. Domain context, since fine grained authorisation is a speciality: FGA is about deciding what a given identity may do with a specific resource, rather than simply whether they are authenticated. It is modelled on relationship based access control, the same family of approach as Google's Zanzibar, and it is one of the harder problems in identity because the authorisation check sits in the hot path of every request. Building the developer platform for it means your users are other engineers, which changes what good looks like: API ergonomics, documentation quality, useful error messages and migration paths matter as much as throughput. Working partly in the open is a real differentiator on a CV, since public commits and community engagement are visible evidence of the work in a way most enterprise engineering is not. Location is Bengaluru. Good fit for an engineer with eight or more years who enjoys building for developers and is comfortable maintaining several language SDKs at once rather than owning a single service.