Theory Card 013 — Chunking / Structure
Research lens
Chunking lets people compress many low-level details into a smaller number of meaningful units they can reason about. 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
Experienced engineers do not see ten separate facts in a prompt; they see a pattern family, a data shape, and a likely invariant. BASIC encourages chunking because Breakdown and Structure force the candidate to label parts before manipulating them. 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 Chunking, 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
Without chunking, candidates react to every detail individually and lose the global picture of the problem. 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 Chunking changes the way you would handle the prompt.”