Riya Sen

Associate Product Manager at DabbaDash | Food delivery, fewer confusing buttons, occasional open-mic damage

I’m an associate product manager at DabbaDash, working on the bits between “I’m hungry” and an order actually arriving. I moved from Kolkata to Bengaluru in 2025 and have since developed strong opinions about delivery instructions, secondhand jackets, and what qualifies as a kathi roll. My work involves customer interviews, funnel analysis, and asking whether a feature needs to exist before we give it three screens. Outside work, I test jokes at open mics and watch K-dramas with the completely false confidence that I’ll stop after one episode.

Working on checkout and post-order support for a fictional food-delivery platform. Partner with design, engineering, and operations to investigate abandoned orders, improve delivery-instruction flows, and test clearer status messages. Moved to Bengaluru for this role.

Based in Kolkata, analysed ordering behaviour for a neighbourhood meal-subscription startup. Built SQL dashboards, tagged customer-support themes, and helped evaluate changes to menu discovery and repeat ordering.

Product discovery, SQL, Funnel analysis, Customer interviews, A/B testing, Product analytics, Requirements writing, Cross-functional collaboration, User journey mapping

English, Bengali, Hindi

Watched a customer type “please call, bell doesn't work” into delivery instructions, then hesitate because they weren't sure anyone would see it. Tiny moment. Very useful interview. We've been looking at how those instructions travel through the order journey, not just whether the text box exists. A field can technically work and still fail the person using it. My contribution to the discussion was a flow diagram. My contribution to lunch was ordering to the wrong office entrance. Staying close to the problem, apparently.

One year in Bengaluru, one year as an APM, and I have finally stopped saying “quick question” before asking something with six dependencies. The biggest change in how I work: I write down what would make us NOT build something before getting attached to the idea. Support conversations and boring little funnels have saved me from several very attractive bad ideas. Outside work, open mics are teaching me a related lesson: silence is feedback. Unfortunately, it does not come with a dashboard.

Did a five-minute open-mic set this week and spent the next morning reviewing a checkout experiment. Both involved discovering that the thing I thought was obvious was, in fact, not obvious. In comedy, I can rewrite the setup. At work, we're checking where people lose context before the payment step instead of immediately adding more explanatory copy. Trying to get better at separating “they didn't understand this” from “I didn't explain this well.” Less glamorous than shipping. Usually more useful.