DevOps Engineer

About The Role The role owns the infrastructure that keeps production systems running at scale - Kubernetes clusters, CI/CD pipelines, cloud environments, and the observability stack that surfaces problems before customers notice them.

This team treats reliability as a product. The work spans hands-on automation, incident response, infrastructure-as-code, and platform improvements that remove toil for dozens of engineers shipping code daily.

Key Responsibilities

• Build and maintain Kubernetes infrastructure (EKS/GKE) across multiple environments, including cluster upgrades, autoscaling policies, and node lifecycle management
• Design and enforce infrastructure-as-code using Terraform and Terragrunt, keeping environments reproducible and drift-free
• Own CI/CD pipelines in GitHub Actions or GitLab CI, reducing build times and deploying safely with canary and blue/green strategies
• Instrument and maintain observability tooling: Prometheus, Grafana, Datadog, and alerting that pages on real problems, not noise
• Lead incident response and blameless postmortems; drive root-cause fixes and set SLOs/SLIs for critical services
• Harden cloud security posture: IAM least-privilege policies, secrets management via Vault, and network segmentation across AWS or GCP
• Partner with product engineering teams to improve developer experience - golden paths, deployment automation, and self-service tooling

What We Are Looking For

• 4–8 years in DevOps, SRE, or platform engineering, with significant experience running production Kubernetes
• Deep hands-on expertise with at least one major cloud: AWS, GCP, or Azure
• Strong Terraform skills and a track record of managing large-scale infrastructure-as-code repositories
• Solid scripting/programming ability in Python, Go, or Bash for automation and tooling
• Experience building CI/CD pipelines and understanding of deployment strategies, rollbacks, and progressive delivery
• Background in incident management, on-call rotations, and reliability engineering practices (SLOs, error budgets)
• Bonus: HashiCorp Vault experience, service mesh (Istio/Linkerd), cost optimization/FINOPS, or Go development for internal tooling