Axon Interview Questions — Page 3

Axon·Software Engineer·Technical Phone Screen

Jun 2026

Axon software engineer interview with a data structure design problem. The question was clean and well-scoped, though the O(1) constraint on getRandom is the part that trips people up if they haven't seen it before.

Design a data structure that supports insert, remove, and getRandom operations, all in average O(1) time. Each element in the set must have equal probability of being returned by getRandom.

“The insert and remove parts feel straightforward until you hit getRandom.”

View Post

Axon·Software Engineer·Technical Phone Screen

Jun 2026

Axon software engineer interview with a graph traversal problem involving a heterogeneous entity model. Pretty standard algorithmically but the multi-type node setup added enough wrinkle to keep you on your toes.

You have three entity types: groups (which can nest other groups and users), users (who belong to groups and own devices), and devices (which belong to users). Given a starting entity, either a group or a user, return all reachable devices by traversing the membership graph. How do you handle cycles and visited tracking across the different node types?

“The cycle handling part is what they actually cared about.”

View Post

Axon·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Axon for a software engineer role. The whole thing was one big deep-dive into building an image translation service, and they made it clear upfront that vague answers would get pushed on. Felt like a gauntlet.

Design an end-to-end service that extracts text from user-uploaded images using OCR, detects the source language, translates it into multiple target languages, and renders the translated text back onto the image. Walk through the full pipeline.
How would you secure communication between the frontend and backend in this system? Compare approaches like signed requests, HMAC, OAuth, and mTLS, and explain which you'd use and why.
Define the database schema for this service. Specifically describe the users, jobs, images, translations, and languages tables: what columns each has and how they interact with each other in the pipeline.
What storage and CDN strategy would you use for both the original uploaded images and the translated output images?

“I started with the happy path: upload triggers OCR, OCR result goes to language detection, then fanned out to translation workers per target language, then a rendering step that overlays text back on the image.”

View Post

Axon·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Axon for a software engineer role. The problem was basically a fulfillment center dispatch system, think Uber for trucks and containers inside a warehouse. Pretty meaty scope for a single session.

Design a fulfillment center system that handles truck routing, assigns trucks to pickup and dropoff jobs across docks and yards, tracks containers and their inventory, and manages route updates with ETA handling.
How would you handle throughput and latency requirements for the dispatch service, and how do you ensure inventory state stays consistent across the system?
Walk through how you'd approach surge handling and real-time replanning when truck assignments need to change mid-route.
How would you use geo-indexing to support efficient truck dispatch and location lookups in this system?

“I started with functional requirements which felt right, but I underestimated how much the inventory tracking piece would complicate the data model.”

View Post

Axon·Software Engineer·Hiring Manager Screen

Jun 2026

Interviewed for a software engineer role at Axon. The questions were mostly career and motivation focused, felt more like a hiring manager conversation than anything technical.

What drew you to Axon specifically?
Walk me through your career path and what has shaped the direction you've taken.
Where do you see yourself in the next five years?

“I had a decent answer prepared around the mission but stumbled a bit trying to make it sound genuine rather than rehearsed.”

View Post

Axon·Software Engineer·Technical Phone Screen

Jun 2026

Axon software engineer interview with a geometry-flavored coding problem. Not the typical graph or DP question I was expecting, which threw me off a bit at first.

Given a sequence of 2D GPS coordinates representing a recorded path, compress it by removing redundant collinear points. Keep only the endpoints and any points where the direction actually changes, and use integer cross products for the collinearity check to sidestep floating-point issues.

“My first instinct was to just compute slopes between consecutive points and compare them, which is the obvious wrong answer the moment you think about vertical lines or precision loss.”

View Post

Axon·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Axon for a software engineer role. The prompt was deliberately open-ended, which sounds fun until you're actually in it trying to figure out where to even start.

Design a test orchestration service for an engineering organization that supports test definition, scheduling, execution on compute workers, and result tracking.
How would you handle failures, retries, and concurrency limits in the execution layer of this system?
What APIs and data models would you expose for this service?
How would you store and query execution logs, artifacts, and test results at scale?

“This thing sprawls in every direction the second you start talking.”

View Post

Axon·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026

Behavioral question from an Axon software engineer interview. Just the one question shared, but it's the kind that can go sideways fast if you're not ready to actually own a real mistake.

Tell me about a significant technical mistake you made on a past project. What was the impact, how did you handle it, and what did you take away from it?

“The part that trips people up is they try to pick a mistake that sounds small enough to be safe.”

View Post

Axon·Software Engineer·Onsite - System Design / Architecture

Jul 2026

System design round at Axon for a software engineer role. The prompt was dense, basically a full distributed systems problem around uploading body camera footage with legal chain-of-custody requirements. A lot to cover in one session.

Design a backend service for uploading large video files from body cameras or dashcams, where files may be several GBs, networks are unreliable, and uploads need to be resumable with chunk-level tracking.
How would you design the storage layout to isolate newly uploaded footage from content that has passed security checks, and what does the promotion pipeline look like?
How do you prove that a piece of footage has not been tampered with after upload, and what integrity verification approach would you use across the full lifecycle?
Design a tamper-evident, auditable chain of custody log that records every action taken on a piece of footage, from upload through access, legal holds, and eventual deletion.
What access control model would you apply to this system, and what security considerations are specific to footage that may be used as legal evidence?

“The size and reliability constraints were the easy part to talk through.”

View Post

Axon·Software Engineer·Technical Phone Screen

Jul 2026

Axon software engineer interview with a graph traversal problem involving nested group membership and device access. The core challenge was handling cycles in the group graph while keeping the solution efficient. Pretty straightforward if you've done BFS/DFS before, but the cycle constraint is where people probably trip up.

Given a nested group access model where groups can contain users and other groups (including cycles), and users own devices, find all unique device IDs accessible from a given set of starting groups by recursively expanding group membership.

“My first instinct was DFS and I just went with it.”

View Post