This role builds […]’s authentication and identity systems. It is not a DevOps, SRE, cloud or infrastructure role.
Before you apply: you should have built identity systems, not administered or configured them. Last week you would have been writing a lot of code. We’re looking for people who have written their own authenticators, extensions or protocol flows — who have worked on how tokens are issued, signed, rotated and revoked, how sessions behave, and how OAuth, OpenID Connect, SAML and SCIM actually work underneath the products that implement them.
If you’ve migrated a live user base onto a new identity provider without breaking logins, you’ll be at home here.
Architecture, administration and product configuration alone are not sufficient. We want to understand what you personally implemented, tested, automated and supported in production.
If your background is cloud IAM policies, RBAC, Terraform, Kubernetes, CI/CD, or access governance and joiner-mover-leaver processes with identity as one tool among many, this isn’t the role — that’s a different discipline and a different team. We won't be progressing with your application.
At […] we’re building the next generation of AI-native enterprise software for some of the world’s largest organisations. Identity is foundational to it: every product, every service and increasingly every AI agent has to prove who it is before it can do anything. You’d own that, end to end, in a small team.
We also expect you to be using AI seriously