Infrastructure Architect

Axon Axon · Enterprise · AZ · 4705 Core IT Infrastructure

Axon is seeking an Infrastructure Architect to lead the technical direction, architectural integrity, and operational maturity of its core infrastructure platforms, including virtualization, storage, cloud (Azure/AWS), databases, and foundational platform services. The role involves managing a team of engineers, designing and approving infrastructure solutions, driving modernization efforts, and establishing standards for resilience and observability. This is a hands-on leadership role focused on building scalable and durable platforms.

What you'd actually do

  1. Own the architecture and technical direction for Axon’s infrastructure platforms, including VMware, storage, cloud (Azure/AWS), databases, and core platform services.
  2. Lead and manage a team of infrastructure engineers, providing technical guidance, prioritization, and mentorship while ensuring high operational standards.
  3. Design, review, and approve infrastructure solutions supporting corporate IT and Axon product/R&D teams, balancing scalability, security, reliability, and cost.
  4. Remain hands-on in critical areas such as virtualization, cloud engineering, storage, and database platforms, serving as a senior escalation point.
  5. Partner closely with Network, Platform, Security, and Product teams to deliver well-architected, cross-functional solutions.

Skills

Required

  • 8+ years of experience in infrastructure engineering
  • Demonstrated ownership of complex on-prem and cloud environments
  • Deep hands-on expertise with VMware virtualization
  • Enterprise storage expertise
  • Cloud infrastructure expertise (Azure required; AWS preferred)
  • Strong experience with database and platform services
  • Proven experience leading and managing technical infrastructure teams
  • Proven experience defining, tracking, and reporting on infrastructure metrics, KPIs, and dashboards
  • Hands-on experience with Infrastructure as Code (IaC) and automation tools (e.g. Terraform, Ansible, GitHub Actions)

Nice to have

  • AWS preferred

What the JD emphasized

  • Azure required