My process felt like a focused technical evaluation once it got rolling. The interview lasted about forty-five minutes and mixed a harder DSA question with a simpler system-design prompt about optimizing servers. Alongside the technical parts, the round also included math questions that were more about algorithmic reasoning than pure calculation.
The interviewer itself made a difference—this round felt straightforward, and the back-and-forth stayed productive as I worked through each part. Still, I didn’t get an offer. What lingered was that even in a “good” technical interview, the bar was high enough that I needed every piece to land cleanly, not just the easier sections.
> 1 year
Difficult Neutral India
My process started with a coding plus aptitude test, and it moved pretty quickly from there. After that elimination-style round, I had a personal interview, and then I went to a hackathon in Bangalore that was followed by another interview. At each step, they contacted me after the prior round and updated the details, which made the scheduling feel less stressful.
The coding portion felt medium difficulty and fair, but the graph and tree focus showed up again once the hackathon began. In the hackathon environment, I remember that an employee gave hints, and that helped me stay oriented when the problems started to get tricky. The hackathon questions drew from DSA topics like trees, and I also faced multithreading requirements tied to what I worked on during the live portion.
> 1 year
Easy Negative Rājpura, Punjab
My process looked clean on paper: a coding round first, then a technical interview, and finally an HR round. The coding portion felt manageable and fo…
Unlock every Backend Engineer interview experience
