Practiced popular system design problems like designing a URL shortening service, Pastebin, Instagram, Dropbox, Facebook Messenger, Twitter, YouTube/Netflix, Typeahead Suggestion, API Rate Limiter, Twitter Search.
Practiced system design for some Google products, including Google Search, YouTube, Google Photo Sharing and Storage, Google Docs, Google Drive.
Revised system design concepts such as CAP and PACELC theroem, SQL vs No-SQL, Types of No-SQL databases and their applications, Consistent Hashing, Bloom Filters, Load Balancers, Horizontal Scaling, Caching, Database Partitioning/Sharding, Indexes, Rate Limiting, Distributed Queues, Request Deduplication.
Watched few YouTube videos on system design.
Key Takeaways
from rohitverma
Develop a solid grasp of data structures and their applications. Tree questions were a recurring theme in three rounds of my interview.
Google emphasizes the quality of your solution, unlike META, where speed is the primary focus.
The responses to follow-up questions carry significant weight.
Be prepared for lengthy problems and writing substantial code during the interview.
Some follow-up questions may delve into complexities related to implementing your solution in a production environment.
from ricbedin
Interviewing is a skill and it does not reflect how good you are as a software engineer
learn how to master it
apply it in a simulated environment
reflect on feedback
Your job is to convice whoever is interviewing you that you can do the job
Each interview is an encapsulated experience
do as many interviews as possible, starting form the lowest priority ones
try to align your top-tier companies’ timelines as closely as possible
do not let other people experience affect your view of your own process