Difficulty
Average
Candidate-reported interview insights
Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences at AXS.
Difficulty
Average
Average rounds
3.1
The first interview was a conversation with a manager and it went well. The second interview was presented as another chat with an additional manager, but it turned out to be a coding interview. I was surprised, but honestly, I probably should have expected it. I didn't do great because I was nervous and anxious. I really think I would have been a good fit for the role, as it's a perfect match for my skills, but I couldn't perform at my best. I'm disappointed in myself but thankful for the chance.
The communication was really clear. They moved fast and made decisions quickly. The interview was conversational, with a nice balance between technical aspects and personal style and approach. I bombed because I was nervous, but they told me within a day or two they weren’t moving forward, which I appreciated.
First, I had a call with the engineering manager. Then, I had a technical interview with the engineering lead; it wasn't like LeetCode questions. Finally, I did an on-site interview with the team.
A focused selection of the most detailed candidate-submitted questions.
Practice technical, system design, and behavioral questions with Zitlee.
Interview information is based on candidate reports and may not represent the current official hiring process of AXS.