Real, anonymous reports from people who interviewed for Software Engineer at Arm, newest first and distilled into what to expect across the loop.
My process felt very technical from the start. After the recruiter stage, I ended up in a one-hour technical interview that mixed coding and systems-level questions with behavioral prompts layered in. A big theme was Python and software structure—object-oriented Python came up, and I had to work through coding questions while thinking out loud about the approach.
After a recruiter call, the next step was a more structured technical sequence. I had a first technical interview with two interviewers, and then I moved into another technical round that included a presentation and a programming test. The programming piece was framed like a standard data structures and algorithms coding challenge, and the overall difficulty felt moderate compared to the hardest parts I’d seen in other loops.
The interview process typically includes a series of technical interviews that assess coding skills, systems-level understanding, and problem-solving abilities, often starting with a recruiter call followed by multiple technical rounds. Candidates can expect a mix of coding challenges, system design discussions, and theoretical questions related to computer architecture and low-level systems.
Behavioral questions are integrated throughout the process, often focusing on candidates' past experiences, decision-making processes, and motivations for applying. This aspect emphasizes the importance of articulating one's background and how it relates to the role being applied for.
Candidates often experience delays in communication and feedback throughout the interview process, with some reporting long waits between interview stages and a lack of clarity regarding their status. This can lead to frustration and uncertainty about the outcome.
Candidates are expected to demonstrate strong coding skills under time pressure, often through LeetCode-style problems and live coding exercises. The interviews assess not just the final solution but also the reasoning and thought process behind the approach taken.
Interviews tend to probe deep technical knowledge, particularly in areas like computer architecture, low-level programming, and optimization techniques. Candidates should prepare for both theoretical questions and practical coding tasks that require a solid understanding of underlying concepts.
The overall difficulty of the interview process is perceived as high, with candidates noting that the questions often require a blend of theoretical knowledge and practical application. Some candidates felt the process was coherent and well-structured, while others found it challenging due to the depth of knowledge required.