Theory Card 009 — Cognitive Load / Implement
Research lens
Cognitive load theory argues that solving unfamiliar problems can consume the same limited mental resources needed to learn and reason clearly. In the Implement stage of BASIC, the goal is to execute the chosen plan in controlled order. 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 interviews, this shows up when a candidate knows the topic but melts down as soon as the prompt becomes multi-step or ambiguous. BASIC helps by giving the brain a fixed order of operations instead of asking it to invent the process from scratch every time. In practice, Implement is where the candidate should ask: How do we write or walk through the solution one stable layer at a time? 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 transcribe the plan instead of improvising. For Cognitive Load, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from keeps execution disciplined and easier to debug.
Common miss
The common miss is trying to optimize and code at the same time, which overloads memory and causes avoidable confusion. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Implement step and explain how Cognitive Load changes the way you would handle the prompt.”