YoE: 12+\nCurrent: Tech Lead at a unicorn Indian startup\n\nI\'m avoiding listing down the exact problems but this should give you all a general idea on how to prepare\n\nProduct/System Design: \n - Design a system which appears in most preparatory material. Nothing special. Some counter questioning.\n\nProduct/System Design:\n - Design a system which appears in most preparatory material. Nothing special. No counter questioning. This question presented challenges related to scaling a search server. You can read on how to scale Elasticsearch or Solr if you\'ve worked on it before.\n\nSpeed Coding (this is the only exact question I\'m giving away, as it\'s quite tricky to get right in a 40 minute pressure round)\n - Find local minima in array (search in leetcode)\n\nRelaxed, laid-back coding:\n - Level order traversal of a tree (practice a few problems related to this)\n - Alien dictionary (popular FAANG problem, do all possible variants of this problem. search on leetcode)\n\nHM:\n - Behavioral questions\n\nProbable reject as I bombed the speed coding round. It was absolutely disgusting. The others were good/above average as per my assessment. FB expects you to not bomb even a single round. Above-average performance in every interview is a must.\n\ntl;dr leetcode FTW. For system design, pick up any resource and go through it. At the end of the day, if you have not worked on scale you will only have theoretical knowledge and you won\'t be able to do better than the average candidate. For SDE2/L4/E4 levels, it\'s probably okay but anything more than that (7/8+ yoe) you need to find a scale project in your current job to get that experience.

YoE: 12+\nCurrent: Tech Lead at a unicorn Indian startup\n\nI\'m avoiding listing down the exact problems but this should give you all a general idea on how to 