Started off with basic questions based on my previous work experience. Then it started getting technical - questions on computer architecture fundamentals like cache memory, TLB, memory management, etc.
Then there were a few questions related to semaphores and mutex. After that, there were questions related to embedded C - static, volatile, storage classes, and debugging faulty code, stuff like that. Overall, you need to understand the basics of embedded C to crack the interview.
Difference between binary semaphore and mutex?
What is cache coherency?
What is TLB?
What is the significance of volatile keyword?
The following metrics were computed from 1 interview experience for the Arm Intern Firmware Engineer role in Austin, Texas.
Arm's interview process for their Intern Firmware Engineer roles in Austin, Texas is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Arm's Intern Firmware Engineer interview process in Austin, Texas.