How do you decide what goes inside an interrupt handler and what gets deferred to a task or the main loop?

What the interviewer is looking for

• This question tests real-time systems. Understands interrupts, scheduling, priorities and timing deadlines, and reasons about race conditions and priority inversion.
• Strong answers: Keeping handlers short, capturing data and signalling, deferring heavy or blocking work, protecting shared data, and keeping latency predictable.
• Likely follow-up: How do you safely pass data from the interrupt to the task?

Another way it may be asked: A button press triggers an interrupt that should update a screen and send a message. What should the interrupt itself do?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• Tell me about a time you ran into a race condition or a priority problem in firmware. How did you find and fix it?
• When would you choose a real-time operating system over a simple bare-metal loop, and what does that choice cost you?
• What does the volatile keyword do in C, and when would you need it in firmware?
• Can you explain the difference between I squared C, SPI and UART, and when you might pick each one?
• Your board powers on but the sensor never responds. What steps would you take to figure out what's wrong?

Browse all questions