How do you test firmware when the hardware isn't ready yet or is in short supply?

What the interviewer is looking for

• This question tests firmware testing & reliability. Tests on host and on target, uses hardware in the loop, watchdogs and safe update mechanisms.
• Strong answers: Hardware abstraction layers, unit tests on the host, simulators or emulators, development kits, and planning hardware in the loop tests later.
• Likely follow-up: What kinds of bugs will still only show up on the real board?

Another way it may be asked: The new boards arrive in two months, but you need to start writing and testing code now. How do you do it?

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

• How would you design a firmware update process for devices in the field so a failed update never bricks them?
• 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?
• How do you decide what goes inside an interrupt handler and what gets deferred to a task or the main loop?

Browse all questions