Staff Site Reliability Engineer

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

Staff Site Reliability Engineer to define how Axon builds and operates its core platforms, focusing on Zero Touch (controlled, compliant execution framework) and identity/security foundations. The role involves designing and building platforms, tooling, and guardrails for engineers, with a strong emphasis on automation, self-service, policy-by-default, security, identity, and auditability in regulated environments. Collaboration with product and platform teams is key, particularly in a modern, AI-driven environment.

What you'd actually do

  1. Lead the design and implementation of Zero Touch, Axon’s controlled, compliant execution framework for operational and change workflows.
  2. Define opinionated workflows, APIs, and abstractions that allow engineers to execute infrastructure and application changes safely, repeatably, and with strong guardrails.
  3. Embed policy‑as‑code, approvals, and audit trails into the framework so that compliance requirements are enforced by default, not as an afterthought.
  4. Partner with Identity, Security, and Platform teams to design secure patterns for authentication, authorization, and workload identity across cloud platforms.
  5. Define and standardize how services integrate with SSO/OIDC, RBAC, secrets management, certificate management, and key management so that platform workflows and APIs are identity‑aware and least‑privilege by design.

Skills

Required

  • 10+ years of experience in software engineering, with a focus on infrastructure, platform, or reliability engineering.
  • Strong programming skills in one or more languages such as Go, TypeScript, Python, or Java, with an emphasis on building services and tooling, not just scripts.
  • Experience operating and scaling public‑facing, distributed systems, including designing for availability, latency, and graceful degradation.
  • Deep familiarity with Infrastructure as Code (e.g., Terraform, CDK, CloudFormation) and modern CI/CD practices, including how to model policies, environments, and workflows as code.
  • Demonstrated experience building or owning platforms that other engineers depend on (e.g., deployment frameworks, execution engines, internal developer platforms, or SRE tooling).
  • Practical experience with identity and access management: Integrating applications and platforms with SSO/OIDC providers and enforcing RBAC/ABAC.
  • Designing safe patterns for secrets management, key management, and workload identity.
  • Working with security and compliance part

What the JD emphasized

  • highly regulated environments
  • correctness, traceability, and least privilege are non‑negotiable
  • compliance requirements are enforced by default, not as an afterthought
  • identity-aware and least‑privilege by design