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 AI-native enterprise software for some of the world's largest organisations, and identity is foundational to it: every product, service and AI agent must prove who it is before it can act.

The company is hiring two Principal Platform Engineers to build the shared authentication and authorisation capabilities that product engineering teams depend on. You would own this area end to end in a small team.

The company has billion-dollar revenue, more than 7000 employees and offices on every continent.

This is an identity systems role, not a DevOps, SRE, cloud or infrastructure role. You should have built identity systems rather than administered or configured them.

Candidates whose background is mainly cloud IAM policies, RBAC, Terraform, Kubernetes, CI/CD or access governance, with identity as one tool among many, will not be progressed. That is a different discipline and team.

Engineers who have moved a live user base onto a new identity provider without breaking logins will feel at home here.

Architecture, administration and product configuration alone do not meet the bar. The company wants to know what you personally implemented, tested, automated and supported in production.

A software development background is particularly valuable but not a prerequisite. Engineers whose coding grew out of platform engineering, infrastructure or SRE work are welcome.

Responsibilities

  • Design and build platform services, APIs and automation for authorisation and authentication across three hosting environments: the cloud-native platform, the legacy hosting platform and the lifecycle cloud.
  • Consolidate a fragmented authorisation landscape into one model that is correct, fast and reliable in distributed, multi-tenant environments.
  • Own the services you build in production.
  • Establish 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.
  • The current stack is SpiceDB on PostgreSQL for authorisation, Curity for authentication, and Keycloak estates migrating onto it. You do not need prior experience with each product.

Requirements

  • Substantial hands-on experience building and running platforms or shared infrastructure for software engineering teams.
  • Strong coding and scripting skills applied to infrastructure, automation, deployment tooling or integrations. You can maintain code, review changes and write 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 operates 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 reduce manual work for engineering teams.
  • A sound grasp of APIs, networking, data stores and distributed-system behaviour, and the ability to troubleshoot production issues.
  • Technical leadership shown through design decisions, code reviews, engineering standards and support for other engineers.
  • Experience building application or backend services is a strong advantage but not required. Your coding may come mainly from infrastructure and platform work. You must be willing to work with Go-based tooling and services and build skills where needed.
  • You have built authentication and access control in applications, APIs or shared platform services, and you have written your own authenticators, extensions or protocol flows.
  • Working knowledge of OAuth 2.0, OpenID Connect and token-based authentication, including secure validation and common failure modes. You understand how tokens are issued, signed, rotated and revoked, how sessions behave, and how OAuth, OpenID Connect, SAML and SCIM work beneath the products that implement them.
  • Practical understanding of access control models, including role-based, attribute-based and relationship-based models, and experience implementing permission checks or designing permission models.
  • Understanding of permission models, least privilege and tenant isolation, and of where access decisions are enforced.
  • You can reason about correctness, latency, consistency and the traceability of authorisation decisions.
  • Understanding of enterprise federation, SSO and external identity-provider integration in a customer-facing platform.
  • Experience with cloud infrastructure, Kubernetes, containers, GitOps and Infrastructure as Code, with an approach to reliability that covers observability, performance testing, safe rollouts, rollback, backup and recovery.
  • Examples of diagnosing production failures and using code or automation to prevent them from recurring.
  • Sound engineering judgement across distributed systems, relational data and event-driven services.
  • Ability to turn security requirements into working software, automated tests and maintainable platform capabilities.
  • Deeper experience engineering and operating authentication infrastructure at scale is particularly welcome.
  • Familiarity with fine-grained authorisation engines or policy-as-code approaches is valuable.
  • The company would particularly like to talk to you if you have production experience with Curity, especially extending it, automating its configuration and lifecycle, or operating it as part of a software platform.
  • The company would particularly like to talk to you if you have engineered and operated Keycloak in a software product environment, including customisation, automated delivery or migrations.
  • The company would particularly like to talk to you if you have built fine-grained authorisation using SpiceDB or a comparable relationship-based authorisation engine.
  • The company would particularly like to talk to you if you have deeper experience with enterprise federation, SAML, policy-as-code, or authentication and authorisation in distributed, multi-tenant systems.
  • The company would particularly like to talk to you if you have built self-service identity capabilities, APIs or SDKs that other engineering teams use.
  • The company would particularly like to talk to you if you have worked with Go, PostgreSQL and Kafka or RedPanda in production.
  • These items are advantages, not substitutes for strong platform engineering, coding and automation skills. Strong platform engineers with relevant authentication and authorisation foundations are encouraged to apply even without experience of the specific products.

Conditions

Hybrid working is offered, with flexibility to suit how you work.

You will stay close to the code while helping other engineers make good architectural decisions. The company values clear technical reasoning, constructive challenge and ownership from design through production.

The company is interested in how you use AI-assisted engineering: what you delegate, how you review and test the output, and how you stay accountable for the software you ship. It expects AI to be part of how you design, build and ship, beyond autocomplete or chat.

The company is an equal opportunity employer.

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 London, 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
  • London, 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