Senior Site Reliability Engineer
Senior Site Reliability Engineer
Posted yesterday
SENIORITY
Lead
About the role
- Design, develop, and maintain Kubernetes operators and controllers in Go to automate deployment, configuration, scaling, and lifecycle management of Stargate services
- Own and manage Stargate production releases and deployment pipelines using
- GitOps practices
- Drive operational excellence initiatives including metrics collection, log aggregation, uptime monitoring, KPI tracking, and SIM Integration
- Maintain and achieve 99.99% (four nines) to 99.999% (five nines) uptime SLAsDesign, develop, and maintain Helm charts for Stargate and related infrastructure components
- Implement and manage progressive deployment strategies including canary deployments and blue-green deployments
- Oversee critical Kubernetes infrastructure including volume management, DNS configuration, load balancer provisioning, and secret monitoring/management
- Manage and optimize Kubernetes deployments and related AWS services
- Implement and maintain observability stack using OpenTelemetry for comprehensive monitoring and alerting
- 5+ years of experience in Software Engineering, Site Reliability Engineering, DevOps, or a related discipline
- Kubernetes administration experience with elevated cluster access in production environments
- Strong software development experience in one or more programming languages (C++, Go, Node, Python, etc.)Strong proficiency writing and maintaining Helm charts for complex, multi-component applications
- Hands-on experience implementing canary deployments, blue-green deployments, and other progressive delivery patterns
- Deep knowledge of Kubernetes infrastructure management: persistent volumes, DNS/networking, load balancers, and secrets management
- Production experience with GitOps workflows and Flux CD
- Experience developing Go-based Kubernetes operators and controllers
- Experience with AWS cloud services, particularly EKS (Elastic Kubernetes Service), Secrets Manager, VPC networking, IAM, and AWS Load Balancers
- Experience with Karpenter for Kubernetes node autoscaling and cluster optimization
- Experience with OpenTelemetry instrumentation and observability platforms
- Kubernetes certifications (CKA, CKAD, or CKS)
- Experience building and maintaining CI/CD pipelines (GitHub Actions, Jenkins, GitLab CI, etc.)Knowledge of infrastructure-as-code tools (Terraform, CDK)
- Experience implementing SRE practices including SLIs, SLOs, and error budgets
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
