# How to Whiteboard for System Design Interviews

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/blog/how-to-whiteboard-for-system-design-interviews
Source observed: 2026-11-04T22:02:49.046Z
Last checked: 2026-11-04T22:02:49.046+00:00
Indexed: 2026-11-05T06:51:22.757+00:00

---

# How to Whiteboard for System Design Interviews

We wrote this System Design article to help software engineers, engineering managers, and technical program managers structure ambiguous system design interview answers on a physical or virtual whiteboard. We use “Design Instagram” as the main sample question and cover six steps.

Anthony Pellegrino • Last updated a month ago

## Six Tips for Whiteboarding System Design Questions

Whiteboarding lets you illustrate your thinking efficiently with a marker or web app. System design interviews commonly use tools such as Zoom Whiteboard, Miro, or [Whimsical](https://whimsical.com/?ref=exponent-blog.ghost.io). Ask your recruiter which platform your target company expects and practice with that platform.

### 1. Clarify and Record Requirements

System design questions are often vague, so begin by restating the prompt and breaking it into manageable requirements. Ask:

- What daily load must the system handle?
- What data will be stored?
- How often will the data be accessed or changed?

Write the requirements as bullets and use back-of-the-envelope calculations to estimate daily, monthly, and annual traffic. For example, 100,000 daily users, each sharing approximately five photos of roughly 5 MB each, gives a starting point for component decisions. Keep the requirements visible and refer back to them as you design.

> **How to do this on a whiteboard:** List requirements in bullet points. Write the simple formula used to calculate daily, monthly, or annual traffic, and keep it visible in a corner of the screen.

#### Sample: “Design Instagram” clarifying requirements

This **sample system-design scenario** includes:

- Uploading images from a mobile client
- Letting users follow other users
- Generating an image feed
- Supporting 10 million users, two photos per month per user, and 5 MB per photo

The sample calculation produces a baseline of **1.2 petabytes of data per year**. The design should handle that traffic and ideally scale beyond it. Align with the interviewer before moving on.

### 2. Diagram a Quick Data Model

Define the data model next. Different data types may require different storage and access patterns, and diagramming their relationships helps eliminate unsuitable component choices.

> **How to do this on a whiteboard:** For relational data, draw small two-column tables for each database. One column contains the ID—for example, “name” in a `users` table—and the other contains the data, such as a string value.

#### Sample: “Design Instagram” data model

In this **sample design**, we need to store users, photos, and user interactions. We choose a relational structure such as MySQL or Postgres because queries such as “fetch all photos posted by X user” may be frequent. Draw three tables: users, photos, and user interactions.

![Sample user and photo data-model diagram](https://storage.ghost.io/c/a5/f5/a5f5c2f0-4c62-43c7-891b-662a0b6d68b3/content/images/pmlesson/2021/10/image-2.png)

The visible sample diagram shows fields including user `id`, `name`, `email`, and `location`, and photo `id`, `user_id`, `caption`, and `location`; it also shows primary-key and foreign-key relationships.

### 3. Note Decision Points Throughout

Record the takeaways that the hiring manager should focus on while you draw. Explain the trade-offs in your system decisions and why each choice fits the problem space.

> **How to do this on a whiteboard:** Star or circle key components, put choices in parentheses, or underline them. Choose one method and use it consistently.

Design trade-offs are especially important takeaways and should be noted frequently.

### 4. Take Notes

Reserve an area of the whiteboard for notes before you begin. Notes clarify the diagram, preserve key concepts, and let you refer to previously defined components without repeatedly re-explaining them.

> **Tip:** As you build the system, include notes about design trade-offs and takeaways.

> **How to do this on a whiteboard:** Dedicate a corner to notes and add them sequentially. Keep them organized and legible so you can refer to them later.

### 5. Diagram the Design: Start Simple, Then Scale Up

Start with the simplest design. Explain component relationships and connect them to the requirements you established earlier. Then elaborate as the system scales, explaining decisions and checking in with the interviewer regularly. System design whiteboarding is intended to show high-level decision-making and domain knowledge, so clean, simple representations work best.

> **How to do this on a whiteboard:** Represent components with simple shapes—for example, databases as cylinders—and relationships with arrows. Label everything and stay consistent; there are few strict conventions.

In a remote interview, the interviewer may require an online whiteboarding tool; we like [Whimsical](https://whimsical.com/?ref=exponent-blog.ghost.io).

#### Sample: “Design Instagram” system diagram

A common **sample approach** starts with the backend and databases after defining the data model. The example uses:

- One database for metadata
- AWS S3 for photo object storage
- A cache for quick data retrieval

![Sample Instagram system-design diagram](https://storage.ghost.io/c/a5/f5/a5f5c2f0-4c62-43c7-891b-662a0b6d68b3/content/images/pmlesson/2021/10/image-3.png)

As the **sample system** scales, add a load balancer to route requests to the appropriate services and reduce the risk of overloading deeper components.

### 6. Keep Things Legible

Whether the interview uses a physical or virtual board, make the design easy to read. Avoid cramped writing and convoluted diagrams. Leave white space between points and diagrams so the hiring manager can understand the design.

## Examples of Whiteboarding System Design Questions

We bring the process together with these sample prompts:

- Design Instagram
- Design Facebook Messenger
- Design Twitter’s API

For more sample system design questions, use our [System Design interview course](https://www.aced.io/courses/system-design-interviews?ref=exponent-blog.ghost.io). You can also review our guide to the [most commonly asked REST API questions](https://www.aced.io/blog/top-rest-api-interview-questions/?ref=exponent-blog.ghost.io).

## Ace Your System Design Interview with Aced

We help candidates prepare with company-specific interview guides, a System Design interview course, professional coaching, and a community of tech insiders and job seekers. You can:

- Practice behavioral and system design skills with our [interview practice tool](https://www.aced.io/practice?ref=exponent-blog.ghost.io).
- Enroll in our [System Design interview course](https://www.aced.io/courses/engineering-management?src=nav&ref=exponent-blog.ghost.io).
- [Create a free account](https://www.aced.io/signup?src=blog).

### Related Blog Posts

- [The Top 30 Engineering Manager Interview Questions of 2022](https://www.aced.io/blog/top-30-engineering-manager-interview-questions) — a month ago • 8 min read
- [Stripe System Design Interview (2026 Guide)](https://www.aced.io/blog/stripe-system-design-interview) — a month ago • 8 min read
- [DoorDash System Design Interview (2026 Guide)](https://www.aced.io/blog/doordash-system-design-interview) — a month ago • 6 min read
- [Microsoft System Design Interview (2026 Guide)](https://www.aced.io/blog/microsoft-system-design-interview) — a month ago • 8 min read

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fblog%2Fhow-to-whiteboard-for-system-design-interviews&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fblog%2Fhow-to-whiteboard-for-system-design-interviews). Opening a form does not execute a tool.