Okta
About this role
Okta is the enterprise identity company, and FGA is its fine grained authorisation product. This team
owns the developer experience around it: SDKs in Go, JavaScript, .NET, Python and Java, plus CLI
workflows, IDE integrations, GitHub automation, documentation and release strategy. The distinctive
part is that all development is done in the open as open source, and the team actively reviews
community contributions, so your work is public and so is your review history. You would own
significant parts of the SDK and tooling ecosystem, keep implementations consistent across five
languages, and build features like BatchCheck and ListRelations. Apply if you like developer tooling,
which is a specific taste: your users are engineers and the quality bar they apply is unforgiving.
owns the developer experience around it: SDKs in Go, JavaScript, .NET, Python and Java, plus CLI
workflows, IDE integrations, GitHub automation, documentation and release strategy. The distinctive
part is that all development is done in the open as open source, and the team actively reviews
community contributions, so your work is public and so is your review history. You would own
significant parts of the SDK and tooling ecosystem, keep implementations consistent across five
languages, and build features like BatchCheck and ListRelations. Apply if you like developer tooling,
which is a specific taste: your users are engineers and the quality bar they apply is unforgiving.
Who this is for
Requirements. 5+ years of experience as a software engineer, ideally with experience building SDKs,
libraries or developer tooling.
Responsibilities. Maintain and enhance existing FGA SDKs in Go, JavaScript, .NET, Python and Java
using the SDK generator framework. Customise and refine SDK templates and wrappers so behaviour is
consistent across languages, supporting configuration overrides such as store ID, authorisation model
ID, headers and parallelisation limits. Implement and improve core SDK features including client
credentials authentication flows, robust error mapping, retry logic with jitter, and rate limiting
safeguards. Implement advanced capabilities such as BatchCheck, ListRelations and non transactional
write operations.
What makes this one different. The team's guiding principle is stated as "One developer experience,
many deployment models", covering both the open source and SaaS versions of FGA. All development
happens in the open as open source and community contributions are welcomed and reviewed. That means
your commits and code reviews are publicly visible, which is a genuine plus if you want a portfolio
and a genuine consideration if you would rather work privately.
Location. Bengaluru. Okta operates a flexible model where the role allows, so confirm office days in
the first call.
⚠️ Board metadata to ignore on Okta postings generally. Several Okta requisitions publish "Minimum
Work Experience: 0.0" in their Greenhouse metadata, which as structured data reads like no experience
is needed. It is an unfilled placeholder. Years here come from the requirement list in the body.
Who this is for. An engineer with five or more years who genuinely enjoys building for other
developers, and who is comfortable being polyglot: this is five SDK languages, so breadth matters
more than depth in any one. Authorisation is a good domain to learn properly and hard to pick up
casually.
libraries or developer tooling.
Responsibilities. Maintain and enhance existing FGA SDKs in Go, JavaScript, .NET, Python and Java
using the SDK generator framework. Customise and refine SDK templates and wrappers so behaviour is
consistent across languages, supporting configuration overrides such as store ID, authorisation model
ID, headers and parallelisation limits. Implement and improve core SDK features including client
credentials authentication flows, robust error mapping, retry logic with jitter, and rate limiting
safeguards. Implement advanced capabilities such as BatchCheck, ListRelations and non transactional
write operations.
What makes this one different. The team's guiding principle is stated as "One developer experience,
many deployment models", covering both the open source and SaaS versions of FGA. All development
happens in the open as open source and community contributions are welcomed and reviewed. That means
your commits and code reviews are publicly visible, which is a genuine plus if you want a portfolio
and a genuine consideration if you would rather work privately.
Location. Bengaluru. Okta operates a flexible model where the role allows, so confirm office days in
the first call.
⚠️ Board metadata to ignore on Okta postings generally. Several Okta requisitions publish "Minimum
Work Experience: 0.0" in their Greenhouse metadata, which as structured data reads like no experience
is needed. It is an unfilled placeholder. Years here come from the requirement list in the body.
Who this is for. An engineer with five or more years who genuinely enjoys building for other
developers, and who is comfortable being polyglot: this is five SDK languages, so breadth matters
more than depth in any one. Authorisation is a good domain to learn properly and hard to pick up
casually.
Apply on company site
Opens www.okta.com, the employer's own application page. Applying is always free.