After my initial screening, I moved into a machine coding round, and then into a DSA-focused session that felt like LeetCode-medium territory, with a fair amount of emphasis on getting to the right logic quickly. The process then continued with product/design thinking and finally wrapped with a hiring manager conversation that mixed technical follow-ups with behavioral and cultural fit.
Overall, it felt like a fairly structured sequence: solve, then go deeper, then talk through how I approached ambiguity. The difficulty stayed mostly in the “medium” band, and I felt I could keep up with the pacing as long as I organized my approach and communicated clearly. I didn’t get an offer, but the rounds ended with a sense that my technical communication was understood rather than rejected outright.
> 1 year
Difficult Positive Bengaluru
My experience followed what looked like a standard, structured hiring flow. It began with resume shortlisting and then a recruiter call to talk through my background and interest. After that, I had an online coding test centered on algorithms, data structures, and general programming skills.
Once I cleared that, I went through multiple technical rounds that covered deeper topics like data structures and algorithms, system design, and coding exercises. The final stage was a cultural-fit style discussion intended to check alignment with how the team works.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
