Excalidraw Solo Diagramming vs Narrated System Design Mocks
Many candidates prepare for system design interviews by diagramming alone in a whiteboard tool such as Excalidraw: pick a classic prompt—a URL shortener, a news feed, a chat app—and sketch boxes and arrows until the architecture looks right. It is relaxing, visual, and easy to repeat. The other habit is narrated system design mocks: one prompt, a timer set to the length of the real round, requirements and scale questions said out loud first, tradeoffs explained as you draw, and a short wrap-up of bottlenecks before time runs out.
Both end with a diagram. The useful question is narrower: when does solo diagramming beat narrated system design mocks—and when does the reverse happen?
This is a workflow comparison, not a review of Excalidraw or any other whiteboard tool—many are good, and some interview loops use one directly. Round formats vary by company and level. What stays stable is the difference between drawing a design and leading a conversation about a design while someone listens and the clock runs.
At a glance
| Category | Solo diagramming (e.g. Excalidraw) | Narrated system design mocks (Luna side panel optional) |
|---|---|---|
| Session shape | Open-ended sketching, edit until it looks right | One prompt, fixed round length, talking throughout |
| What gets practiced | Components, layout, vocabulary | Requirements, tradeoffs, pacing, explanation |
| Feedback | Whether the picture looks complete | Self-postmortem: scoping, depth, time spent per phase |
| Environment fidelity | Medium for the canvas, low for the conversation | High for "explain while drawing, clock running" |
| Best for | Learning building blocks, reviewing reference designs | Scoping out loud, tradeoff narration, finishing on time |
| Main tradeoff | Silent, untimed, and endlessly editable | Tiring; awkward to talk to an empty room |
What solo diagramming looks like
A typical solo diagramming session:
- You pick a well-known prompt and open a blank canvas.
- You draw clients, a load balancer, services, a database, a cache, maybe a queue.
- You compare with a reference design from a book, course, or video and fix what you missed.
- You save the diagram and move on to the next prompt.
- Closer to the loop, you still need to practice saying all of it out loud, in order, on a clock.
Honest strengths. Solo diagramming is a good way to build a component vocabulary. Drawing a cache, a queue, or a read replica yourself makes the pieces concrete in a way reading alone does not. A whiteboard tool is fast to edit, so you can try several layouts and see which one is clearer. Saved diagrams become a personal library you can review before a loop. And if your target companies run system design on a shared canvas, getting comfortable with a tool like this removes friction on the day.
Honest limits. Most system design rounds are scored on the conversation as much as the picture: did you ask about requirements and scale, explain why you chose each piece, and talk through tradeoffs and failure cases? A silent diagram skips all of that. Solo sessions are also untimed, so it is easy to spend forty minutes perfecting boxes when a real round wants scoping in the first few minutes and a deep dive before the end. And comparing with a reference design can turn into copying its shape instead of reasoning from the requirements.
When solo diagramming wins: you are new to system design; you do not yet know the common building blocks; you want to review reference architectures; or you need to get fluent with the canvas tool your loop will use.
What narrated system design mocks look like
Narrated mocks flip the polarity: the diagram is a byproduct of the conversation.
- Set a timer to the length of your real round, if the recruiter shared it. Open the canvas you will actually use.
- Pick one prompt you have not diagrammed recently.
- Spend the first minutes on requirements out loud: functional needs, rough scale, read/write ratio, what you are deliberately leaving out.
- Narrate before you draw each piece—say what it is for and what you considered instead.
- Around the middle, pick one component and go deep: data model, scaling, a failure case. If you stall, pause, breathe, and restart out loud.
- Save the last minutes for bottlenecks and what you would change at ten times the scale. Write a one-sentence postmortem on where the time went.
Optional companion: Luna Interview is a Chrome extension framed as a practice / calm side panel—not a substitute for knowing the material, and never an "undetectable" live cheat. Keep it beside the canvas while you own the requirements, the design, and the narration.
Honest strengths. Narration and pacing—the parts interviewers hear. A timed, spoken mock shows whether you scope before drawing, whether you can explain a tradeoff in two sentences, and whether you reach a deep dive before time runs out. Stalling mid-design and recovering out loud rehearses a moment that is common in real rounds. Practicing on the real canvas means fewer surprises on the day.
Honest tradeoffs. Talking to an empty room feels strange at first, and solo mocks cannot ask the follow-up questions a real interviewer would—a friend or a peer session covers that better. Full-length mocks are tiring. And if the building blocks are still unfamiliar, a timed mock becomes a long stall that teaches less than a slow diagramming session.
When narrated mocks win: your interview is within a few weeks; you know the components but feedback says you were "hard to follow"; you run out of time before the deep dive; or you start drawing before asking about requirements.
Decision table for candidate situations
| Your situation | Prefer solo diagramming | Prefer narrated system design mocks |
|---|---|---|
| New to system design | Strong fit—learn the building blocks | After a week of diagramming |
| Know the parts, but answers feel scattered | Light | Strong fit—narrate before you draw |
| Run out of time before the deep dive | Light | Strong fit—timed phases |
| Loop uses a shared canvas tool | Get fluent with the tool | Mock on that same tool |
| Interview in a week | Review saved diagrams | Primary lane—one mock a day |
| Only 30 free minutes on weeknights | Strong fit—one diagram | Save full mocks for weekends |
| Stall when asked "what if this fails?" | Read about failure modes | Strong fit—forced deep dive |
A fair practical method (try both in one week)
Do not pick by which one produces nicer pictures. Learn the pieces silently, then practice leading the conversation.
Diagram days (two evenings): One classic prompt per evening on a blank canvas. Draw it, compare with one reference design, and write down two components you left out and why they mattered.
Mock days (next two or three sessions): One prompt per session you have not drawn recently. Timer at your real round length, requirements out loud first, narrate before drawing each piece, one forced deep dive around the middle, bottlenecks in the last minutes. Keep a calm practice side panel beside the canvas if you use Luna. Score only: requirements said before the first box, a tradeoff explained for every major component, deep dive reached before time ran out.
End of week: Compare where the time went. Many candidates keep both—solo diagramming to learn and review designs, narrated mocks a few times a week once a loop is near.
Common mistakes / when NOT to use each
Skip diagram polishing when you have redrawn the same prompt many times and still have not said a design out loud. A tidy library of diagrams is a common false summit. Also skip memorizing a reference design's exact shape—interviewers usually change the requirements.
Skip mock theater when you reuse a prompt you just diagrammed, pause the timer to look things up, or skip requirements because you "know this one." Also skip any practice-tool framing that promises stealth help in a real employer interview—that is the wrong goal and the wrong integrity bar.
For both: reference designs and AI are for study and postmortems, not mid-mock rescue if you are training transfer. The skill is your design and your reasoning, explained out loud, within the round's time.
Soft close
If your bottleneck is calm practice beside the canvas you will actually use—timed prompts, narration, recovering from a stall—Luna Interview is a Chrome side panel built for that practice loop, not for cheating or replacing study. Soft trial path: https://lunainterview.xyz/
Use solo diagramming when learning the building blocks is the bottleneck. Use narrated system design mocks when explaining tradeoffs on the clock is the bottleneck. The offer goes to the candidate who can walk an interviewer through why each box is there—not the one with the prettiest diagram.
Rehearse with an AI interview copilot, then browse commonly reported interview questions.