Axon Software Engineer interviews typically combine a recruiter screen, LeetCode-style live coding, and behavioral rounds. Some candidates also report system design or a take-home. Most reports here ended without an offer.
$160K
Avg. Base Comp
$208K
Avg. Total Comp
4-6 rounds
Typical Rounds
2-4 weeks
Process Length
Candidates describe the Axon Software Engineer loop as a recruiter screen followed by live coding that leans on data structures and algorithms, then a behavioral stretch. Hash maps come up repeatedly, along with binary search, strings, recursion and dynamic programming. Reported problems include an officer-activity pattern question, Number of Islands, palindromes, an interleaving-strings problem, and splitting a list of image heights into three near-equal groups. In that last case the interviewer kept changing the requirements, so expect to defend edge cases and time complexity as the problem shifts.
Several candidates say the rounds were more than coding. Some describe a product-flavored design prompt, such as one tied to image detection and license plate recognition, or one integrating two Axon technologies. Others report two separate system design rounds, a take-home design presented to team members, or a Kafka-style queue design. Behavioral rounds are often substantial: candidates mention resume deep dives, STAR-style follow-ups, "why Axon", ownership, and handling ambiguity or ethical issues.
Experiences vary a lot in logistics. Some candidates describe a bare-bones text editor, a strict 30-minute coding limit, or several interviews packed into a few days. Others report a smoother, friendlier process. Most reported outcomes were rejections, though one candidate received an offer after a fairly manageable set of coding rounds. Practice explaining your reasoning aloud, sketch a plan before coding, and keep a few adaptable project stories ready.
Synthesized from 31 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Axon process.
I didn't get an offer from Axon, but the process was a positive one overall, so here's how it went. It started with a 20-minute recruiter call where we talked through my background and why I was interested in the company. It was a pretty standard HR-style screen, mostly walking through my CV and work experience.
Next came the live coding round, which opened with more conversation about my work experience before moving into the problem. I was given a question from their LeetCode-style list, and the difficulty felt like easy to medium. I was able to solve it, but this is where I slipped: I couldn't explain some of the tradeoffs in my code or clearly talk through the complexity. Looking back, getting a working solution wasn't enough, and they clearly cared about the reasoning behind the choices.
The process I went through ended with a rejection, so I can't speak firsthand to the later stages. The final stage is a block of three back-to-back interviews: a 90-minute engineering-with-AI round, a 45-minute session with an engineering manager, and a 60-minute culture fit conversation. That's a long stretch in a single sitting, so it's worth planning your energy for it.
My main takeaway is to treat the coding round as a conversation. Solve the problem, but be ready to defend every decision and state the time and space complexity out loud without hesitation.
Prep tip from this candidate
In the live coding round, practice explaining the tradeoffs and time/space complexity of your solution out loud, since a working answer alone wasn't enough. Also prepare for the final stage, which runs three back-to-back interviews: a 90-minute engineering-with-AI round, an engineering manager round, and a culture fit round.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Axon
Describing a data project and its challenges
| Question | |
|---|---|
| Scalable Data Pipelines | |
| Marketing Workflow Optimization | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Top 3 Users | |
| Raining in Seattle | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Find the First Non-Repeating Character in a String | |
| Comments Histogram | |
| Minimum Change | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| Upsell Transactions | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| P-value to a Layman | |
| Maximum Profit | |
| First Touch Attribution | |
| Google Maps Improvement | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR call covering their background, projects, motivation for Axon, and sometimes location preferences and salary expectations. Most describe it as straightforward. Prepare a concise introduction and a clear answer for why Axon, since that question may recur in later rounds.
Several candidates describe a first technical step that was a live LeetCode-style coding session, often easy-to-medium and built on hash maps, strings or binary search. Others report a hiring manager conversation about past projects first. Some sessions reportedly used a plain editor and a tight time limit, so practice without autocomplete.
Later technical rounds typically include more data structures and algorithms work, with dynamic programming, recursion, or partitioning problems reported. Interviewers may extend a problem with new requirements, so be ready to discuss edge cases and time and space complexity. A few candidates mention C++ or C-leaning questions, so language fluency may matter.
Some candidates report design interviews that were specific to Axon's products, such as image detection, license plate recognition, or integrating two Axon technologies. One reported a take-home design that had to be presented to two team members, and another described two design rounds. Not every candidate reports a design round.
Candidates commonly describe structured behavioral interviews with STAR-style follow-ups on ownership, collaboration, mistakes, ambiguity, and why Axon. Some report resume deep dives with managers or directors, and a few mention in-person or panel stages. Prepare several adaptable stories that you can tell concisely.
