Senior Software Engineer | Kubernetes Automation

What you'll be solving A pod is mid-request. The node it's running on is about to disappear - Spot is pulling the instance, or Autoscaler has flagged the node as underutilized and marked it for removal. The safe move is to wait.

The profitable move is to act now. Every team in this pipeline is built to close that gap: make the aggressive call and still guarantee nothing breaks. That guarantee is the hard part.

Deciding which nodes to kill, which pods to move, and which storage volume to resize is a genuinely hard optimization problem - several of them are P=NP-hard in the general case - and it has to run continuously, in production, faster than a human would ever attempt it by hand. Get it right and clusters run at half the cost. Get it wrong once and you've taken down something live.

This posting covers multiple teams working on different pieces of the same automation problem node placement algorithms and provisioning, deep integrations with tools like Karpenter, workload rightsizing (vertical and horizontal), moving running workloads between nodes without interrupting them, storage that scales itself, and GPU capacity optimization across clouds and regions. All of it runs in real time, in production, with no human tuning YAML in the loop. This is a location-specific opportunity.

We are currently accepting applications from candidates residing in the following European countries: Bulgaria, Croatia, Estonia, Greece, Hungary, Latvia, Lithuania, Poland, Romania, Slovakia, Cypru