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 builds next-generation AI-native enterprise software and is hiring two Principal Platform Engineers to create the common login and permissions services that product engineering groups rely on.

The company has billion-dollar revenue and 7000+ employees on all continents. Identity underpins every product, service and AI agent, which must verify who it is before acting, and you will own that end to end in a small team.

One authorisation model must cover three hosting environments: the cloud-native platform, the legacy hosting platform and the lifecycle cloud. It has to be correct, fast and reliable across distributed, multi-tenant systems.

The current stack uses SpiceDB on PostgreSQL for authorisation and Curity for authentication, and Keycloak estates are moving onto it. You do not need prior experience with each product.

This role builds the company's authentication and identity systems. It is not a DevOps, SRE, cloud or infrastructure role.

Responsibilities

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

Requirements

  • Architecture, administration and product configuration alone are not enough. The company wants to hear what you personally implemented, tested, automated and supported in production.
  • Substantial hands-on experience building and running platforms or shared infrastructure for software engineering teams.
  • Strong coding and scripting for infrastructure, automation, deployment tooling or integrations. You should be comfortable maintaining code, reviewing changes and writing automated tests.
  • Experience automating provisioning, configuration, deployment and operational tasks through version-controlled, repeatable workflows.
  • Production experience with Kubernetes and containers in a setting that delivers and operates software.
  • Practical experience with a major public cloud, Infrastructure as Code, CI/CD and GitOps.
  • Experience building reusable platform capabilities or self-service workflows that reduce manual work for engineers.
  • Solid grasp 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 the company's Go-based tooling and services and build 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 of where access decisions are enforced.
  • Ability to turn security requirements into working software, automated tests and maintainable platform capabilities.
  • You should have built identity systems rather than administered or configured them. That means having written authenticators, extensions or protocol flows, and understanding 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. Moving a live user base to a new identity provider without breaking logins is a strong fit.
  • Applicants whose experience is mainly cloud IAM policies, RBAC, Terraform, Kubernetes, CI/CD, or access governance and joiner-mover-leaver processes, with identity as just one tool among many, will not be progressed.
  • Particularly welcome: production experience with Curity, especially extending it, automating its configuration and lifecycle, or running it within a software platform.
  • Particularly welcome: engineering and running Keycloak in a software product, including customisation, automated delivery or migrations.
  • Particularly welcome: fine-grained authorisation built on SpiceDB or a comparable relationship-based engine.
  • Particularly welcome: deeper experience with enterprise federation, SAML, policy-as-code, or authentication and authorisation in distributed multi-tenant systems.
  • Particularly welcome: self-service identity capabilities, APIs or SDKs used by other engineering teams.
  • Particularly welcome: Go, PostgreSQL and Kafka or RedPanda in production.
  • These are extras, not substitutes for strong platform, coding and automation skills. Strong platform engineers with relevant authentication and authorisation foundations are encouraged to apply even without these specific products.

Conditions

Hybrid working is supported, with flexibility to suit different needs and lifestyles.

You will 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 wants to know how you use AI in 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, not only autocomplete or chat.

The company welcomes people from all backgrounds and perspectives.

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