The interviews involved 4 rounds The interviewers were very self-proclaimed and would do anything to beat you down. If an interview is around system design, then you need to follow with the candidate around certain decisions not ask tool specific questions. it should not matter if someone has used aws lambda or not. if someone knows the working and fundamentals, lambda or any other tool is just a 2 hour job then. but they were all fixated upon tools. Very poor experience. classic case of frogs in a well.

The interview process was quick and straightforward. The following rounds took place. 1) Started with an assignment to design and implement a RESTful service for a restaurant management software. (Any language and framework). - I used Golang for this round. 2) Once my assignment was reviewed, I had a call with one of the cofounders and he explained me about the company and future process. 3) Technical interview mostly focusing on the theoretical stuff like OOP concepts, multithreading and java related questions. - I didn't like this round very much as the focus was not on any practical knowledge. 4) Interview call with the CTO where he discussed about my previous projects and asked questions regarding it. He also gave an insight to what the company does and the tech overview. - This interview helped me understand much better what the company does. 4) The last round was supposed to be the final round but I had to go through one more technical round as mentioned by the HR. I enjoyed the last technical round as it started with some DS algo question, then the focus shifted on databases and other concepts related to it like indexing and optimisation. At last there was a system design question where I had to design a distributed cache. - This round went well 5) I had the final call with the cofounder where I got the offer and other details were sorted out.