Razorpay Product Manager Interview Guide

I was really impressed by how organized Razorpay's hiring team was throughout the process. They were clear about timelines, flexible with scheduling, and kept me informed at every step—which honestly set a positive tone from the start.

The interview itself was structured across four distinct rounds, each testing a different dimension. The first round dug into my background and asked me to walk through a product case I'd actually worked on. They wanted to understand my thinking, not just hear a polished story—so I talked through the problem I identified, how I prioritized, and what metrics mattered. They pushed back on my assumptions, which kept me honest.

The product thinking rounds were heavy. I was asked to design an app for delivery executives (like Swiggy's), and they grilled me on user personas, what the MVP should look like, and which metrics would signal success. I then had to tackle a different scenario—building a product for startup founders—which tested whether I could adapt my framework to a completely different context. They weren't looking for a "right" answer; they were watching how I thought through trade-offs.

I also got a system design question that felt more like what I'd expect from a TPM role—designing something Swiggy or Zomato-like, with questions about APIs, load balancing, database architecture for orders, and payment integration. It was a lot of ground to cover, but it made sense for the role.

I made it all the way through and received an offer, but ultimately I decided to decline. Looking back, I think the process itself was strong—the rounds were varied, the bar was clear, and the team actually seemed invested. If I'd been more aligned on the role itself or the company at that moment, I would've said yes.