There was an online coding round in which I had to generate org hirerarchy. The data was coming from a file, with each employee having information about his boss, and CEO will have NULL as his boss. This was followed by a phone interview. There was an XML file, from which you will have to create a tree structure. I took quite a lot of time in this question, but was not able to solve it fully. Next I was asked to design an LRU cache, which I did it. Got an onsite call next day. I flew to LA and stayed at one of the ocean facing hotel. The level of difficulty was at onsite interviews was pretty hard and questions were quite unexpected. First question was to based on finding out the number of ways of doing something. In next round I was asked to build a snake and ladder game and write test cases for it. Third round was to write a crawler program which removes race condition. Last round was a design question where I had to design a system which interacts with external systems. I did not get the job offer because I was not doing well. I was requiring a lot of help from interviewers in some of the questions. Basically, before they ask you, tell them that you are going to handle such and such corner cases. They are not interested in writing codes, but they are more interested in how many different approaches you can take, and how many different corner cases you can handle. So, dont wast your precious 1 hour in writing any code, unless they ask you to. Write a function signature at the max and move on to writing the cases that you will handle. I did waste a lot of time in writing loops and i, j, k etc. and did not think about different cases where my program will fail and how I will optimize my approach.