Atmora runs more than 40 client workloads across EKS and AKS, from a nine-node cluster carrying Kestrel Industrial's shop-floor telemetry to a two-region active/passive setup for Corvus Logistics. You will own the internal platform those delivery teams deploy onto: the Terraform module library, the Argo CD app-of-apps layout, and the paved path that takes a service from merge to production in under 12 minutes.
Full-time — on site
4-7 years in infrastructure, including at least one production Kubernetes estate you did not inherit already working
Jodhpur, India
Apply for this role
The work
What you will do
Maintain the Terraform module library used by every engagement, and keep drift close to zero through a weekly plan-and-review cycle across all accounts.
Run progressive delivery with Argo Rollouts — canary at 5 / 25 / 100 per cent with automated rollback on error-rate and latency gates.
Bring cloud spend down on two named accounts by 20-30 per cent through right-sizing,
spot node pools and storage tiering, without moving any SLO.
Own the observability stack (Prometheus, Loki, Grafana), including a cardinality budget currently set at 1.5 million active series.
Handle escalations on the infrastructure rotation and run blameless reviews afterwards.
You
What we look for
Kubernetes past the tutorial layer: scheduling, admission webhooks, PodDisruptionBudgets, and why your rolling update stalled.
Terraform written as reusable modules with sensible variable surfaces, not copied directories.
Linux networking you can debug — iptables or eBPF paths, DNS resolution inside a pod, MTU mismatches on overlay networks.
Go or Python valuable enough to build a controller or a one-off migration tool.
Judgement about when Kubernetes is the wrong answer and a pair of VMs behind a load balancer would serve the client better.