A real-time interview assistant does two useful things in a whiteboard interview. First, when the interviewer sets the problem, it captions the prompt and shows a structured answer: the components a complete diagram needs and an order to draw them that keeps the explanation coherent. Second, once you have drawn, Read screen (Ctrl+Shift+S) captures your own diagram and answers about it, which works as a critique: a missing component, an arrow with no label, a single point of failure you have not mentioned. The drawing itself is yours. The tool cannot draw, cannot see what you meant by an unlabeled box, and cannot replace the explanation the interviewer is scoring while you draw.
This guide covers the kinds of diagrams whiteboard rounds ask for, how to draw from a list without reading from it, how to get a useful critique from your own drawing, and how to practice with paper and a timer.
What a virtual whiteboard round asks you to draw
"Whiteboard interview" once meant algorithms on a physical board. Over video it usually means a diagram in a shared whiteboard app, with the interviewer watching the canvas and listening to you explain. The diagram types that come up, and what each one is testing:
| Diagram type | Typical prompt (examples we wrote) | What the component list gives you | Draw first |
|---|---|---|---|
| High-level architecture | "Sketch a photo-sharing service." | Clients, API gateway, services, storage, cache, queue, CDN | The client and the main write path, left to right |
| Sequence or request flow | "Walk me through what happens when a user posts." | The actors in order and the messages between them | Vertical lanes for each actor, then the first request |
| Data model | "What tables would you need?" | Entities, keys, relationships, the hot table | The entity the system is about, then what points to it |
| State machine | "Model the lifecycle of an order." | States, transitions, the failure and timeout edges | The happy path as a straight line, then the failure edges |
| Deployment or infrastructure | "How would this run across two regions?" | Regions, load balancers, replicas, the replication arrows | One region complete, then copy and connect |
| Algorithm trace | "Show me how your merge works on this input." | The steps and the invariant to keep | The input, then one step at a time with the pointer positions |
The last column matters more than the third. Interviewers follow your pen; a diagram that grows in a sensible order is easy to follow and a diagram that appears in random pieces is not, even if the final picture is the same. Our AI for system design interview guide covers the architecture case in depth; this page is about the drawing.
Drawing from a list without reading from it
CoPilot Interview's real-time interview assistant returns the component list as text in its own desktop window. Three settings make it usable while your hands are on the canvas:
- Click-safe mode (Ctrl+Shift+F). The window never takes focus from the whiteboard app, so a glance does not interrupt your drawing.
- Bullet points. Press the Bullet points button so the list is a list; six short lines read faster than a paragraph.
- Hotkey scrolling (Ctrl+Shift+/). Move down the answer without clicking into it.
Then work in a loop: say the component, draw the box, label it, explain the arrow into it, glance at the list, repeat. Saying before drawing matters. The interviewer hears "next I need somewhere to store the images themselves, separate from the metadata" and then watches an object store appear, which reads as a thought becoming a drawing. Drawing first and explaining afterward reads as copying.
Keep the whiteboard window beside the assistant window, both on your own screen, and if you share your screen, share the whiteboard window only. The real-time interview assistant for presentation interviews guide has the same window arrangement for slides.
Read screen on your own diagram
The second use is the one most people miss. After you have drawn the first version, press Ctrl+Shift+S with the whiteboard visible. The app captures the screen and answers about what is shown. Type a question to steer it; the typed-question field accepts anything. Useful prompts (ours, as examples):
- "What is missing from this architecture for the requirements I listed?"
- "Which component here is a single point of failure?"
- "What will the interviewer ask about next?"
- "Is anything on this diagram unlabeled or ambiguous?"
The answer, in about 2 seconds, is a short critique you can act on while the interviewer is still looking at the picture: add the missing cache, label the arrow, mention the failover before being asked. Pin screen captures a chosen area, such as the canvas alone, and answers what is drawn there.
Two cautions. Read screen reads what is drawn, so an unlabeled box is a box; the critique is only as specific as your labels. And a critique is a list of possible gaps, not a verdict. If it suggests a component your requirements do not need, say so out loud; that reasoning is worth more than the component.
Algorithm whiteboarding
Some whiteboard rounds are still algorithmic: trace your approach on an example, draw the tree, show the pointer positions. Coding mode (Ctrl+Shift+C) with the 📝 Note option helps here, because the 2-4 line approach and complexity comment is a plan you can draw from. If the interviewer asks "why does that invariant hold?" press Ctrl+Shift+E (Talk answer) for an answer in words. Draw the input first, then one step at a time, and say the invariant at each step. For the data-structure patterns that recur, our guide to graph algorithms for coding interviews is good drawing practice.
What the tool does not do on a whiteboard
It does not draw, arrange or clean up. A cluttered diagram with arrows crossing everywhere is yours to fix. It cannot see the scale numbers you wrote in the corner unless you type them, and it does not know what the interviewer said about requirements unless that was captioned as a question. It cannot help with pen control in an unfamiliar whiteboard app, which is the most common practical failure in these rounds: candidates lose two minutes finding the text tool. Open the whiteboard app the employer uses the day before and draw a sample architecture in it.
It also does not fix thin understanding. If the component list says "message queue" and you cannot explain what the queue buys you in this design, the follow-up finds that out in one question.
Practice with paper and a timer
The free AI mock interview includes system design prompts built from the job description. Run one, draw your answer on paper or in a whiteboard app while you explain out loud, and let the answer be scored out of 10 with what worked and a model answer. Then, on your own, press Read screen on your drawing and compare the critique with the model answer. Twenty minutes per prompt is a realistic target; most rounds allow 30 to 45 for the drawing part.
Pick canonical problems and draw each one twice, once cold and once after reading the guide. Design a chat app and design a notification system are two that exercise most of the components in the table. The free AI interview assistant plan covers 15 minutes a day of practice with no signup; a live 60-minute whiteboard round needs Standard (60-minute sessions) or Pro (70-minute sessions). If you compare AI interview assistants for whiteboard rounds, test whether a tool can read a diagram you drew and say something specific about it; a tool that only answers spoken questions misses half the round.
Follow the rules of the employer or assessment you're in — many people use it only to practice, which works on the free plan.
Draw a design prompt out loud before the real round
The free AI mock interview builds system design prompts from the job description, reads them aloud, and scores each spoken answer out of 10 with a model answer. Draw while you talk. 15 free minutes a day, no signup.
Try a free AI mock interviewFAQ
Can a real-time interview assistant draw on the whiteboard for me?
No. It shows a text list of components and an order to draw them in its own desktop window. You draw on the shared whiteboard yourself, and the interviewer watches the drawing appear while you explain it.
How does Read screen critique my diagram?
Press Ctrl+Shift+S with the whiteboard visible and the app captures what is drawn. Type a question such as 'what is missing' or 'which component is a single point of failure' and a short critique appears in about 2 seconds. It reads only what is labeled, so label boxes and arrows first.
What should I draw first in an architecture diagram?
The client and the main write path, left to right, then storage, then the supporting pieces like cache, queue and CDN. Interviewers follow your pen, so a diagram that grows in a sensible order is easier to score than one that appears in random pieces.
Does it work for algorithm whiteboarding, not just system design?
Yes. Coding mode with the Note option gives a short approach and complexity comment to draw from, and Talk answer (Ctrl+Shift+E) answers 'why does that work' questions in words. Draw the input first and trace one step at a time.
Which whiteboard apps does it support?
Any. The assistant captures your computer's audio for the interviewer's questions and captures the screen for Read screen, so it does not depend on which whiteboard app the employer uses. Practice in that app the day before so you know where the tools are.
Is the free plan enough to practice whiteboard interviews?
For practice, yes. The free AI mock interview includes system design prompts, scores spoken answers out of 10 and gives a model answer, and Read screen works on your own drawing. A live 45- to 60-minute round needs Standard or Pro for the longer sessions.