DevOps Engineer
saxon globalRedwood City (CA)
About the role
Job TitleLead the design and management of highly available, scalable Kubernetes infrastructure using Amazon EKS.Design, manage and optimize large scale EKS clusters with thousands of nodes. Implement and manage infrastructure using Infrastructure as Code (IaC) with Terraform and Terragrunt. Champion a Git-first approach to infrastructure and CI/CD automation. Build and maintain robust CI/CD pipelines using Harness to streamline application delivery across environments. Drive infrastructure automation and environment consistency across development, staging, and production. Design and implement monitoring and observability solutions using New Relic, ensuring performance visibility and uptime. Securely manage secrets using AWS Secrets Manager Support production systems through incident management, root cause analysis, and proactive reliability improvements. Collaborate with engineering and security teams to define best practices for deployment, security, and scalability. Mentor and guide junior DevOps team members and developers in adopting modern infrastructure practices. Support the larger team as an active contributor offering innovative ideas to solve problems, improve performance and drive what comes next.
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.