The interview process typically started with an online coding assessment focusing on data structures and algorithms.

After clearing that, I moved on to a couple of technical interviews. These mainly revolved around solving real-time problems on a whiteboard or a shared doc—again, mostly DS/Algo-based.

One of the rounds had a strong focus on system design, where I had to architect a scalable service.

There was also a behavioral round where they assessed culture fit, past experiences, and collaboration style.

In some cases, there was a final round with the hiring manager that covered high-level discussions around technical vision, role expectations, and how I would contribute to the team.

One question that stood out was: ‘How would you design a rate limiter that works across distributed systems?’

It was interesting because it tested both my understanding of system design and my ability to think about consistency, latency, and fault tolerance at scale.