Embedded Systems interview questions
Microcontrollers, peripherals, and the hardware-software boundary.
Interviewers rarely ask you to define anything here. They describe a symptom, a measurement, or a constraint and watch how you reason. The 6 concepts below are what a strong answer draws on, and they are exactly what this product weights up when a job posting mentions embedded, microcontroller, mcu.
What interviewers probe
- MCU Architecture & Peripherals
- Cores, buses, memory maps, and how a peripheral is actually configured.
- Interrupts & ISR DesignCore
- Latency, priority, nesting, and what belongs inside an ISR.
- DMA
- Offloading transfers, buffer ownership, and coherency pitfalls.
- RTOS & Scheduling
- Tasks, priorities, priority inversion, and when an RTOS earns its cost.
- Memory & Stack Constraints
- Stack sizing, heap avoidance, and diagnosing overflow on a small part.
- Low Power Modes
- Sleep states, wake sources, and measuring real current draw.
An example question
32-bit ARM Cortex-M part; the sensor value is a 64-bit timestamped struct.
A flight controller occasionally reports a sensor value that is physically impossible — a mix of an old and a new reading. The sensor is read in an ISR and consumed in the main loop. What is going on, and how do you fix it without disabling interrupts for long?
What a strong answer covers
It is a torn read. The struct is larger than a single word, so the ISR can fire partway through the main loop's read and update part of it, leaving the consumer with fields from two different samples. Marking it volatile does not help — volatile controls compiler reordering and caching, not atomicity. The heavy fix is a short critical section around the read, but the better ones avoid blocking: double-buffer with a single atomic index that the ISR flips after a complete write, so the consumer always reads a whole sample; or use a sequence counter the writer increments before and after, and have the reader retry if it changes or is odd; or push complete samples into a single-producer single-consumer ring buffer. All three keep the interrupt latency bounded, which matters on a controller.
- Identifies the torn read — A multi-word update interrupted partway, not a sensor fault.
- Rejects volatile as the fix — Knows volatile addresses reordering, not atomicity.
- Proposes a non-blocking mechanism — Double buffer, sequence counter, or SPSC ring buffer.
- Considers interrupt latency — Explains why a long critical section is the wrong answer on a controller.
How this topic gets weighted
A posting that mentions embedded, microcontroller, mcu pushes embedded systems up the curriculum, and the weighting is shown with the quote from the posting that caused it. Two candidates preparing for different roles get genuinely different plans from the same taxonomy — and because mastery is stored per concept rather than per application, what you learn here still counts on your next one.
Related topics
Practice embedded systems against a real posting
Paste the job description you are actually interviewing for. The curriculum weights this topic against everything else the role needs, and the scheduler serves the questions that close your gaps fastest.