Theory Card 012 — Chunking / Assess
Research lens
Chunking lets people compress many low-level details into a smaller number of meaningful units they can reason about. In the Assess stage of BASIC, the goal is to evaluate candidate directions and constraints. 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, Assess is where the candidate should ask: What approaches are available, what trade-offs matter, and what complexity target is realistic? 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 compare plausible approaches before committing. For Chunking, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from turns guessing into reasoned choice.
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 Assess step and explain how Chunking changes the way you would handle the prompt.”