Interview process
The interview process was conversational but still quite rigorous. The interviewer spent time understanding my background, especially my experience in B2B SaaS, healthcare AI, workflow products, and distributed deployments. What went well was that I got to explain complex product work in depth, especially around AI-enabled clinical workflows, modular deployments across multiple countries, and how AI findings translate into real operational action. What could have gone better was that some of my answers were initially a little broad. The interviewer probed deeply, so I had to tighten my responses and make the product ownership, trade-offs, and metrics clearer. Overall, it felt like a strong product-thinking conversation rather than a standard resume walkthrough.
- Recruiter screen
- Technical interview
Interview rounds
5 questions across 2 roundsRecruiter screen
2 questionsSpecific questions asked
Work Experience and why and how you built?
Technical interview
3 questionsQuestion types asked
Specific questions asked
Estimate the number of API calls done by a user facing app if Qure.ai makes one?
Why Blinkit?
Interview tips
I would tell them to prepare 2–3 deep product stories from their experience, not just surface-level achievements. For each story, they should be clear on the problem statement, users, business context, product decisions, trade-offs, metrics, and what they personally owned. They should also prepare for open-ended product thinking questions, guesstimates, RCA, metrics, and B2C product sense. For Blinkit specifically, it is important to think beyond “10-minute delivery” and understand the larger system: inventory, availability, replenishment, dark stores, riders, substitutions, customer trust, and unit economics.
Company culture
It is actually a pretty close team with people having great learning. Everyone owns a couple of problem statements and work on them.
Get full access with a membership, or share your experience to try it free.
More Zomato interview experiences

“Interviewer was nice. He was kind off to help and explain all clarifying questions. What went well : - indentifying stakeholder What didn't well : -> end user experience could have been explained more clearly”

“Discussions about frontend fundamentals and my work experience went well. I was supposed to code the solution within 10 minutes after I had thought through the approach, but I took longer because I was supposed to solve the question in JS, while I primarily solve DSA questions in C++. ”