What to Expect in the Miro System Design Interview

Miro's system design round is about an hour long, and it happens on a Miro board. Expect questions about the company's own product domain: real-time collaboration at large scale. Reported examples include designing the whiteboard's edit sync, tracking cursors for millions of users, and keeping shared objects consistent. The interviewer evaluates architecture and communication together, and the board itself is your communication tool. Practice drawing designs in Miro before the interview.

Why Real-Time Collaboration Dominates

Miro's product is a shared canvas where many people edit at once. Every mouse movement, sticky note, and shape change must reach other users quickly. The systems behind this must handle sudden load, conflicting edits, and users on slow networks. So the interview tests whether you can design for those exact conditions. Generic scaling talk is not enough. Answers must engage with the collaboration problem directly.

Question Types Candidates Report

• Design the real-time whiteboard sync. Handle thousands of simultaneous edits on one board. The walkthrough below covers this shape.
• Design presence and cursors. Show who is on the board and where their pointer is, for millions of users. Presence means the live indication of who is currently active.
• Keep one object consistent under concurrent edits. Two users resize the same shape at once. The design must end with both users seeing the same shape.
• Broadcast events at scale. Distribute updates using a publish-subscribe system, where senders publish events and interested clients subscribe to them.
• Handle unpredictable load. A large company workshop can put hundreds of editors on one board within a minute.

A Walkthrough: Sync for a Shared Whiteboard

Step 1: Requirements. Many editors per board, updates visible within about 100 milliseconds. Boards must survive server failures without losing work. Users on poor networks must catch up cleanly. State these targets aloud before drawing anything.

Step 2: Connections. Each client holds a WebSocket, a long-lived two-way connection to a sync server. Every edit becomes a small event: object id, change, author, and time. Small events keep the network cost per edit low.

Step 3: Ordering. One server owns each board at a time and orders its events. Assigning boards to servers is sharding: splitting load by key, here the board id. This gives one authoritative event sequence per board.

Step 4: Conflict handling. Explain the two standard approaches by name. Operational transformation (OT) rewrites concurrent operations so they apply cleanly in any order. Conflict-free replicated data types (CRDTs) are data structures that merge concurrent edits automatically. For a whiteboard, per-property last-writer-wins on shapes is often enough. Saying when the simple rule fails, such as for text on stickies, earns credit.

Step 5: Fan-out. The sync server publishes accepted events to a publish-subscribe channel per board. Subscribed edge servers forward events to their connected clients. Cursor positions can be sent at a lower rate, since they are disposable.

Step 6: Persistence and catch-up. Events append to a log, and snapshots of board state are saved regularly. A reconnecting client loads the latest snapshot plus the events after it. A quick estimate helps: 500 editors sending five events per second is 2,500 events per second per board, which one server handles comfortably.

What the Interviewer Grades

Whether updates stay fast at realistic scale. Whether all clients converge, meaning they reach identical board state. How you reason about tradeoffs, such as CRDTs against simpler rules. And how clearly you draw and explain the design on the board itself. A tidy diagram with labeled arrows counts as communication skill here, because the product is the diagram tool.

How to Prepare

• Build the fundamentals first. WebSockets, sharding, caching, and message queues all appear here. Grokking the System Design Interview covers each with worked designs.
• Go deeper on consistency and replication. Advanced System Design Interview, Volume II treats ordering and fault tolerance in the needed depth.
• Practice on a real Miro board. Draw this walkthrough yourself, with boxes and labeled arrows, inside one hour.
• Prepare numbers. Events per second, payload sizes, and latency budgets make your design concrete.
• See the whole loop. The design round sits in a five-stage process, described in What is the Miro interview process like?.