Theory Card 080 — Error Detection / Check
Research lens
Error detection relies on having reference points that make mismatches visible. In the Check stage of BASIC, the goal is to verify correctness, quality, and risk. That makes this concept especially relevant here, because it shapes how much mental work the candidate is trying to carry at once and what gets made explicit.
Why it matters in SWE interviews
In coding rounds this means edge cases and invariants; in design rounds it means bottlenecks, outages, and abuse cases. Structure and Check create those reference points by naming what should happen before execution is complete. In practice, Check is where the candidate should ask: Does the answer actually satisfy the prompt, handle edge cases, and survive scrutiny? That question acts like a cognitive boundary. It protects the answer from turning into an unstructured search.
BASIC move
A strong move here is to review and stress-test before you hand the answer over. For Error Detection, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from creates a verification loop instead of assuming success.
Common miss
The miss is discovering mistakes only after the interviewer asks a pointed follow-up. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Check step and explain how Error Detection changes the way you would handle the prompt.”