Sr Software Engineer II, Storage

Axon•Washington, DC

1d•Hybrid

About The Position

Join Axon and be a Force for Good. At Axon, we’re on a mission to Protect Life. We’re explorers, pursuing society’s most critical safety and justice issues with our ecosystem of devices and cloud software. Like our products, we work better together. We connect with candor and care, seeking out diverse perspectives from our customers, communities and each other. Life at Axon is fast-paced, challenging and meaningful. Here, you’ll take ownership and drive real change. Constantly grow as you work hard for a mission that matters at a company where you matter. Axon Storage keeps petabyte-scale evidence safe for customers whose investigations depend on it. As the team grows into the next phase of its stewardship, we're investing in systems that govern themselves — correctness and invariants enforced in code, errors that software can respond to, interfaces that give the next engineer a wall at their back to build against. You'll help lead that push, shaping the architecture and the engineering discipline that make reliability the default rather than an act of heroism.

Requirements

8+ years building and operating distributed systems in production — not just designing them, running them at scale with real traffic and real failures
BS in Computer Science, a related technical field, or equivalent practical experience — we care about what you've shipped and kept running, not where you learned it
Distributed-systems expertise paired with an operability-first mindset — you treat a system's 3am behavior as a design requirement, not a post-incident learning
A track record of designing self-governing systems — invariants enforced in code, errors routed to software rather than humans, boundaries that give the next engineer a wall at their back
Strong opinions held with respect, and the ability to genuinely take others' perspectives on — you commit, take action, and deliver, and you do it across org boundaries without needing to own them
Comfort with the unknown — you'll take smart risks on systemic change when the alternative is watching a known problem keep costing the team
A track record of growing other engineers, not replacing them — the win is a team that operates at a higher level, not a hero who carries it

Responsibilities

Refine how the team responds to incidents — finding the patterns under individual action items and the software fixes that eliminate whole classes of concern
Audit the current surface area, identify duplication, and partner with the manager on a reliability-and-migration roadmap the team can execute against
Design interface contracts and invariant checks that let the team build forward without a single person needing to hold the domain in their head
Carry a banner — bring a clear point of view on great software and take the team with you, through alignment rather than assertion
Mentor teammates from "writes working features" toward "produces great software"