Theory Card 096 — Abstraction Control / Breakdown
Research lens
Abstraction control is knowing when to stay high-level and when to zoom into mechanism. 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
Junior candidates often stay too concrete; senior candidates can also fail by staying too abstract. Structure and Implement help balance this by separating the skeleton from the deep dive. 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 Abstraction Control, 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 oscillating randomly between architecture, edge cases, syntax, and product requirements. 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 Abstraction Control changes the way you would handle the prompt.”