Mock-собеседование по System Design от Team Lead из Яндекса

Interview practice: https://clck.ru/3ASssc Programming courses: https://clck.ru/3ASt6y Mock interviews with Team Lead from the Yandex System Design section on the it-interview.io platform. Practice interviews with developers from leading companies and get detailed feedback on your salary and grade expectations, as well as any areas you still need to work on! Vladimir's YouTube channel:    / @vladimir_balun_programming   Timecodes: 00:00 - Introduction 01:05 - System Requirements 06:52 - Load Estimation 14:22 - API Design 16:55 - Architecture Design 46:06 - Data Storage Discussion 50:45 - Fault Tolerance and Scalability Discussion 56:24 - Conclusion [[ Candidate Review ]] Recommend this person for the next stage? YES What were their technical skills? 4/5 What were their problem-solving abilities? 3/5 What were their communication skills? 5/5 During the interview, we designed the Instagram feed. We formalized the requirements, estimated the load, designed the architecture and data model, but didn't have enough time to calculate the required resources. The candidate was quite good; he independently guided the design process step by step, but he overlooked numerous edge cases during the design process (I had to constantly prompt him with these). He was pleasant to talk to, and it was comfortable to communicate with him. During the requirements formalization, he forgot to clarify how the feed would be structured, about subscriptions and unsubscriptions, and about subscription limits. He didn't formalize the essence of a post, so for a while, it was unclear what a post was. The RPS calculations were correct and also correctly identified that the system would have a predominantly read load, but he miscalculated the traffic and required data storage volume. When choosing databases, he made an unfounded choice, without providing any justification. He chose in-memory for the cache without calculating or considering how expensive it was and whether it was necessary in that situation. He chose neo4j to store user relationships (subscriptions), but didn't understand how to map user relationships as a graph. Recommendations for the candidate: I would recommend paying more attention to various design nuances (what happens if this or that is present, etc.), and also trying to make well-reasoned choices between tools and databases. System Design. Ranking. No experience. System design. Karpov courses. #interview #mockinterview #leetcode #algorithms