Arm Embedded Interview Guide
- Roles
- Software Engineer, Firmware Engineer, Embedded Software Engineer, Graduate Engineer
- Hiring hubs
- Cambridge, Manchester, Bengaluru, Austin, Sophia Antipolis
- Focus
- C, compilers and optimisation, memory systems, synchronisation
Processes differ by team, level and country, so treat this as a typical picture, not a guarantee. Last updated: November 2026.
At a glance
| Typical process | Phone interview and/or skills test → one or more technical interviews → behavioural questions |
| Main focus | C and pointers, how compilers optimise code, caches and memory systems, synchronisation, system design for embedded |
| Coding style | Reading and reasoning about short C functions; some problems written on paper |
| Reported difficulty | Software Engineer candidates on Glassdoor rate it about 3 out of 5, with around 60% positive experiences |
How the process usually runs
Glassdoor's summary of Arm software interviews lists phone interviews, skills tests and one-to-one interviews as the most common stages. Graduate and intern candidates in Bengaluru and Austin describe basic C pointer questions and core OS and architecture concepts. More senior candidates report open discussions on memory subsystems and system design with performance trade-offs. The overall process can take several weeks.
Topics that come up most
- C and pointers → Pointers & Memory
- Compilers: which optimisations are and are not legal for a given function (aliasing,
volatile, side effects) → C Programming, Embedded C - Memory systems: cache coherency, TLBs → Operating System Concepts, Microcontrollers & ARM
- Synchronisation: binary semaphore vs mutex → RTOS
volatile→ Embedded C
Questions candidates reported (paraphrased)
- Given five or six short C functions, explain which compiler optimisations could and could not be applied.
- Binary semaphore vs mutex.
- What is cache coherency? What is a TLB?
- Why does
volatilematter? - Design an embedded software system and discuss the trade-offs.
Practice questions
These are the questions Arm candidates most often report, or close variants of them. Each links to a full answer or a coding problem with tests on this site.
- Which compiler optimisations can change how your C code behaves?
- What is strict aliasing?
- What is volatile and when must you use it?
- Does volatile make a variable thread-safe or atomic?
- What is the difference between a mutex and a binary semaphore?
- What are the cache coherency problems with DMA?
- How do Arm systems keep DMA and CPU caches coherent (ACP, I/O coherency)?
- What is a TLB, and how do you calculate the effective memory access time?
- What is RISC, how does it differ from CISC, and why did Arm succeed?
- What does the inline assembly __asm volatile("" ::: "memory") do?
- What is a function pointer and where is it used?
- Implement memmove (coding)
How to prepare
- Understand what the compiler may assume: strict aliasing, undefined behaviour,
restrict,volatileand side effects. - Revise caches, TLBs and memory ordering, ideally in the context of the Arm architecture (Cortex-A vs Cortex-M).
- Practise writing clean C under exam-like conditions; one candidate notes that thinking before writing on paper helped.
Share your experience on the forum and help the next candidate.
Sources: summarised from candidates' public interview reports on Glassdoor [1] [2] [3] [4] [5]