4 rounds of technical interview, hr round, hiring manager interview, ranging different areas in technical interview like c, perl, conp arch, sv and uvm etc., mostly moderate level of question difficulty
I applied online. The process took 1 week. I interviewed at Arm (Mountain View, CA) in Sep 2018
Interview
I was interviewed by the design lead of the company. He asked me a few behavioral questions and viewed one of my recent projects. He answered a few of my questions. This design lead is particularly respectful and bright to people. He has the patience to mentor young designers. Although I did not get the offer, the interview process was joyful, and I learnt a lot from his mentorship.
Interview questions [3]
Question 1
As a new grad just out of school, how do you want to design your career? Where do you see your start point is?
Top academic institutes with HCI degree teach students how to use specific methodologies to do research or design. However, they do not teach students how to design to solve a problem that really is the users’ needs. Do you think your institute teach you how to design? Why?
I applied online. The process took 2 months. I interviewed at Arm (Cambridge, East of England, England) in Jan 2018
Interview
Short HireVue interview with some simple questions about why you applied to the position etc., and one trivial programming task. Overall ~20 minutes long, although the coding question had a one hour time limit despite it only taking 5-10 minutes to complete.
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.
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'.
Interview questions [1]
Question 1
How would you compress program trace coming straight from a CPU (i.e. compress the trace of an assembly program)?