I was a little weirded out by the fact they are offering a Tesla to new engineering hires, as well as the ridiculous space doors on their office. Seems gimmicky and combined with their terrible employee reviews here on Glassdoor I wasn't expecting a great process. Their mission and product sounded super cool though so I wanted to check it out. First I had a phone screen which surprised me by going very well. The recruiter was friendly and informative, and asked a whole range of questions about front end engineering, javascript, and even data structures and algorithms. I correctly answered all of the questions and felt really good about the process. The phone screen felt very comprehensive and thorough and I was confident I had accurately demonstrated my knowledge and skills (as much as possible over the phone). I was then brought in for an initial 90 minute interview with the team lead. This is where it went south fast. The team lead boasted about how their vision had been confusing and unclear a few months ago, but now he had a clear focused vision going forward. He then explained to me the three different possible outcomes of their project, all very different (huh, I thought the vision was clear now). He gave me contradictory answers to multiple questions I had also asked the recruiter, and additionally he did not seem to have a grasp on front end architecture and best practices. Once we were done with Q&A, we moved to the technical section. He told me he was going to question me on a range of subjects covering front end and even some backend and algorithms. I was excited to show off my range of skills, however he then asked me to solve a single algorithm problem. I solved it relatively quickly, and began looking for optimizations. He cut me off and said he wasn't interested in my optimization. He continued pressing me for some optimization that I was not seeing, and the "hints" he gave did not give any indication what he was actually wanting. We danced around the problem for the entire remainder of the interview with him never being able to make clear what he wanted until we were out of time. At one point he tried to write some code on the white board but got confused because he wasn't sure if javascript arrays had a length property. Needless to say I was not very impressed. He eventually told me he wanted me to write it recursively, but there was not enough time remaining for me to solve it. As a side note, the time complexity of the recursive solution was worse than the iterative solution so I'm not sure why he thought the recursive solution was better. Overall the second interview was a poor experience. I am a very talented engineer and their evaluation process was very blunt and clumsy. Coupled with their seeming confusion about their future vision and the consistently bad employee reviews, I decided I would not pursue the position further should they ask to advance me, however they did not so the feeling was mutual.

Was referred by a current employee and was able to skip the phone screen. Studied the Cracking the Coding Interview book a little bit beforehand since I heard several former Microsoft employees work at Axon and the questions could be similar to the Microsoft interview. On-site was divided up into interviews with several people: 1. Meeting with a recruiter and introduction 2. CSS/HTML and web page design interview. Also demo of some of their products 3. Coding Question - pretty difficult but my studying helped 4. JavaScript / Coding Question 5. Lunch interview at a nice spot near by 6. Design Interview with their Design Lead 7. Meeting with VP of engineering - talked in depth about my work experience and some pretty technical details of systems. Overall, the day was long but I felt pretty good about how everything went afterwards. Culture seemed very upbeat and passionate about increasing police transparency. Office is very modern, free snacks/drinks, standing desks, MacBook Pros. Very social vibe, not like a bunch of drones in an office. I think I got a little bit lucky with my coding questions, since I'd studied sections that helped me. Would probably be good to know how to use lots of basic computer science data structures/algorithms, Linked Lists, Hash Tables, Graphs, Binary Search, etc.