The recruitment process consisted of several stages: Online coding – a one-hour session focused on solving programming problems and demonstrating practical coding skills. Technical meeting – a two-hour in-depth discussion covering system design, problem-solving approach, and technical knowledge relevant to the role. Soft skills meeting – a 90-minute conversation assessing communication skills, teamwork, and overall cultural fit.

The technical round focused on a DSA problem about finding the closest points to the origin, where I was asked to explore multiple approaches like sorting, heaps, and quickselect. It felt straightforward, and I was ready for it thanks to the time I spent on PracHub brushing up on similar questions. The interview also included a behavioral section, but overall, I found the process to be very easy. Happy to say I received an offer, which I gladly accepted!

Tough interview. The Process: Automated Online Assessment (OA) with 2 coding questions and a system simulation, followed by a 4-round virtual Loop. Every single round started with 20 minutes of intense, behavioral behavioral questions diving into Amazon's Leadership Principles, followed by 25 minutes of technical coding or system design. Amazon interviews are a test of mental endurance because you have to switch from deep behavioral storytelling straight into complex coding which can be so difficult. I used Apex Interviewer to practice the cognitive context switch. Running through their live-coding workspace helped me ensure my technical communication and architectural structures remained sharp and automatic, even after spending the first half of the interview defending my past project metrics. I fed the practice AI questions I extracted from glassdoor and gothamloop. In the end, the offer was way lower than I hoped.