Tell me about a time you ran into a race condition or a priority problem in firmware. How did you find and fix it?

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.
• What to bring out: A concrete story, how they gathered evidence through tracing or toggling pins, the root cause, and a correct fix such as critical sections, mutexes with priority inheritance or redesign.
• Expect a follow-up like: How did you prove it was really fixed and not just hidden?

Another way it may be asked: Think of a bug that only appeared sometimes because two things ran at the wrong moment. What happened?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the real-time systems you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

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

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• How do you decide what goes inside an interrupt handler and what gets deferred to a task or the main loop?
• 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