Watch the 40-second version: https://www.youtube.com/shorts/v0NKUo-p5Dc

The First 60 Seconds Decide Your System Design Interview. Here Is the Script.

Most candidates hear "design a photo app" and reach for the marker. That is how you lose in the first sixty seconds, before a single box is drawn. Not because your boxes were wrong. Because you never showed anyone how you think.

Here is the part nobody tells you: the interviewer is not grading your diagram. They are grading what you do with ambiguity. In real work, nobody hands you a clean requirements doc either. They hand you a noun in a meeting and expect an architecture by Friday. The clarification round is a live demo of how you handle that. Treat it like filler and you have told them everything.

The classic mistake is asking "web or mobile?" and thinking you clarified. That is trivia, not thinking. What actually works is a thirty-second script, three moves:

First, turn the noun into a journey. "Design a photo app" is a noun. "A user captures a photo, uploads it, shares it with followers who comment" is a journey. Journeys have edges. Edges are where requirements hide.

Second, draw the boundary out loud. "In scope: upload pipeline, storage, feed. Out of scope: auth, payments." Half of all failing interviews die here, in the mushy middle where the candidate designs half of three systems instead of one system well.

Third, name the one hard part. "The interesting bit is reliable uploads on flaky mobile networks." This is the move that separates seniors from everyone else. Juniors describe. Seniors diagnose.

And here is the non-obvious angle. Every clarifying question you ask is a negotiation over where you get scored. Ask about scale, you will be graded on architecture. Ask about edge cases, you will be graded on rigor. Ask about the product journey, you will be graded on product sense. So clarify deliberately, toward the strengths you actually want judged. You are not buying time. You are choosing the battlefield.

The 30-second script, copy-paste edition

1. Journey it: "So a user captures a photo, uploads it, shares it with followers who comment. Right?"
2. Bound it: "In scope: upload, storage, feed. Out of scope: auth, payments, moderation."
3. Diagnose it: "The hard part looks like reliable uploads on bad mobile connections."
4. Anchor it: "Roughly how many daily uploads are we designing for?"

Four sentences. Thirty seconds. No boxes. And the interviewer has already decided you are one of the ones who thinks.

This is question 1 of 60 in my Frontend System Design Interview Playbook, the full set of questions, scripts, and traps, with the answers I wish someone had handed me: https://bittalk.gumroad.com/l/frontend-interview-playbook