Snowflake low-level design interview
You design and build a small working system in code: classes, interfaces, data structures and how they change when a new requirement arrives. In India, the 90-minute machine coding round (Flipkart, PhonePe, Swiggy, Razorpay) is often the first filter for SDE 2.
0%ready
| Progress | Problem as candidates report it | Next step |
|---|---|---|
| Multiplayer extension of a chess game (LLD)Class diagram, Java code and follow-ups | Start | |
| In-memory file system (LLD)Class diagram, Java code and follow-ups | Start | |
| Time-based key-value store (LLD)Being added: class diagram, Java code and follow-ups | Coming soon |
How Snowflake runs it
- Build five classic systems end to end under a 90-minute timer: parking lot, splitwise, snake and ladder, rate limiter, in-memory key-value store.
- Separate models, services and storage; keep the main method thin.
- Learn when to use strategy, factory and observer patterns, and when not to.
- Handle invalid input explicitly: graders check validation.
The low-level design round, scored by level · New to LLD? Start with OOP, SOLID and the design patterns, then the machine coding problems.
Questions people ask
Does Snowflake have a low-level design or machine coding round?
Not as a fixed round, but candidates report object-oriented design questions: Multiplayer extension of a chess game (LLD); In-memory file system (LLD); Time-based key-value store (LLD).