AI Platform Engineer – GitOps & Kubernetes

Location: Bucharest, Romania (Hybrid)

Team: Platform Engineering

Level: Mid / Senior

Who We Are?

We're a small platform engineering team at Raiffeisen Bank Romania, and when I say small, I mean four people-small. Four people managing 75+ production applications, spread across 5 Kubernetes clusters (3 on EKS, 2 on-prem), backed by 200+ Git repositories. If that sounds either terrifying or exciting to you, we should talk.

The only reason this works is automation. We don't manage things manually. We build systems that manage things for us. GitOps isn't a buzzword here, it's the entire supply chain, from the moment a new repo is created to the moment an app update ships to production and keeps itself up to date without anyone touching a keyboard.

We're growing, and we're looking for someone who gets that philosophy.

What You'll Be Working On:

• Owning the platform: Our deployment platform is built on FluxCD, running across EKS and on-prem clusters. You'll be helping maintain, extend, and improve it.
• Developer experience: We believe friction kills adoption. You'll build the kind of tooling that makes developers want to use the platform — Copier templates, Taskfile automations, the works.
• GitOps everything: Not just Kubernetes manifests — repo creation, CI pipelines, infrastructure config, dependency updates. If it can be in Git and reconciled automatically, it should be.
• Incident response and reliability: Small team, real production. You'll own what you build. We're not doing on-call, but we are the first line of support.

Our Stack:

We're not listing this to impress. We're listing it so you know what you're walking into:

• GitOps: FluxCD (with a fleet repo pattern and branch promotion strategy)
• Kubernetes: EKS + on-prem, Helm, Kustomize, tf-controller
• IaC: OpenTofu, Terragrunt
• CI: GitHub Actions
• Languages: Primarily Python; some JavaScript/Node for frontend services

What We're Looking For:

Must-haves

• Solid Kubernetes experience — you're comfortable with the control plane, not just kubectl get pods
• Familiarity with GitOps concepts and at least one GitOps tool (FluxCD or ArgoCD)
• IaC experience — Terraform or OpenTofu, bonus points for some Terragrunt exposure
• A genuine appreciation for developer experience and platform hinking
• You treat automation as a force multiplier, not a nice-to-have

Nice-to-haves

• FluxCD specifically (the more the better)
• Experience with Renovate beyond the defaults
• Copier, cookiecutter, or similar templating tools
• GitHub Actions at scale
• AWS / EKS experience
• Azure experience

Mindset-wise

• You'd rather spend a day automating something than a week doing it manually forever
• You think good developer experience is an engineering problem, not a documentation problem
• Small team doesn't scare you — it energizes you

What We Offer

• The chance to do meaningful platform work that actually ships
• A team that values clean systems, good tooling, and sharing knowledge
• Real ownership — no ticket queues, no bureaucratic approval chains for every PR
• Flexibility and hybrid work

Interview/Hiring Process

Initial, get-to-know, interview

Homework (1 week deadline)

Technical interview to talk about the homework