Describe your most memorable bug and fix

A strong answer is structured (STAR/Led-Task-Action-Result) and shows technical depth plus learning. ## Suggested structure (what interviewers look for) 1) **Context**: 2–3 sentences. What project (CPU, verification, OS, etc.), scale, and why it mattered. 2) **Symptoms & impact**: What failed (wrong output, rare hang, perf regression), how often, severity. 3) **Debug approach**: - Reproduction strategy (minimize test, seed control, bisection, reduce nondeterminism). - Observability (logs, waveform, assertions, perf counters, tracing, printf vs formal). - Hypothesis-driven iteration (what you suspected and how you ruled it out). 4) **Root cause**: A crisp technical explanation (race condition, wrong assumption about ordering, off-by-one in index bits, missing flush on mispredict, CDC issue, etc.). 5) **Fix**: The change and why it’s correct (include any invariants). 6) **Validation**: - Regression tests added (directed + randomized). - Assertions/coverage improvements. - If applicable: formal/property checks. 7) **Prevention**: Process or design improvements (code review checklist, lint rules, better spec, added monitors). ## Example outline (adapt to your experience) - **Context**: “In an OoO core project, I was responsible for verifying the load/store queue + store buffer.” - **Bug**: “A random test occasionally read stale data after a store; failure rate ~1/5,000 seeds.” - **Debug**: - Reduced to a minimal sequence of store-load with a branch mispredict. - Added assertion: “a younger load must not bypass an older store to the same address unless forwarding occurs.” - Inspected waveforms/transaction logs around mispredict recovery. - **Root cause**: “On branch mispredict flush, one LSQ entry’s valid bit was cleared but its address compare metadata wasn’t, so a later load incorrectly believed there was no older matching store.” - **Fix**: “Made flush reset both valid and compare metadata atomically; added a one-hot/consistency assertion for LSQ entry state.” - **Validation**: “Added directed test for mispredict+store-load aliasing; ran full regression; coverage improved on that corner.” - **Prevention**: “Introduced an LSQ state machine diagram in the spec and a checklist item for flush/reset completeness.” ## Common pitfalls to avoid - Blaming others or being vague (“it just didn’t work”). - No clear root cause. - No evidence of validation/prevention. - Choosing a trivial bug with no learning signal. If you share your project domain (DV, OS, compiler, etc.), you can tailor the story to highlight the most relevant skills.