
Six parts, about two minutes
- The problem, and who had it. One sentence a non-engineer would follow.
- The constraints. Scale, deadline, the thing you could not change.
- What was built. Three boxes and how they talk. No more.
- Your part. What you personally designed, wrote or decided.
- The hard decision. One trade-off, with what you gave up.
- The result. What changed, with a number if you have one, and what you would do differently.
Three boxes
Whatever the real architecture was, describe it as three parts at first. An interviewer can hold three boxes in their head and ask about any of them. Twelve boxes, and they stop listening and wait for you to finish.
Say I
"We migrated the order pipeline" tells the interviewer nothing about you. "I wrote the consumer and designed how we would run both systems side by side during the move" does. Give the team credit once, then talk about your own work.
The hard decision is the interview
Almost every follow-up question will be about the trade-off, so choose it before the interview. Pick a decision where a reasonable person could have gone the other way, and be ready to argue the other side as well.
Prepare two versions
- Two minutes, for the opening.
- Ten minutes, with the data model, the failure cases and the numbers, for when they say tell me more.
Common mistakes
- Starting with the technology list.
- Spending a minute on company background.
- Describing a project where you cannot say what you did.
- Having no number at all. Even a rough one is better than none.