How the interviewer opens it
“Design a browser-based IDE where users manage files, edit code, and run terminal commands. The service must support many users.”
The prompt is vague on purpose. The first minutes are for you. Reduce the prompt to the core features and agree on the numbers before you draw.
What to clarify first
- Workspace behavior
- User scale
- Read and write traffic
- Workspace resources
- Start rate and delay
- Interactive latency
- File consistency and durability
- Idle workspaces
- Trust and network access
- Availability and exclusions
The interviewer has the answers. In a SysRound round, Alex gives these answers, as a real interviewer does.
Scope of a strong answer
Core requirements
- Create, start, stop, and delete a personal workspace
- List, create, read, save, rename, and delete files
- Run commands through an interactive terminal
- Isolate each workspace and preserve saved files across host failures
Usually out of scope
- Collaborative edits
- IDE extension support
- Git hosting
- GPU workloads
- Regional disaster recovery
- Development of an identity service
What interviewers ask about
- Workspace starts and stops
- Fast starts require spare compute, but idle workspaces waste resources. Delayed actions can stop a newer runtime or create two active runtimes.
- Terminal sessions
- A terminal carries an interactive process, not separate command requests. Slow browsers and lost connections create output gaps and uncertain input delivery.
- Workspace isolation
- Users execute hostile code on shared infrastructure. API checks alone cannot contain kernel attacks, stolen credentials, resource abuse, or data residue.
- File changes and failures
- Editors, compilers, and shells all change the same files. A completed save must survive host failure without creating two writable copies.
Common mistakes
- Treats the IDE as a text editor and ignores terminal behavior.
- Uses one large host with separate user directories as the isolation boundary.
- Keeps every workspace active without a compute or memory estimate.
- Stores files only on temporary disks and treats snapshots as complete durability.
- Retries lifecycle requests without protection against duplicate runtimes.
- Promises command replay or process recovery without a clear failure model.
The bar by level
- Senior (L5/E5)
- Defines lifecycle states, idempotent operations, and recovery after timeouts. Handles terminal backpressure, reconnect limits, durable saves, resource quotas, and hostile code.
- Staff (L6+/E6+)
- Defines ownership across runtime generations and storage failures. Quantifies spare capacity and cost. Distinguishes external resource limits from guest policies. Addresses stale hosts, zone limits, credential scope, and safe resource reuse.