You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
IFS

Principal Platform Engineer — Authentication & Identity Engineering

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay £90K - 130K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company is building the next generation of AI-native enterprise software, and the team is hiring two Principal Platform Engineers to build the shared authentication and authorisation capabilities that product engineering teams rely on.

The role focuses on identity systems. It is not a DevOps, SRE, cloud or infrastructure role.

Authorisation is being consolidated from a fragmented landscape into one model across three hosting environments: the cloud-native platform, the legacy hosting platform and the lifecycle cloud. It must be correct, fast and reliable in distributed, multi-tenant settings.

The current stack uses SpiceDB on PostgreSQL for authorisation and Curity for authentication, and Keycloak estates are moving onto it. Experience with each of these products is not required.

Identity underpins everything: every product, service and AI agent must prove who it is before acting. You will own that end to end in a small team.

The company has billion-dollar revenue and more than 7000 employees on all continents.

Responsibilities

  • Design and build platform services, APIs and automation for authentication and authorisation.
  • Own those services in production.
  • Set patterns that product engineering teams can adopt with confidence.
  • Make secure authentication and authorisation available through documented, automated, self-service workflows.
  • Write and review infrastructure and automation code, build platform integrations, and contribute to tooling and services, including those written in Go.

Requirements

  • Substantial hands-on experience building and operating platforms or shared infrastructure for software engineering teams.
  • Strong coding and scripting skills for infrastructure, automation, deployment tooling or integrations. You maintain code, review changes and use automated tests.
  • Experience automating provisioning, configuration, deployment and operational tasks through version-controlled, repeatable workflows.
  • Production experience with Kubernetes and containers in an environment that delivers and runs software.
  • Practical experience with a major public cloud platform, Infrastructure as Code, CI/CD and GitOps.
  • Experience building reusable platform capabilities or self-service workflows that cut manual work for engineering teams.
  • Sound understanding of APIs, networking, data stores and distributed-system behaviour, and the ability to troubleshoot production issues.
  • Evidence of technical leadership through design decisions, code reviews, engineering standards and support for other engineers.
  • Experience developing application or backend services is a strong advantage but not required. Your coding may come mainly from infrastructure and platform work. You should be willing to work with Go-based tooling and services and build your skills where needed.
  • Practical experience implementing authentication and access control in software applications, APIs or shared platform services.
  • Working knowledge of OAuth 2.0, OpenID Connect and token-based authentication, including secure validation and common failure modes.
  • Understanding of permission models, least privilege and tenant isolation, and the ability to explain where access decisions are enforced.
  • The ability to turn security requirements into working software, automated tests and maintainable platform capabilities.
  • You have built identity systems rather than only administered or configured them. You have written your own authenticators, extensions or protocol flows, and you understand how tokens are issued, signed, rotated and revoked, how sessions behave, and how OAuth, OpenID Connect, SAML and SCIM work underneath the products that implement them.
  • Architecture, administration and product configuration alone are not sufficient. We want to know what you personally implemented, tested, automated and supported in production.
  • Migrating a live user base onto a new identity provider without breaking logins is a good fit for this role.
  • Applicants whose background is mainly cloud IAM policies, RBAC, Terraform, Kubernetes, CI/CD, or access governance and joiner-mover-leaver processes, with identity as one tool among many, will not be progressed.
  • You use AI seriously in your engineering, as part of how you design, build and ship software, not only for autocomplete.
  • Advantage: production experience with Curity, especially extending it, automating its configuration and lifecycle, or running it as part of a software platform.
  • Advantage: experience engineering and running Keycloak in a software product, including customisation, automated delivery or migrations.
  • Advantage: experience building fine-grained authorisation with SpiceDB or a comparable relationship-based engine.
  • Advantage: deeper experience with enterprise federation, SAML, policy-as-code, or authentication and authorisation in distributed, multi-tenant systems.
  • Advantage: experience building self-service identity capabilities, APIs or SDKs that other engineering teams use.
  • Advantage: experience running Go, PostgreSQL and Kafka or RedPanda in production.
  • Valuable: familiarity with fine-grained authorisation engines or policy-as-code approaches.
  • Deeper experience engineering and running authentication infrastructure at scale is particularly welcome.
  • These advantages do not replace strong platform engineering, coding and automation skills. Strong platform engineers with solid authentication and authorisation foundations are encouraged to apply even without experience of the specific products.

Conditions

Hybrid working is offered, with flexibility to suit individual needs.

You stay close to the code while helping other engineers make sound architecture decisions. The team values clear technical reasoning, constructive challenge and ownership from design through production.

The company is interested in how you fit AI-assisted engineering into your work: what you delegate, how you review and test the output, and how you stay accountable for the software you ship.

The company values diversity and welcomes applicants from all backgrounds.

Where you’d work

Part of the week in the office

You can work from

  • United Kingdom

About the company

IFS

  • Industry: SaaS

Office in United Kingdom

Also hiring in Palo Alto, United States, Krakow, Poland, Madrid, Spain and 9 more places

9 of their 49 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Go
  • PostgreSQL
  • Kubernetes
  • Terraform
  • Kafka
  • CI/CD
Seniority
Principal
Type
Full-time
Industry
SaaS
Specialty
Backend
Region
United Kingdom
Show 7 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Principal
Experience
6+ years
Tech stack
  • Go
  • PostgreSQL
  • Kubernetes
  • Terraform
  • Kafka
  • CI/CD

Location

Work model
Hybrid
Region
United Kingdom
Office
  • United Kingdom
Remote from
  • United Kingdom

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason