Interview Process - \n\n1 Online assessment - \n3 questions: 2 easy, 1 medium done via codility\nPassed this with 100% (recriter tells you the score, not codility)\n\nVirtual Onsite - \n4 rounds - 15 minutes of discussion about expereince , role offerings and 30 minutes for coding or system design\n\n1. API based system design - I didnt do the best job at this, should have spent more time gathering requirements\n2. Easy coding question - Asked an optimization follow up which I botched up\n3. Easy-Medium coding question - Probably the best round, was able to code it even though psuedocode was ok, did a dry run\n4. System design - Standard known system design question\n\nThe effective time you have is only 30 minutes or less to finish the task (which is sufficient), the rest of the time goes into experience and job discussion\n\nSystem design questions were also on codility, had to write psuedocode and not draw diagrams\n\nThe job itself seems to be very demanding! I doubt I\'m going to be given an offer, but either way I dont think I will move ahead.\n\nAlso just want to reiterate common knowledge for other people preparing, doing questions on leetcode doesn\'t really mimic the actualy interview. I\'ve done about 400 Qs at this point and yet, I even botched up an easy question. My mind kinda went blank and at that point its hard to get back into focus and keep going. I would say after you\'ve covered most different types of questions on leetcode, try to practice in mock interviews or any other technique to mimic the real thing.

Interview Process - \n\n1 Online assessment - \n3 questions: 2 easy, 1 medium done via codility\nPassed this with 100% (recriter tells you the score, not codili