16 · EVOLUTION
Grow a design through multiple stages of scale.
Start with a small clean system, evolve it through growth stages — new requirements, tech debt accumulation, scaling decisions. See how trade-offs compound.
Start evolving →STAGE 1 · LAUNCH
Tech Debt
10%
"Monolithic to start"
STAGE 2 · GROWTH
Tech Debt
30%
"Extracted payment & notifications"
STAGE 3 · SCALE
Tech Debt
55%
"Quick coupling shortcut — tech debt added"
STAGE 4 · CRISIS
Tech Debt
80%
"Scaling wall hit — refactor needed"
Your choices at each stage determine this.
What happens at each stage.
Initial design
A clean slate. Single service, well-scoped, minimal dependencies. The initial design is intentionally small — you will not be evaluated on this state, only on how you evolve from it.
Tech Debt at this stage
First evolution
A new requirement arrives the initial design was not built for. First trade-off: extract quickly with coupling, or invest in abstraction? The first decision shapes everything downstream.
Tech Debt at this stage
Complexity compounds
A scaling requirement forces structural change. Shortcuts from Stage 2 now constrain your options. Coupling starts showing up as orange lines. Tech debt is accumulating visibly.
Tech Debt at this stage
Final evaluation
The full history of decisions is analysed. Tech debt score, scalability ceiling, extensibility rating. Hindsight makes every shortcut obvious — the question is whether you saw it coming.
Tech Debt at this stage
How shortcuts compound.
A single rushed decision in Stage 2 doesn't just affect Stage 2. It constrains every stage that follows.
Tech Debt Score
Stage 1
Clean start
Stage 2
First shortcuts
Stage 3
Coupling added
Stage 4
Scaling wall
Evolution Stage
Note: A 10% shortcut in Stage 2 becomes a 30% refactoring effort in Stage 4. The compounding effect is not linear — delayed decisions grow exponentially harder to unwind.
Everything built for long-horizon thinking.
Multi-stage progression
Evolution scenarios have three to five stages, each introducing a meaningful constraint that builds on the previous design state — not a trivial extension.
Tech debt accumulation visible
A running tech debt indicator shows how each stage's shortcuts and rushed decisions compound into a harder-to-maintain system over time.
Trade-off decision points
At each stage you see the trade-off you are making — speed vs. cleanliness, coupling vs. flexibility. There is no pretending trade-offs do not exist.
Scale, tech debt, and trade-offs focus
Evolution specifically targets the concepts that come up in senior LLD follow-ups: how do you handle growth, and how do your early decisions age?
Post-evolution system analysis
A full analysis after all stages shows your final system's metrics — tech debt score, extensibility rating, and a comparison to the benchmark evolution path.
Long-term thinking training
Most LLD practice focuses on the initial design. Evolution trains the harder skill: designing for a system that will grow, change teams, and accumulate shortcuts over years.
Who should practice Evolution?
Senior engineers and SDE-2+ candidates
Who need to demonstrate that their designs hold up over time, not just at inception. Evolution is the mode that separates senior-ready candidates from the rest.
Engineers preparing for "how would you evolve this?" follow-ups
These questions appear in almost every senior LLD round. Evolution gives you structured reps at answering them with trade-off awareness, not just incremental feature additions.
Engineers who make clean initial designs but poor long-term decisions
If your Stage 1 designs are clean but your Stage 3 and Stage 4 become unmanageable — this is the exact gap Evolution is designed to close.
Technical leads and staff-level candidates
Preparing for rounds that assess long-term design thinking, cross-stage decision awareness, and the ability to reason about decisions with downstream consequences.
Start small. Watch your decisions compound.
The initial design is already on the canvas. Your job is to evolve it well enough that a future engineer can still work with it.
Start evolvingFAQ
Questions people ask
→ Explore more