Theory Card 103 — Transfer Across Domains / Structure
Research lens
Transfer means using a learned principle in a new context rather than only in the exact form it was originally practiced. 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
This is the difference between memorizing one tree solution and applying the same reasoning to graphs, recursion, or system pipelines. A stage-based framework travels well because the same sequence can guide coding, design, debugging, and project explanation. 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 Transfer Across Domains, 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 learning isolated answers instead of a reusable method for building answers. 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 Transfer Across Domains changes the way you would handle the prompt.”