Theory Card 071 — Verification Discipline / Breakdown
Research lens
Verification discipline is the habit of testing, checking edge cases, and reviewing whether a solution matches the original requirement. In the Breakdown stage of BASIC, the goal is to decompose the prompt into named parts. 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
Interviewers notice immediately when a candidate hands over code or architecture without validating it. The Check stage makes verification an explicit deliverable rather than an optional flourish. In practice, Breakdown is where the candidate should ask: What exactly is the problem asking, what are the constraints, and what is the shape of the input and output? 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 split the problem before trying to solve it. For Verification Discipline, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from prevents premature solutioning and keeps working memory from being flooded too early.
Common miss
The miss is ending the answer as soon as a plausible solution appears. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Breakdown step and explain how Verification Discipline changes the way you would handle the prompt.”