> Markdown version of [/jobs/ext/4269236-site-reliability-engineer-remote](https://www.wearedevelopers.com/jobs/ext/4269236-site-reliability-engineer-remote). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Site Reliability Engineer (Remote) - **Company:** Cisco Systems, Inc. - **Location:** Boulder, CO, United States (Remote available) - **Experience:** Experienced - **Salary:** $128,600.0 - $184,900.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Amazon Elastic Compute Cloud, Amazon S3, Microsoft Azure, Configuration Management, Disaster Recovery, Python (Programming Language), Nagios, Reliability Engineering, Scripting, System Availability, Grafana, Infrastructure as Code (IaC), Git, Build Management, Containerization, Infrastructure Automation Frameworks, Route53, Functional Programming, Puppet, Software Coding, Terraform, Software Version Control, Docker - **Published:** October 17, 2026 - **Apply:** https://dejobs.org/x/x/78FBE0113F2244ADBE949BAC247F3456/job/ ## About the Role * Bachelor's degree and 5 years of related experience, or Master's degree and 3+ years of related experience. * Practical experience with major cloud platforms (AWS, GCP, or Azure) and core services (e.g., EC2, S3, Lambda, Route53) * Applied experience with Infrastructure as Code (IaC) and configuration management, specifically Terraform and Puppet * Applied experience with CI/CD pipelines and version control (Git) * Prior experience writing code in Python or another scripting language to automate infrastructure and execute maintenance windows * Applied experience participating in an on-call rotation, including incident response, troubleshooting, and writing root cause analyses * Prior experience monitoring and alerting on production services against SLOs and SLAs Preferred Qualifications * Experience with containerization and orchestration tools, specifically Docker and Kubernetes * Experience with production monitoring and observability tools such as SignalFx and Nagios * Familiarity with utilizing AI as part of an automation strategy to reduce repetitive tasks * Experience designing and implementing tools, frameworks, or automation toolsets that reduce operational toil * Experience supporting automated rollbacks and zero-downtime release practices * Experience troubleshooting security controls and contributing to changes that address security issues * Experience mentoring or acting as a resource for colleagues with less experience * Ability to build productive working relationships with peer stakeholders across product and engineering teams. ## Description This position will perform work that the U.S. government has specified can only be performed by a U.S. citizen on U.S. soil This position is remote and can be performed from locations within the United States. This role requires reliable internet connection and the ability to work independently in a remote environment. **Meet the Team ** The Site Reliability Engineering team keeps production services available, scalable, and secure for customers worldwide. We own the monitoring, alerting, and incident processes that help us meet internal Service Level Objectives (SLOs) and customer-facing Service Level Agreements (SLAs). Our work underpins every product release, from automated rollbacks to zero-downtime deployments, so customers can rely on the platform. We are a collaborative group of engineers who share an on-call rotation, learn from every incident through blameless post-mortems, and support one another across regions. If you enjoy turning operational challenges into automation and making systems measurably more resilient, you will fit right in. **Your Impact ** Improve the reliability, scalability, and performance of production services by writing code that automates releases, rollbacks, and recovery. Serve as an on-call SRE, troubleshooting and debugging complex issues across infrastructure and platform services, then document root causes in post-mortems to prevent repeat incidents. Test high availability and disaster recovery measures, and recommend changes that remove single points of failure. Design and build new tools, frameworks, and automation toolsets to reduce operational toil and speed up the detection of potential issues. Success looks like services that consistently meet their SLOs and SLAs, fewer repeat incidents, and colleagues who benefit from the practices you share.