Free lesson · Mobile System Design Interviews

The 5-Step Framework - Your Interview Playbook

Easy6 min readmobilemobile-system-designinterview-prep

Why You Need a Framework

Here's something most people don't realize: your brain doesn't think clearly under pressure. You're nervous, the clock is ticking, and the interviewer is waiting. That's when it's easy to ramble, skip important details, or second-guess yourself.

A framework is your safety net. It's a repeatable process that keeps you on track, shows the interviewer you're organized, and prevents you from spiraling.

Think of it like cooking. If you follow a recipe - prep ingredients, heat the pan, cook, plate - you'll make good food every time. Without a recipe, you're improvising, and things go wrong.

The 5-Step Framework Overview

Here's your playbook. We'll dive deep into each step in the next sections, but here's the high-level roadmap:

The House-Building Analogy

Imagine you're building a house. Here's how the framework maps:

• Step 1 (Detective): You meet the client. They say "I want a nice house." You ask: How many bedrooms? What's your budget? Do you need a home office? What's the neighborhood like? What's most important to you?

• Step 2 (Contract): You summarize: "So you want a 4-bedroom, 2-bath house for $500k in the suburbs, with a focus on natural light and a large kitchen. Does that sound right?"

• Step 3 (Blueprint): You draw the floorplan. Here's the living room, kitchen, bedrooms, where the foundation goes, electrical layout - high-level structure.

• Step 4 (Build): The client says, "I'm worried about the kitchen design." You zoom in and detail out the exact layout, appliance placement, counter space, storage.

• Step 5 (Walkthrough): You walk the client through their day: "In the morning, you wake up, walk to the kitchen, grab coffee, sit in the sunroom overlooking the garden..." Does it feel right?

Suggested Time Allocation

You've got 45-60 minutes. Here's how to split it:

Step 1 (Detective)     →   5-8 minutes   (Be efficient, but thorough)
Step 2 (Contract)      →   3-5 minutes   (Quick alignment)
Step 3 (Blueprint)     →   12-15 minutes (Most important visual output)
Step 4 (Deep Dive)     →   15-20 minutes (Interviewer leads here)
Step 5 (Walkthrough)   →   5-10 minutes  (Ties it all together)
Slack/Q&A             →   5 minutes      (Buffer for overruns)

💡 Tip: Watch the clock. If you're halfway through and still in Step 1, gently move forward. Interviewers notice when you keep asking questions indefinitely.

Why a Framework Matters

It Shows Structure

An interviewer watching you bounce between ideas thinks: "Is this person organized? Can I trust them to own a project?" A framework shows you think systematically.

It Prevents Rambling

Without a structure, you might spend 10 minutes on database indexing, then suddenly jump to UI design, then back to authentication. That's confusing. A framework keeps you focused.

It's Repeatable

You practice the framework on one problem (e.g., Instagram), then use the exact same approach on a different problem (e.g., Uber). No thinking required - just execute the playbook.

It Buys You Thinking Time

By following the framework, you're not inventing new ideas every second. You're following a tested process. That frees up mental energy to think deeply about the actual design.

Bad Interview vs. Good Interview

What a Bad Interview Looks Like

Candidate: "So we need a photo app. I'll use a database, and we'll cache stuff, and uh... we'll need servers for the backend. Oh, and authentication. Let me draw this..." spends 5 minutes drawing a messy diagram with arrows everywhere

Interviewer: "How many users are we expecting?"

Candidate: "Uh... millions? Or maybe thousands? I don't know, a lot. Anyway, let me tell you about the database schema..." starts listing columns randomly

Interviewer: (thinking) "This person doesn't have a plan. They're making it up as they go."

What a Good Interview Looks Like

Candidate: "Before I design anything, I'd like to understand the requirements better. Can I ask some questions?"

Interviewer: "Sure."

Candidate: "Thanks. First, functional requirements - what core features are we building? Second, scale - how many users, DAU, storage? Third, platforms - iOS only, Android, or both? Fourth, constraints - any specific tech stack requirements or latency targets?"

Interviewer: answers

Candidate: "Got it. So we're building Instagram-like photo sharing, 100M users, 10M DAU, both iOS and Android, and we want sub-2-second image load times. Let me summarize: users can upload photos, follow others, see a feed, like posts. Out of scope: search, stories, live video. Does that sound right?"

Interviewer: "Perfect. Go ahead."

Candidate: draws a clear diagram with boxes for iOS app, Android app, API server, photo storage, database, cache layer "Here's my high-level architecture. Let me walk you through a user flow..." points at diagram, explains coherently

The difference? The good interview has a structure. The candidate is in control of the conversation.

The 5 Steps at a Glance

Step 1 - The Detective Phase: You ask questions like a detective gathering clues. The goal is to extract real requirements from a vague prompt. This is your most important step. If you build the wrong thing, your beautiful design is useless.

Step 2 - Define the Contract: You explicitly state what you're building, what you're not building, and what success looks like. This is a quick alignment checkpoint. Interviewers love this because it shows you think clearly about scope.

Step 3 - Draw the Blueprint: You sketch the high-level architecture. Major components, how they talk, data flows. This is where you show you can think about systems holistically.

Step 4 - Build the House: The interviewer picks something interesting ("Let's talk about caching") and you zoom in. This is where deep technical knowledge shines. You're not designing everything in detail - just the part they're curious about.

Step 5 - The Walkthrough: You trace a real user scenario through your system to prove it works. A user opens the app, taps upload, what happens? This reveals bugs in your design before they happen in the real world.

🎯 Interviewer's Perspective: I'm looking for candidates who know when to zoom in and when to zoom out. Step 3 shows you can think big-picture. Step 4 shows you can go deep. Step 5 shows you can connect the dots. Together, they tell me you're a complete engineer.

What Happens if You Skip a Step?

Skip Step 1 (Understanding): You design the wrong thing. Or you miss an important constraint (like "we need offline support") and your design falls apart under scrutiny. This is the most costly mistake.

Skip Step 2 (Contract): You and the interviewer drift out of sync. You design for millions of users, they were thinking hundreds of thousands. Awkward.

Skip Step 3 (Blueprint): You jump straight to implementation details. The interviewer can't see the forest for the trees. They can't tell if you understand the big picture.

Skip Step 4 (Deep Dive): You stay at the surface. You talk about architecture but can't defend technical choices when challenged.

Skip Step 5 (Walkthrough): You leave a gap in the interview. You've designed components but haven't proven they work together. Holes in your logic might only show up here.

Your Mindset Going In

You're not trying to impress the interviewer with how much you know. You're trying to show that you can think clearly, ask good questions, and solve problems systematically. That's it.

If you follow this framework, you'll be in the top percentile of candidates. Most people go in without a plan and hope it works out. You're going in with a battle-tested playbook.

What's Next

Now it's time to master Step 1: The Detective Phase. This is where everything starts. Ask the wrong questions, and you'll design for the wrong problem. Ask the right questions, and your job is half done.

Back to Mobile System Design Interviews