7 Comments
Apr 21Liked by Saurabh Dashora

Never had a system design interview in my life, even though I've met these problems during my career. For which roles people should expect interviews like this? Bookmarking for the future, who knows which position will require this.

Thanks for the shoutout, Saurabh!

Expand full comment
author

Some years ago, they used to be only for specific-architecture roles.

But over the years, I've seen such System Design rounds become quite common for all levels. Sometimes, it's one round or two rounds as well in the overall process. It also gets coupled with a low-level design round.

The tricky part is to be convincing while answering since there are no absolutely right answers.

Expand full comment
Apr 22Liked by Saurabh Dashora

Yeah, there are some open-ended questions which is really good because you can actually have a discussion. Great!

Expand full comment

Thanks for the mention Saurabh!

Expand full comment

People who apply these 23 tips has a much higher chance to nail the system design interviews! Great post and thanks for the shoutout, Saurabh brother!

Expand full comment
author

Thanks Daniel! I definitely feel these tips can help create an orientation.

Also, your article on refactoring tips was superb and valuable. Had to share it 🙂

Expand full comment
May 3·edited May 3

Great guide with some important points.

I think most of the time NFR values are either over stated or under stated. While designing system one should start with flexible approach. IMO, there is no harm in spinning up a 3 node small size DB cluster at first. Let me know your thoughts

Expand full comment