We're assisting our client hiring a Platform Engineer with strong SRE practices to own the reliability, automation, and observability of a cloud-native platform on Azure. You'll work across infrastructure-as-code, Kubernetes, GitOps, and observability tooling to keep Java microservices running reliably at scale, and to make it easier for development teams to ship safely.
This role sits at the platform and infrastructure layer. You'll partner closely with application teams (and an application support function, where one exists), but your focus is the systems underneath the applications, not day-to-day business-logic triage.
What you'll do
- Design, build, and maintain Terraform modules for Azure infrastructure, including state management and multi-environment workspace strategy
- Operate and evolve AKS clusters: upgrades, node pool scaling, networking (CNI, NSGs), and security posture
- Own the GitOps delivery pipeline using ArgoCD, including app-of-apps structure, sync strategies, and drift detection and remediation
- Run and improve the Elastic Stack observability platform: ingestion pipelines, index lifecycle management, dashboards, and alerting
- Define and track SLOs/SLIs for key services and drive error-budget conversations with engineering teams
- Participate in an on-call rotation, lead incident response, and write blameless postmortems for platform-level incidents
- Reduce operational toil through automation, self-service tooling, and golden paths for teams deploying Java microservices
- Partner with backend teams to right-size Kubernetes resource requests/limits, tune JVM behavior in containers, and improve readiness/liveness probes
- Contribute to capacity planning and cost optimization across the Azure estate
What we're looking for
- Azure: Solid hands-on experience with core Azure services in production
- Terraform: Demonstrable experience writing and maintaining modules, managing state, and working with workspaces, not just running apply against an existing codebase
- Kubernetes/AKS: Real operational experience with cluster upgrades, node pool management, and troubleshooting networking and scheduling issues
- ArgoCD: Practical GitOps experience specifically with ArgoCD (app-of-apps, sync waves, handling drift). Flux experience alone won't fully transfer
- Elastic Stack: Experience operating Elasticsearch/Kibana (or ECK on Kubernetes) beyond reading dashboards, including ingestion pipelines, index lifecycle, and scaling
- SRE fundamentals: Experience with SLOs/SLIs, on-call rotations, and structured incident response and postmortems
- Scripting/automation: Proficiency in at least one of Bash, Python, or Go
Nice to have
- Familiarity with Java/JVM operational characteristics (GC behavior, container memory limits, startup/warm-up). You don't need to write Java
- Experience with Wiz, Defender for Cloud, or similar CSPM/security tooling
- Experience building internal developer platforms or self-service tooling
- Knowledge of cost management and FinOps practices in Azure
What this role is not
- Writing or maintaining Java application code
- First-line business or data triage (such as reprocessing failed orders or handling user-reported app bugs). That sits with application support, where that function exists