Basic Framework
Breakdowncomparisonresearch-cardBASIC vs STAR

Comparison Card 171 — Architecture Review / Breakdown

Architecture Review — BASIC step map

Situation

An architecture-review interview asks whether you can critique and improve a proposed system. In this setting, the active interview task is happening now, not in the past.

What you make visible is what gets credit.

Why BASIC fits better here

During Breakdown, BASIC asks the candidate to decompose the prompt into named parts. BASIC helps because reviewing still requires decomposition, assessment, proposed structure, and validation. That matches the live technical work of the round, because the interviewer is evaluating present-tense reasoning, not only narrative polish.

What goes wrong with a STAR-shaped response

STAR describes what happened in the past; architecture review is an active evaluation of a present artifact. If a candidate leans too hard on a story-shaped answer in this moment, they may sound organized while still leaving the technical core underdeveloped.

What the interviewer is really seeing

The signal is thoughtful critique, prioritization, and improvement with trade-offs. The BASIC move at this stage is to split the problem before trying to solve it. That gives the interviewer concrete evidence that the candidate can think, choose, build, and verify under pressure.

Practical script

“In this architecture review situation, I’m using the Breakdown step to split the problem before trying to solve it. The main question I need to answer is: What exactly is the problem asking, what are the constraints, and what is the shape of the input and output?”

Why this matters
Breakdown isn't just problem comprehension. It's scope control. Every minute you spend here reduces the chance of building the wrong thing for ten minutes. In system design, it's even more critical — the requirements you miss at Breakdown haunt you at Check.

References

S6 S7 S9 S10 S15

Related in BASIC vs STAR

January 9, 2023

Why BASIC is better than STAR for SWE interview use cases

Let’s start with the honest version:

September 8, 2023

Comparison Card 106 — Coding Easy / Breakdown

A short coding prompt with a relatively direct solution still requires clarity, not just speed. In this setting, the active interview task is happening now, not in the past.

September 10, 2023

Comparison Card 107 — Coding Easy / Assess

A short coding prompt with a relatively direct solution still requires clarity, not just speed. In this setting, the active interview task is happening now, not in the past.