What embedded job interviews actually ask
The topics that come up in nearly every technical interview in this field, and what interviewers are really listening for.
An embedded interview almost never tests memorisation. It tests whether you understand what happens underneath the code — which is why the same questions keep coming back.
Memory management
The difference between stack and heap, what happens when memory runs out, and why calling malloc inside an interrupt is a problem. This is the most common question in the field and it filters fast.
Interrupts
What you may and may not do inside an ISR, what volatile actually means and why it does not solve timing problems, and how to move data out of an interrupt without losing it.
Communication
UART, SPI, I2C — not the definition, but how you debug them when they fail. A good interviewer asks "the line is silent, what do you check first".
RTOS
What priority inversion is, when you actually need an operating system, and the difference between a semaphore and a mutex. This separates people who read about it from people who used it.
What a good answer sounds like
Not "it just is", but "it is, because the hardware behaves this way, and here is how I would verify it". Interviewers are listening for a way of thinking, not a quotation.