First round video interview. Basic Java questions and coding exercise on shared platform. After you clear this they will give you coding test. Next round in person for 2.5 hours. First 1.5 hours questions on Basic Java and discussion on your coding exercise. They acted as the sweetest people on Earth, but they will be planning internally to reject you even if you give right answers. Next round of 1 hour they will ask you to describe in detail any of your past projects, Rudest set of people I have met so far. They were not questioning me on the architecture of the project I chose, they were just insulting me. And by that I literally mean insulting. They decided that the project I described was wrong from all aspects and it should be even exist according to them. Of course I was to be rejected, I knew this from the interview. But the feedback they shared was shocking. I have 9 years of experience in Java but according to them I don't deserve to be a software engineer. I do not even know the basic concepts of OOPS like inheritance encapsulation. I am surprised what the video interviewer found right in me that he cleared me.I am if I am going for an interview, I would for sure prepare the basic concepts if not the advanced ones. And they still feel that I was dumb enough to show up in their office without having any knowledge of Java . Beware of them. They might demean you for you to be ashamed of yourself.

total 3 to 4 rounds. The initial first round is with Talent Recruiter and expect this also asking technical questions, asked difference between ConcurrentHashMap and Map, which is more thread safe. which situation we should choose set vs list. What is time complexity for different basic data structure. How you go about designing the priceline like system, all these been asked in first Recruiter call. Then second round was with Principal software engineer, it is more like coding problem with real work style, there will be coderpad with imported Java project, having bunch of class, service and unit test already written. Some unit test is taking time and failing, looking the unit test, class, method, try to figure out why unit test search from Map is taking so much of time, what things you see wrong and how do you improve it ? It ends up being the Map the registration class hashCode method was overiden and it had bad code returning hascode of static string. What all other things are wrong in code, describe about project , something from resume etc