The recruitment process started when I was contacted by HR via LinkedIn and asked to share my availability for the initial HR discussion. After sharing my availability, I received an invitation for the discussion. The process consisted of four rounds (it may vary based on the experience and the role applied for). In the first round, HR asked both general and technical questions. Following this, the second round was scheduled, which was the Coding round. In the Coding round, I was given a problem to solve with code. The interviewer was sharing the problem statements on chat and I had to solve them via code. After successfully completing the Coding round, I was scheduled for the next round, the Coding + Tech round. In the Coding + Tech round, I was asked to solve a problem statement using code/pseudo code. The interviewers asked many questions related to multi-threading and concurrency. Both of them were asking a variety of questions. I loved this conversation. I even could not understand a question and straight away told them. After clearing the round, I realised how mature they were. After clearing this round, HR scheduled me for the fourth and final round, the System Design round. During the System Design round, I was given a problem statement and asked to discuss the final design, including API creation and Schema design etc. However, due to the accent of the interviewer, I faced difficulty understanding what was being said. I had to clarify several times and get his agreement on what I thought the design was. Because it's all about the conversation and how you would work with your peers in reality. Although, in my opinion, the interviewer's questions were more inclined towards the domain rather than technical stuff. Additionally, his accent was a problem for me in understanding 30-40% of what was being said. Unfortunately, I did not clear this round and received feedback that I was asking for more hints. Disappointed - but this is what it is. This interview should have involved discussing the trade-offs rather than understanding the domain perspective.