Stage 3 · Explaining tech
Design review
Present a design as context → problem → options → decision, then handle questions.
Situation
You present a caching design for checkout to the architecture board.
Sample dialogue
You · Solution Architect
Let me give you a high-level overview first.
You · Solution Architect
The context is that our checkout is getting slower every month.
You · Solution Architect
The problem is that every request hits the database directly.
You · Solution Architect
We looked at three options. In the end, we decided to add a Redis cache in front of the product catalog.
You · Solution Architect
Does that make sense so far?
Emma · Principal Engineer
Mostly. Have we considered what happens to prices when the cache is stale?
You · Solution Architect
Good question. Prices are never cached. We only cache product descriptions and images.
Emma · Principal Engineer
Great. And what's the rollback plan?
You · Solution Architect
It's behind a feature flag, so we can turn it off in seconds.
Key phrases
Let me give you a high-level overview first.
Start a presentation with the big picture.
The context is that our checkout is getting slower every month.
Set the background before the problem.
The problem is that every request hits the database directly.
State the core problem clearly.
In the end, we decided to go with Postgres because the team already knows it.
Explain the final decision and why.
Have we considered what happens if the service goes down?
Raise a risk as a question rather than a criticism.
Let me walk you through the request flow.
Offer to explain a process step by step.
How to practice
- Pick a system you work on. Write one sentence each for context / problem / options / decision.
- Present for 5 minutes, record it, then answer 3 tough questions (rollback, cost, scale).
- Shadow the opening until your intonation sounds natural.