Basic Framework
StructureExpert Decompositiontheoryresearch-cardWhy BASIC Works

Theory Card 033 — Expert Decomposition / Structure

Expert Decomposition — BASIC step map

Research lens

Experts tend to organize problems around deeper structures and subproblems, while novices often focus on surface details. 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.

Patterns are shortcuts, not substitutes for reasoning.

Why it matters in SWE interviews

That gap is visible in interviews when one candidate sees 'tree recursion with a base case' and another only sees a confusing story problem. Breakdown and Structure train the habit of expert-like decomposition even before full expertise is developed. 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 Expert Decomposition, 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 latching onto a keyword or memorized trick without identifying the real subproblem boundaries. 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 Expert Decomposition changes the way you would handle the prompt.”

Engineering insight
Structure is where you convert thinking into a plan someone else could follow. In coding interviews, that means the algorithm's skeleton — the invariant, the loop structure, the recursive contract. In system design, it's the component diagram with clear data flow. The test: could a teammate build from your description alone?

References

S5 S10 S12

Related in Why BASIC Works

January 7, 2023

Why BASIC works for software engineers

BASIC — Breakdown, Assess, Structure, Implement, Check — works for software engineers because it is not just a catchy mnemonic. It is a compact operating system for thinking under…

January 19, 2023

Theory Card 006 — Cognitive Load / Breakdown

Cognitive load theory argues that solving unfamiliar problems can consume the same limited mental resources needed to learn and reason clearly. In the Breakdown stage of BASIC,…

January 21, 2023

Theory Card 007 — Cognitive Load / Assess

Cognitive load theory argues that solving unfamiliar problems can consume the same limited mental resources needed to learn and reason clearly. In the Assess stage of BASIC, the…