Theory Card 043 — Constraint Discovery / Structure
Research lens
Constraint discovery is the habit of finding the limits that shape the solution space: input size, ordering, durability, latency, or correctness rules. In the Structure stage of BASIC, the goal is to externalize a plan, invariant, or architecture. 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 often hide the real difficulty inside a constraint rather than in the visible wording of the question. BASIC creates a dedicated moment for finding those limits before you lock in a solution. In practice, Structure is where the candidate should ask: What is the sequence, helper structure, invariant, or component map that will carry the solution? 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 make the plan visible before full execution. For Constraint Discovery, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from reduces hidden-state thinking and makes reasoning inspectable.
Common miss
The miss is solving a simpler version of the problem than the interviewer actually asked. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Structure step and explain how Constraint Discovery changes the way you would handle the prompt.”