At the start everything looked great. Recruiters were very prompt and gave a very detailed walkthrough of the hiring process. Recruiter call also comprised some technical questions like "What data structures are database indexes based on? What are various isolation levels ? what is CAP theorm? etc. " The focus was heavily on multi-threading, core java and database concepts. The next stage was live coding interview. Was asked to build a in-memory LoadBalancer app. I followed TDD as advised by the recruiter. The interviewer and I both had some network issues hence there was some time lost in between. However I was still able to finish the assignment step by step. Throughout the interview the interviewer did not bother to tell me that there are certain number of functionalities to be completed failing which would result in rejection. He seemed quite happy with my code and approch. One day later I get rejection letter stating that I should expand my Junit knowledge and not always rely on assertTrue method. Also should improve my coding speed as it currently impacts your ability to complete challenges on time. Though I agree with the first point the later one seemed quite irrelevant. Looking at some other very similar interview experiences it looks like they are not looking to hire and are just doing it to make a impression in the market that they are growing. I feel like I dodged a bullet as at the end of the interview I asked the interviewer "How does he find working at the company" and he let out a long sigh before saying "It's Hard" and went out to share how people are overworked. There's a constant need of context switching for the engineers etc.

Recruiter round, they’re basically looking for buzz words. They asked for my experiences in handling different scenarios, then other db and concurrent related questions . Overall it was straightforward, just go through other’s experiences here and you should be covered