By far the most unprofessional company you can ever imagine. After scheduling the first phone interview, recruiter asked me to reschedule. Upon rescheduling, the interviewer didn't call me at the scheduled time so it had to be rescheduled again. In the email correspondence, their recruiter cross-texted- In confirmation email, the name, phone number and resume were of a different candidate who was probably interviewing for the same position. I cleared the first interview, but seems like another team was also interested in my profile so I had to do a phone interview with second team too. The recruiters took more than a week to respond for scheduling phone screens or conveying next steps. On passing phone screen, I was called for Onsite interview with both team. My onsite interview went really well. A day after interview, I was asked for 2 references as the next step. My references never received any communication from them, but then a day later I got a 'Thank you' note. The recruiter didn't even care to respond when I asked for feedback. I feel lucky that I didn't get the offer from unprofessional Groupon, else I wouldn't have landed at Amazon.

It was a 2 week process for me. Stage 1 - Recruiter phone call - 30-45 mins. It was very engaging and positive. Stage 2 - First technical round - Its on the difficult side technically. The questions were very practical starting from the DNS - Load Balancer - Stacks to the http pages and the internal functioning and redirections if any. Also, there were some serious coding questions. Stage 3 - 4 Xoom Interviews . 2 were technical, 1 was manual and 1 was behavioral. The 2 technical interviews were quite tough in my opinion, but the interviewers were kind enough to throw hints and explanations as and when needed. The questions were highly focused on the data structure part and even the coding questions were more emphasized towards efficiency. In total I got 5 coding problems. I was able to solve 4 of them. But they are really looking for more efficient programs and were looking for the best solution. Even the questions were towards the depth of knowledge of Java, not the basic ones. I feel it was a bit over done requirement for a QA role, (I have created multiple frameworks in my career, and I felt that they were looking for a developer rather than a QA). But undoubtedly, it was a great learning experience throughout. and the interviewers were awesome in their respective skillsets.