Me postulé en línea. Acudí a una entrevista en Arm (Cambridge, East of England, England) en dic 2020
Entrevista
I applied for the job online, First HR interview was held. Then after 2+ week, Technical interview. It last around 2 hours. During the interview, I tried to answer all questions and I think I believe that I answer most of them. Even though, for the architectural related or low level questions, I tried to answer in more detail without being asked(draw, diagrams, etc.) Generally, interview was good, but questions were varity (os, architecture, low level programming, peripherals etc.) As a Junior, I tried to explain all the questions(even though some of them in more detail). Interviewers were kind. After 3 days later, I had a telephone call that I've been told that I was rejected. In the end, ARM should've taken into account my eagerness for learning new things(I believe this is quite important) as much as the other stuffs.
Preguntas de entrevista [1]
Pregunta 1
Cache, Virtual Memory, OS related questions, Memory Management, Arm Architecture, Data structures, bitwise operations, interrupts, peripherals.
Me postulé en línea. El proceso tomó 4 meses. Acudí a una entrevista en Arm en ene 2023
Entrevista
This is rather a review of a complete experience (company, recruiting process, etc.) rather than the interview itself. 1. The job application portal is almost unusable (ICIMS): - No proper application tracking - No job description (this gets exceptionally problematic when you have multiple job applications titled the same way, think "Software Engineer") - No Job ID search - horrible combination with the previous point 2. The recruiting team added a random person - outside of the Arm company - to the technical interview, mistaking them for an Arm employee with similar name/surname. Formally, this is a data transfer to an unauthorized 3rdparty. The situation got resolved when I explicitly noticed (in an email) that the wrong person had been added. 3. Almost impossible to reach the recruiting team: either the email system is broken or the recruiting team is understaffed so much that they could not reply to emails. Ever. 4. The job description did not state much and it turned out that the position I applied for is completely outside of my domain of expertise: fairly different tech stack, fairly different R&D topics. 5. After two technical interview rounds, nothing happened for a month (I think literally a month). At this point any reasonable person would consider the interviews failed and get on with life. Turned out - after another phone call from a recruiter, and after an extra week of silence - I have passed the technical interviews and the company was ready to give me an offer. 6. When speaking with the hiring manager, which is an optional, candidate-requested call (my understanding) - that *only* happened because I wasn't sure about multiple things (see 4) - turned out that the technological stack was actually relevant and the R&D topics were interesting. Without this part of the interview process, my picture of the job was *utterly* different.
Preguntas de entrevista [1]
Pregunta 1
Generally a "C developer" interview for a "C++ developer" position: - questions around key concepts of programming, computer memory, systems programming - interesting, concise during-the-interview programming assignments
I’m really sorry to hear you had a negative interview experience with us. We speak with thousands of people a year and the vast majority have a good experience interviewing with Arm. Please contact me on glassdoorfeedback@arm.com so we can talk about your experience and learn from what happened.
