0 day streak

Snowflake system design interview

Enterprise SaaSProduct Global

Design rounds lean toward data and storage systems and often shift requirements mid-way to test adaptability. Coding problems frequently grow into multi-threaded or distributed versions, so design thinking leaks into coding rounds too.

0%ready
ProgressQuestion as candidates report itWalkthroughPractice boardNext step
Web crawler extended to multi-threaded and distributed crawlingWeb crawler Web crawler – Watch
Recurring notification systemNotification system Notification system – Watch
Authentication for a multi-tenant appAuthentication system Authentication system Open board Watch
Photo album backend with metadata and blob storageWalkthrough being added––Coming soon
Shared quota service across productsWalkthrough being added––Coming soon
Caching for query viewsWalkthrough being added––Coming soon
Design a databaseWalkthrough being added––Coming soon
Speeding up work across many CPU coresWalkthrough being added––Coming soon

Which levels get a design round

SDE 1Software Engineer I (IC1)System design
SDE 2Software Engineer II (IC2)System design
SDE 3Senior Software Engineer (IC3)System design
StaffStaff / Principal Software Engineer (IC4+)System design

How to answer any design question: the LADDER method · How the design round is scored by level

Questions people ask

When does Snowflake ask system design?

A design round is part of the loop at SDE 1 (Software Engineer I (IC1)), SDE 2 (Software Engineer II (IC2)), Senior Software Engineer (SDE 3) (Senior Software Engineer (IC3)), Staff Software Engineer (Staff / Principal Software Engineer (IC4+)). Design rounds lean toward data and storage systems and often shift requirements mid-way to test adaptability. Coding problems frequently grow into multi-threaded or distributed versions, so design thinking leaks into coding rounds too.

What system design questions does Snowflake ask?

Web crawler extended to multi-threaded and distributed crawling; Recurring notification system; Authentication for a multi-tenant app; Photo album backend with metadata and blob storage; Shared quota service across products; Caching for query views; Design a database; Speeding up work across many CPU cores.