Finally a company that has figured out how to conduct a software engineering interview... This was the best software engineering interview process that I have encountered in my entire time in industry. I didn't get the offer but I left the company with deep respect for the people who interviewed me and the product that they have made. First I had a ~45 minutes phone screen that involved general questions regarding my resume and a very simple coding task that I had to explain in pseudocode (as it was on phone). Please take this round seriously. Then, being called onsite I had 4 rounds with four different people who all very definitely way above experienced than me and did know what they were doing. First round was a product demo. Their product is undoubtedly one of the best softwares that I have seen. The guy who gave me the demo was very friendly and nice. This was a real big data tool that they had created. The engagement with the product happened naturally for me in the demo. It is important that you show engagement with the product or you can be rejected. Second one was a very undirected round. The interaction started with the other guy telling me a little bit about himself and then asked about my work. I began explaining my work and a little bit of the things that I knew of what my company did, which was not really something I knew in depth about. The interviewer got stuck on that part and I tried to explain what I knew, but apparently that did not impress him. I'd recommend you to stick to the work you have done when going for a round like this one in any company. This is the round I could not do well in. Third round was a Code Review by another very nice guy. This was the most unexpected round in the sense that I have never been asked to do a code review in an interview. It was a code that the guy had written himself. I could barely review 25% of the code that he brought to the round but apparently I was able to demonstrate my eye for good code. It involved refactoring code properly into smaller and sensible methods and also refactoring code that is repetitive into its own method. See which lines can throw exception and have them wrapped in a try-catch. Any line that should be wrapped in a 'using'. You cannot perform a good code review if you don't write good code yourself. I'd recommend reading Code Complete 2 to improve your coding skills. Fourth round was the only on-whiteboard coding round. Asked to write code for Merge Sort. Was asked to explain how the complexity is O(n Log n). The interviewer was concerned about me able to explain the idea and implement a working code, even if to begin with the code was not very space efficient. This round was over as soon as I provided a working code. This guy, who initially sounded very terse, laconic and to some extent angry, turned out to the be the funniest person I met that day. He spoke many languages, including my mother tongue. His appearance completely belied his nature.