> Markdown version of [/jobs/ext/4620937-staff-site-reliability-engineer](https://www.wearedevelopers.com/jobs/ext/4620937-staff-site-reliability-engineer). 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). --- # Staff Site Reliability Engineer - **Company:** Verrus, LLC - **Location:** Mountain View, CA, United States - **Experience:** Experienced - **Salary:** $250,000 - $300,000 - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Code Review, Continuous Integration, Data Governance, Software Debugging, Distributed Systems, Modbus, Reliability Engineering, Prometheus, Software Engineering, Transmission Control Protocol (TCP), Data Logging, Grafana, HybridCloud, Kubernetes, Process Control Systems, Production Code, Functional Programming, Api Gateway, Software Coding, AWS EKS, Golang - **Published:** November 7, 2026 - **Apply:** https://www.juju.com/job/28_25304_ac79bca3605cb900d01597c7ea60aadc ## About the Role * 8+ years of experience in Software Engineering, SRE, or Production Engineering, with at least 3 years operating at a Senior or Staff level on production-critical systems. * A track record of building force-multiplier infrastructure: you can point to specific platforms, tools, or systems you designed, wrote significant code for, and shepherded into broad production use. * Strong production-grade proficiency in Golang. You have shipped non-trivial Go services and tooling, and generally understand how best to use Go for infrastructure tooling. * Deep experience with public cloud (AWS, GCP) and container orchestration (Kubernetes) - including production operation and failure-mode reasoning, not just deployment. * Proven track record of managing infrastructure as code at scale. * Strong distributed-systems foundations: consensus, replication, RPC and async messaging architectures, capacity planning under uncertainty, and the failure modes that come with each. * Demonstrated incident-leadership experience: you have served as incident commander on serious production events, run rigorous postmortems, and driven the structural fixes through to closure. * Genuine appetite for being hands-on. You want to spend most of your week writing code and debugging real systems, not running working groups., * Experience with EKS-A provisioning or hybrid-cloud environments. * Experience with Kubernetes and familiarity with Crossplane. * Familiarity with NATS or other publish/subscribe technologies. * Familiarity with cuelang. * Some familiarity with Rust and functional programming basics. * An understanding of distributed systems and general RPC architectures. * Familiarity with energy data standards and protocols (e, g, Modbus TCP, DNP3, IEC-61850), IoT protocols, or industrial control systems. * Ability to efficiently identify and resolve issues using problem-solving and communication skills. * Adaptability to work in a rapidly changing, fast-paced environment and picking up new technical areas of expertise. ## Description * Hands-on engineering: write production-grade code (primarily Golang) for the platform, services, tooling, and automation the rest of engineering depends on. The highest-leverage and gnarliest problems will land on your queue. * Platform building: design, build, and support the internal platform spanning AWS EKS, on-prem HCI, and EKS-A - including the components that bridge controls and physical-infrastructure boundaries. Make it easy for other teams to ship reliably on top of it. * Application engineering: write and operate the production services this team directly owns - public API gateway, authentication, edge processing, and others - with the same care for testing, observability, and operational ergonomics that you bring to the platform. * Production hardening: when things break, lead the investigation, run rigorous postmortems, and write the structural fixes yourself when the right answer is code rather than process. * Cyber-physical reliability: build the tooling and abstractions that make reliability engineering coherent across software, infrastructure, and BESS/controls layers - including the framework that distinguishes what can be safely chaos-tested in software, what requires structured GameDays, and what must remain simulation-only. * SLOs and observability: implement SLO-driven operations - error budgets, burn-rate alerting, and the monitoring/logging/tracing stack (Prometheus, Grafana, and adjacent tooling) - and partner with service teams to adopt them. * Infrastructure as Code: grow the IaC and developer-tooling foundations other teams rely on, with a strong emphasis on testability, reproducibility, and ergonomics that actually get adopted. * CI/CD: build and improve the CI/CD pipelines across environments, balancing deployment velocity against the safety constraints of a physically-deployed product. * Cross-team collaboration: work directly with networking, controls, ME, and product engineers on system designs - push back on proposals that won't operate reliably and contribute concrete alternatives, often in the form of working prototypes. * Mentorship through doing: raise the bar through code review, design review, and pairing with senior engineers. Lead by what you ship and what you push back on.