I had one virtual technical round. The interviewer was punctual, and the interview started on time. After a brief introduction, the interviewer asked approximately 10–15 questions related to AWS services, including SRS, S3, CloudWatch, CloudTrail, RDS, DynamoDB, EC2, Serverless architecture, and SQS. There were also 5–6 questions related to Node.js, covering topics such as encryption, microservices architecture, thread pooling, and service workers. The discussion was primarily focused on cloud architecture concepts and backend fundamentals.

I had a disappointing interview experience at this company. The interview lasted almost one hour and covered a wide range of technical questions, all of which I answered to the best of my knowledge. Despite this, I was rejected without any clear feedback. What was more concerning is that a close friend of mine had an interview with the same interviewer and experienced a very similar situation — a long interview, detailed technical discussion, and rejection without explanation. This made the process feel inefficient and unclear, especially considering the time and effort invested by candidates. I would advise future candidates to be cautious and ensure expectations are clearly aligned before proceeding with interviews.