It was a short HireVue interview with some simple questions about why you applied to the position etc., and one trivial programming task. It was overall ~20 minutes long, although the coding question had a one hour time limit despite it only taking 5-10 minutes to complete.
The in person interview was two hours long with three senior engineers. The dress code was business wear, but the interviewers were much more casually dressed and made the interview very relaxed - it was clear they got along well and often joked with each other during the interview.
The questions started with asking about a personal programming project I'd done, followed by questions that started simple but in hindsight were designed to lead me in a specific direction - when I failed to get a hint, they either made it clearer what they wanted or moved on to something else. There were no coding questions - all the questions were to evaluate basic architecture concepts and try to reason about or build on anything either I or the interviewers mentioned. If you mention something specific, chances are they know it better than you do and you may end up 'going down the rabbit hole'.
How would you compress program trace coming straight from a CPU (i.e. compress the trace of an assembly program)?
The following metrics were computed from 1 interview experience for the Arm Systems Architect role in Cambridge, United Kingdom.
Arm's interview process for their Systems Architect roles in Cambridge, United Kingdom is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Arm's Systems Architect interview process in Cambridge, United Kingdom.