Tell me about a time a small detail, like a datasheet footnote or a timing value, turned out to matter a lot.

What the interviewer is looking for

• This question tests attention to detail. Gives examples of catching small but critical details in datasheets, timing or edge cases before they caused failures.
• What to bring out: A specific detail, how it was caught or missed, the impact, and habits they use now such as checklists, errata reviews and peer review.
• Expect a follow-up like: What habit do you use to catch those details consistently?

Another way it may be asked: Think of a time one overlooked number or note caused, or nearly caused, a real problem. 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 attention to detail 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

• 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?
• Tell me about a time you ran into a race condition or a priority problem in firmware. How did you find and fix it?

Browse all questions