Real, anonymous reports from people who interviewed for Software Engineer at Arm, newest first and distilled into what to expect across the loop.
My interview was a single technical-heavy session that lasted about an hour and mixed both coding and systems thinking. I spent time with Python-focused object-oriented questions and also had to do coding. What made it feel different was the breadth: they moved beyond software into hardware-adjacent territory.
After a recruiter call, the process moved quickly into a technical screen. I sat through a call with a hiring manager style interviewer, then had multiple technical interviews afterward, with one round that included a presentation plus a programming test. Across the technical sessions, the pattern stayed pretty consistent: discussion of my background and what I’d done before, followed by theory and coding that leaned into data structures and algorithm-style questions.
The interview process typically begins with a recruiter call, followed by a series of technical interviews that may include coding challenges, system design discussions, and behavioral assessments. The timeline can vary significantly, with some candidates experiencing long gaps between stages.
Candidates can expect a strong emphasis on both software and hardware concepts, including computer architecture, low-level programming, and data structures. Interviews often require deep understanding and the ability to explain design decisions and optimizations.
Coding assessments are common and can include LeetCode-style problems, live coding sessions, and take-home assignments. Candidates should prepare for a mix of algorithmic challenges and practical programming tasks in languages like C/C++ and Python.
Behavioral questions are integrated throughout the process, often focusing on past experiences and problem-solving approaches. Candidates should be ready to articulate their thought processes and how they align with the company's values.
The interview environment is generally described as structured yet friendly, with interviewers aiming to gauge candidates' depth of knowledge rather than just checking off questions. Candidates should expect a mix of technical rigor and open discussion.
Candidates often report a lack of timely feedback and clarity regarding outcomes, with some experiencing long waits for decisions or rejections without detailed explanations. It's important to manage expectations regarding communication throughout the process.