The process had three rounds total. First came a HackerRank coding challenge where I had to implement CRUD methods for an e-commerce system — nothing too complex, but it was a filter to move forward. After that, both the second and third rounds were done face-to-face.
The second round was more conversational. We talked through my resume and then dove into some systems-level concepts: concurrent request handling, race conditions, and how to think about those problems. It felt like a genuine discussion rather than an interrogation, and the interviewer seemed interested in my reasoning. The third round was more hands-on — I had to call an API, parse the result, and perform some calculations on the data. It was practical and engaging, and I felt like I could show how I actually approach problem-solving.
Both interviewers were approachable and the whole process felt collaborative rather than adversarial. The challenge component was there to assess fundamentals, but they gave space to explain my thinking. If you're going for this role, be comfortable discussing concurrent systems and API integration, and don't just recite memorized answers — they want to see how you actually think through real problems.
Prep tip from this candidate
Focus on systems concepts like concurrent request handling and race conditions, and be prepared to integrate and process API data — those were the core technical themes tested beyond the initial coding screen.
