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 its next generation of AI-native enterprise software. This role creates the shared authentication and authorisation capabilities that product engineering teams rely on.

The team is hiring two principal platform engineers to bring one authorisation model across three hosting environments: the cloud-native platform, the legacy hosting platform and the lifecycle cloud. It must be correct, fast and dependable in distributed, multi-tenant settings.

The current stack uses SpiceDB on PostgreSQL for authorisation and Curity for authentication, with Keycloak estates moving onto it. Prior experience with each product is not required.

This is an identity engineering role, not a DevOps, SRE, cloud or infrastructure role. It offers substantial technical ownership of a critical platform capability with impact across the engineering organisation.

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 as 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

  • Hands-on experience building and running platforms or shared infrastructure for software engineering teams.
  • Experience building and maintaining infrastructure code, automation, delivery pipelines, integrations or platform tooling yourself.
  • Experience automating provisioning, configuration, deployment, upgrades and recovery through version control and repeatable pipelines.
  • Experience building self-service capabilities that cut manual work for developers.
  • Experience deploying and running containerised services on Kubernetes in a software delivery setting.
  • Practical experience with a major public cloud, Infrastructure as Code, CI/CD and GitOps.
  • Strong coding and scripting for infrastructure, automation, deployment tooling or integrations, including maintaining code, reviewing changes and writing automated tests.
  • Understanding of role-based, attribute-based and relationship-based access control in applications and APIs, including implementing permission checks or permission models.
  • Understanding of tenant isolation and security boundaries, and the ability to explain where access decisions are enforced.
  • Ability to reason about the correctness, latency, consistency and traceability of authorisation decisions.
  • Practical understanding of OAuth 2.0, OpenID Connect and token lifecycle management, including validation, trust boundaries and failure modes.
  • Experience implementing or extending authentication flows in software.
  • Understanding of enterprise federation, SSO and external identity-provider integration in a customer-facing platform.
  • Sound understanding of APIs, networking, data stores and distributed-system behaviour, with the ability to troubleshoot production issues.
  • An approach to reliability that covers observability, performance testing, safe rollouts, rollback, backup and recovery, and using code or automation to prevent repeat failures.
  • Evidence of technical leadership through design decisions, code reviews, engineering standards and support for other engineers.
  • Experience building identity systems, such as custom authenticators, extensions or protocol flows, and an understanding of how tokens are issued, signed, rotated and revoked, how sessions behave, and how OAuth, OpenID Connect, SAML and SCIM work underneath.
  • Ability to turn security requirements into working software, automated tests and maintainable platform capabilities.
  • Experience migrating a live user base onto a new identity provider without breaking logins is a good match for this role.
  • Backend or application development experience is a strong advantage but not required. Coding experience from platform or SRE work is accepted, and you should be willing to work in Go and build skills where needed.
  • Architecture, administration and product configuration alone do not qualify. You need to show what you personally implemented, tested, automated and supported in production.
  • We would particularly like to talk to you if you have production experience with Curity, especially extending it, automating its configuration and lifecycle, or running it in a software platform.
  • We would particularly like to talk to you if you have engineered and run Keycloak in a software product environment, including customisation, automated delivery or migrations.
  • We would particularly like to talk to you if you have built fine-grained authorisation with SpiceDB or a comparable relationship-based engine.
  • We 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.
  • We would particularly like to talk to you if you have built self-service identity capabilities, APIs or SDKs used by other engineering teams.
  • We would particularly like to talk to you if you have worked with 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 specific products.

Conditions

The company offers flexibility and hybrid work options so you can choose a setup that suits you.

You will stay close to the code while helping other engineers make sound architectural 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 results, and how you stay accountable for the software you ship.

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 progress.

The company celebrates diversity and welcomes people from many different backgrounds.

Where you’d work

Part of the week in the office

About the company

IFS

  • Industry: SaaS

Office in Krakow, Poland

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

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