Difficulty
Average
Candidate-reported interview insights
Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences at Arm.
Difficulty
Average
Average rounds
2.4
The communication for the interview was a bit chaotic. I gave my availability but didn't hear back, so I had to send a reminder. Then they told me they couldn't meet during that time because they were traveling. Eventually, the interviews were scheduled with different people, but after just the first interview with a peer (not the hiring manager), they canceled all the subsequent interviews without any further explanation. This is despite the interviewer seeming very positive about next steps during our chat. The whole hiring experience felt inefficient and not as open and clear as they advertised.
It was a phone interview lasting a bit less than an hour with two engineers. They were quite friendly. They started by giving a brief overview of the role, then asked me to talk about myself. Following that, they inquired about my CV and then posed some technical questions. The conversation flowed, with them asking follow-up questions based on my responses or introducing new subjects. Time was allocated at the end for my questions.
The interview process was pretty smooth and fast. The recruiter set up the interview quickly, and it didn't feel like an interrogation. I found out I wasn't selected for the job via email less than a week later.
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 Arm.