First round was an on-campus interview with manager. The interview was good as there was a general project discussion followed by basic data structure and algorithms questions. The only downside was that the interviewer wanted me to explain the one whole semester long project in about 2-3 minutes and then expected that I should be able to explain in and outs of what I did. Two weeks later, got an invitation for on site interviews at their New York office. Nice location and friendly atmosphere. There were three 1 on 1 interviews scheduled - two with managers and the last one with director. First manager was quite unfriendly and started shooting questions right away and used to get a bit irritated often upon not receiving an expected answer for the question asked. The interviewer was not interested in discussing approaches to answer and just expected the right answer. This round focused heavily on projects done by me and some theory based questions were asked. One of the questions asked was how to remove duplicates from a list. In the first approach, I described to use a hashSet while iterating over the list and if we find a already present element, then remove that element from the list. However, the interviewer said that is should not be done that way and I should just use a set and add all the elements of the list to the set and return the set itself. This didn't made any sense since the original list still contains duplicate and returning the set instead of a list as an answer was weird. I tried to discuss this but the interviewer got irritated. Second interviewer was friendly and this round contained one algorithm question and few data structure question. As soon as we sat down for second round, the interviewer asked me to introduce myself and instead of paying attention and looking at me, the interviewer started drafting the question on a piece of paper and kept on doing it until I finished speaking. The question asked had a major error. It was a standard searching algorithm on leetcode(find bad version) which can be easily solved iteratively or recursively but the interviewer didn't give the stopping condition or the base case that is actually needed to solve the question but was still satisfied with my approach. No coding was required and I had to just verbally describe the algorithm. I tried to tell the interviewer that he/she has forgotten that part and the interviewer seemed confused and changed the question. It was kind of funny. The interviewer was equally confused while phrasing one more data structure question during the interview and kept on changing the original problem statement. Third interview was with director who was highly knowledgeable and this round was again focused on one of my projects. It was a very good and in-depth discussion of algorithm used by me to do the project. Enjoyed the conversation. By far the best round. Overall, it was not a good assessment since the profile was for a developer and no aptitude/coding questions were asked and it was only about projects. Received a rejection three weeks later. The reason wasn't given and I didn't even expect one from them since there were no definitive skill testing questions asked. One advice to the company is to train the managers to conduct interviews and ask question since I have interviewed with several other tech companies and this was one was the most weird.