01
Autoscaling with Karpenter
Node pools that fit the workload, Spot capacity with interruption handling, and consolidation that respects PodDisruptionBudgets.
Senior / Staff
Hire senior Kubernetes engineers and DevOps SREs
Platform engineers who run Kubernetes on EKS and GKE — autoscaling, GitOps delivery, networking and observability — with cost and reliability measured in your own dashboards.
Role profile
What we look for in a Senior Kubernetes & DevOps SRE
Seniority and experience are agreed in the proposal, and you interview every engineer before they start. These are the skills that interview should test.
02
GitOps delivery with ArgoCD
Cluster and application state declared in Git, synced automatically, and rolled back by reverting a commit.
03
Networking and service mesh
Cilium eBPF networking, mutual TLS between services, and ingress through the AWS Load Balancer Controller or Gateway API.
Typical work
What a Senior Kubernetes & DevOps SRE typically works on
Examples of the scope this role is hired for. Your statement of work sets the actual deliverables and how they are accepted.
- 01Multi-AZ EKS clusters defined in Terraform
- 02Compute cost reduction with Karpenter and Spot, measured against your current bill
- 03Blue/green and canary releases with Argo Rollouts
- 04Prometheus, Thanos and Grafana monitoring with alerts that page on symptoms
Stack and tools
What this role works with day to day. Tell us your stack and we’ll say plainly which parts we can staff.
- Kubernetes
- Amazon EKS
- Google GKE
- Karpenter
- ArgoCD
- Terraform
Technology guides
Related service
Cloud & DevOps engineeringA ranked plan to shrink the cloud bill and make deploys boring — with guardrails your team keeps running after we leave.
How hiring works
Four steps, agreed in writing before anyone starts
01
Tell us the role
The stack, the seniority you need, the hours you want covered, and any certifications the work requires. We reply within one business day.
02
We propose engineers
A written proposal sets out who we'd put forward, their seniority and experience, the scope, and the terms. If we can't staff the role well, we say so.
03
You interview every engineer
Nobody starts on your codebase until you've interviewed them and agreed. Use the skills on the role page as your interview checklist.
04
Working arrangements go in the SOW
Working-hours overlap is agreed for each engagement and written into the statement of work — the shared window, who shifts hours, and how handoffs work outside it.
QuantmHill provides development teams from India for Indian startups and SMEs. Role profiles describe project capabilities; availability is confirmed for your engagement. Our team works on India Standard Time. Project working hours, availability and handoff responsibilities are agreed before kickoff.
Need specific certifications? Tell us at the start and we'll confirm whether we can staff to that requirement before you sign. There are no recruiting fees.
FAQ
Questions about hiring a Senior Kubernetes & DevOps SRE
Answered the way we would on a call. If yours isn’t here, send it — we reply within one business day.
Need specific certifications? Tell us at the start and we'll confirm whether we can staff to that requirement before you sign. In the interview, ask the engineer to walk you through a cluster upgrade or an incident they handled — it tells you more than a certificate.
Yes, as a retainer covering cluster upgrades, security patching and monitoring. Hours of cover, on-call arrangements and response times are agreed in the statement of work rather than assumed.
Related roles
Similar and adjacent roles
Add a Senior Kubernetes & DevOps SRE to your team
Tell us the stack, the seniority you need and the hours you want covered. We reply within one business day, and you interview every engineer before they start.