1. Coding round\n- Seems like two parts problem. Solved part 1. I did not get to do Part 2. I still have no clue... There needs to be some kind of trick to solve it.\n- I communicated well about my thought process including correct time/space complexity.\n- No idea. Conservatively, since I didn\'t solve the question completely. \n- Probably, NH / LNH unless other candidates struggle with part 2. Then, maybe LH? (hope so)\n2. Coding round\n- graph problem\n- Spent about 10-15 mins going through my approach with graph. Interviewer was satisfied with this approach. Completed the problem. Got the time/space complexity correct. Found minor bug (forgot else statement) while going through the test case. Time ran out while doing that.\n- H / LH / LNH (leaning no hire)? I\'m not sure since i missed the small detail and didnt complete the verification step.\n3. Coding round\n- https://leetcode.com/problems/search-suggestions-system/solution/ except that input was sorted.\n- I asked about Trie approach\n- Hint was given. Binary search.\n- I couldn\'t come up with binary search (pretty hard) so i went with Trie.\n- Completed, correct time/space complexity, worked through test cases.\n- H / LH / LNH I\'m not sure since I didn\'t solve with binary search.\n4. System design\n- Design ticketmaster\n- I think i did well.\n- Clarified the requirements, DB design, API design, high level diagrams, and deep dive into components.\n- Minor issue with DB design but fixed it.\n- Walked through APIs.\n- SH/ H /LH\n5. Behavioral \n- Some hypothetical questions and typical behavioral.\n- I answered all of them and interviewer is satified.\n- SH/H\n\nOverall, i don\'t think i did too bad nor super well. Conservatively, I might get downleveled or rejected. I prepared for 4+ weeks. \n\nWill update this post. What do you guys think? \n\nGood luck everyone hope it\'s helpful.

Coding round\n- Seems like two parts problem. Solved part 1. I did not get to do Part 2. I still have no clue... There needs to be some kind of trick to solve i