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 €75K - 105K 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 AI-native enterprise software. The team is hiring two Principal Platform Engineers to build shared authentication and authorisation capabilities that product engineering teams rely on.

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

The work is to bring a fragmented authorisation setup into one model across three hosting environments: the cloud-native platform, the legacy hosting platform and the lifecycle cloud. The result must be correct, fast and reliable in distributed, multi-tenant systems.

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

Identity underpins every product, service and AI agent, since each must prove who it is before acting. You would own this end to end in a small team.

Experience moving a live user base to a new identity provider without breaking logins suits this role well.

The company has 7000+ employees on all continents and revenue in the billion-dollar range.

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 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 Go code.

Requirements

  • You have built identity systems rather than only administering or configuring them. You have written 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.
  • What counts is what you personally implemented, tested, automated and supported in production, not architecture or product configuration alone.
  • 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 maintain code, review changes and write automated tests.
  • You have automated provisioning, configuration, deployment and operations through version-controlled, repeatable workflows.
  • Production experience with Kubernetes and containers in a team that delivers and operates software.
  • Practical experience with a major public cloud, Infrastructure as Code, CI/CD and GitOps.
  • You have built reusable platform capabilities or self-service workflows that cut manual work for engineering teams.
  • You understand APIs, networking, data stores and distributed-system behaviour, and you can troubleshoot production issues.
  • You have shown technical leadership through design decisions, code reviews, engineering standards and support for other engineers.
  • You have hands-on experience implementing authentication and access control in applications, APIs or shared platform services.
  • You know OAuth 2.0, OpenID Connect and token-based authentication, including secure validation, trust boundaries and common failure modes.
  • You understand enterprise federation, SSO and external identity-provider integration in a customer-facing platform.
  • You understand permission models, least privilege and tenant isolation, and can explain where access decisions are enforced.
  • You can reason about the correctness, latency, consistency and traceability of authorisation decisions.
  • You turn security requirements into working software, automated tests and maintainable platform capabilities.
  • You build reliable systems with observability, performance testing, safe rollouts, rollback, backup and recovery, and you use code or automation to stop production failures from recurring.
  • You have sound engineering judgement across distributed systems, relational data and event-driven services.
  • Application or backend development experience is a strong advantage but not required. Your coding may come mainly from infrastructure and platform work. You should be willing to work in Go-based tooling and services and build the skills you need.
  • Particularly welcome if you have production experience with Curity, especially extending it, automating its configuration and lifecycle, or running it as part of a software platform.
  • Particularly welcome if you have engineered and operated Keycloak in a software product, including customisation, automated delivery or migrations.
  • Particularly welcome if you have built fine-grained authorisation with SpiceDB or a comparable relationship-based engine.
  • Particularly welcome if you have deeper experience with enterprise federation, SAML, policy-as-code, or authentication and authorisation in distributed, multi-tenant systems.
  • Particularly welcome if you have built self-service identity capabilities, APIs or SDKs that other engineering teams use.
  • Particularly welcome if you have used Go, PostgreSQL and Kafka or RedPanda in production.
  • These 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 these products.

Conditions

The role offers flexibility and hybrid working options.

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 team wants to know how you use AI in engineering: what you delegate, how you review and test the results, and how you stay accountable for the software you ship.

If your 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, this role is not a fit and your application will not progress.

The company welcomes people from all backgrounds and perspectives.

Where you’d work

Part of the week in the office

About the company

IFS

  • Industry: SaaS

Office in Dusseldorf, Germany

Also hiring in Krakow, Poland, Madrid, Spain, Dublin, Ireland and 9 more places

9 of their 48 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
Details12 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
Europe
Show 6 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
Europe
Office
  • Dusseldorf, Germany

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