Site Reliability Engineer II

Axon Axon · Enterprise · Office, WA · 1505 SAAS Ops

Site Reliability Engineer II role focused on networking aspects of Axon's cloud-native services, including Istio service mesh, Kubernetes operations, and infrastructure-as-code on Azure. The role involves building and operating infrastructure, advising software engineers on networking, and ensuring high availability (4x9s) under strict regulatory regimes like FedRAMP.

What you'd actually do

  1. Work on a mixed infrastructure/software team that owns the most important networking-related aspects of Axon systems
  2. Help with Axon’s journey into Istio service mesh applications that are still in their infancy at Axon, but form the foundation of Axon’s future strategy to scale over the next few years.
  3. Be a builder and operator, advancing new features while simultaneously stewarding existing system components subject to strict regulatory regimes like FedRAMP, managing vulnerabilities with timely precision.
  4. Advise software engineers on networking topics through design reviews, ad hoc questions, and pair programming sessions.
  5. Automate routine maintenance of the cloud platform with minimal downtime (4x9s availability). Example: TLS certificate management and automation is a sprawling responsibility in large systems, a mine-field of potential unforced errors that can impact availability

Skills

Required

  • Able to gain CJIS clearance to ensure full US production access
  • Strong experience working on globally diverse 24/7 high volume systems.
  • A demonstrated experience and inclination towards networking topics, anything from infrastructure to services (e.g. service mesh applications, rate limiting, public and private ingress and egress)
  • Excellent problem-solving skills, with the ability to debug problems in cloud native distributed systems.
  • Familiarity with the GitOps approach to software delivery.
  • Design and delivery of infrastructure-as-code on public cloud (Axon uses Azure, but other experience is fine)
  • Experience operating components or services in Kubernetes clusters at scale.
  • Experience in one or more of these common languages used at Axon: Python, Golang, Scala/Java.
  • Empathy to support the needs of software engineers with widely varying levels of awareness of networking concepts

What the JD emphasized

  • strict regulatory regimes like FedRAMP
  • 4x9s availability
  • networking topics