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 is building AI-native enterprise software for some of the world's largest organisations. It has billion-dollar revenue, more than 7000 employees across all continents, and delivers its software on a single cloud-based platform.

Two Principal Platform Engineers are being hired to unify authentication and authorisation across the next-generation enterprise platform. The shared services you build will be the ones product engineering teams rely on.

The team is merging a fragmented authorisation setup into one model that runs across three hosting environments: the cloud-native platform, the legacy hosting platform and the lifecycle cloud. It has to be correct, fast and dependable 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. You do not need prior experience with any of these products.

This role builds identity systems. It is not a DevOps, SRE, cloud or infrastructure role. You should have built identity systems rather than administered or configured them, and most of your recent week would have involved writing code.

You should be a hands-on engineer who builds through code and automates by default. Your experience might come from infrastructure as code, deployment pipelines, automation, platform tooling or service integrations. What counts is reliable, repeatable capability that teams use to ship and run software.

Backgrounds in platform engineering, infrastructure, SRE, identity engineering or systems integration are all welcome, as long as you have substantial hands-on experience building or extending platform capabilities in code.

Software development experience is especially valued but not required. Coding that grew out of platform, infrastructure or SRE work counts.

Identity and access is the domain you will work in, and specialist experience there is especially welcome. Every product, service and AI agent has to prove who it is before acting, and you will own that end to end in a small team.

Candidates whose experience 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. That is a different discipline and team.

Responsibilities

  • Design and build platform services, APIs and automation for authentication and authorisation.
  • Own those services 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.

Requirements

  • 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.
  • Automate provisioning, configuration, deployment and operational tasks through version-controlled, repeatable workflows.
  • Production experience with Kubernetes and containers, delivering and running software applications.
  • 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 understanding 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.
  • Willingness to work with Go-based tooling and services and to develop those 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.
  • An 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.
  • Understanding of role-based, attribute-based and relationship-based access control models.
  • The ability to reason about correctness, latency, consistency and the traceability of authorisation decisions.
  • Understanding of token lifecycle management, enterprise federation, SSO and external identity-provider integration in a customer-facing platform.
  • An approach to reliability that covers observability, performance testing, safe rollouts, rollback, backup and recovery.
  • Experience diagnosing production failures and using code or automation to prevent them from recurring.
  • Sound judgement across distributed systems, relational data and event-driven services.
  • Using AI seriously in your engineering, as part of how you design, build and ship, not only for autocomplete.
  • Include a paragraph about one authentication-system piece you built, such as a custom authenticator or extension, a protocol flow, a key or token problem you solved, or a migration you ran. Expect detailed questions about it.
  • Valuable: familiarity with fine-grained authorisation engines or policy-as-code approaches.
  • Strong advantage: experience developing application or backend services.
  • Particularly welcome: deeper experience engineering and operating authentication infrastructure at scale.
  • Particularly welcome: production experience with Curity, especially extending it, automating its configuration and lifecycle, or operating it within a software platform.
  • Particularly welcome: experience engineering and operating Keycloak in a software product, including customisation, automated delivery or migrations.
  • Particularly welcome: fine-grained authorisation built with 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: experience building self-service identity capabilities, APIs or SDKs that other engineering teams use.
  • Particularly welcome: experience with Go, PostgreSQL, and Kafka or RedPanda in production.
  • Strong platform engineers with relevant authentication and authorisation foundations are encouraged to apply even without experience of these specific products.

Conditions

Hybrid working is available, and the company values flexibility so you can work in the way that suits you.

You stay close to the code while helping other engineers make sound architectural decisions. Clear technical reasoning, constructive challenge and ownership from design through production matter here.

The company wants to understand how you combine AI-assisted engineering with your work: what you delegate, how you review and test the results, and how you stay accountable for the software you ship.

The company values diverse perspectives and an inclusive workplace.

Where you’d work

Part of the week in the office

About the company

IFS

  • Industry: SaaS

Office in Dublin, Ireland

Also hiring in Krakow, Poland, Madrid, Spain, Dusseldorf, Germany 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
  • Dublin, Ireland

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