Product engineer. Independent builder.

Ideas are easy. Making them survive reality is the fun part.

I'm an Android Developer at PhonePe and a builder at heart. I care about products that work when users are impatient and the real world refuses to behave like a neat mockup.

Pocket OS

Tap, explore, move fast

Now

Building Restro AI

The current idea I keep returning to: restaurant software that helps teams think ahead.

Mode

Product-first Android

Small screens, high intent, calm interactions, and no wasted taps.

Signal

Messy products welcome

I like products that have real users, pressure, edge cases, and business reality baked in.

Currently building

A small window into what I keep thinking about while building.

Half-formed thoughts, product beliefs, experiments, and the kind of notes that usually start in too many open tabs.

Now

Building Restro AI

The current idea I keep returning to: restaurant software that helps teams think ahead.

Mode

Product-first Android

Small screens, high intent, calm interactions, and no wasted taps.

Signal

Messy products welcome

I like products that have real users, pressure, edge cases, and business reality baked in.

Experience journey

Not just where I worked. What those places trained me to understand.

Each environment taught a different kind of building: trust, clarity, ownership, ambiguity, and the boring business details that decide whether products actually work.

Chapter 01

Early chapter / Startup operations and marketplace work

Phool.co

The non-code parts of a startup still move the company.

At Phool, I was not there as an engineer. That was the point. I worked closer to marketing, operations, listings, and marketplaces. It gave me a useful respect for the non-code parts of a startup.

Supply
Demand
Timing

Worked across product listings, marketplaces, and high-demand festive sales pressure

Understood how Amazon, Blinkit, Flipkart, and Myntra visibility affects real business outcomes

Built hunger for startup work by doing the unglamorous things that still move the company

Chapter 02

Fintech chapter / Android product engineering

Fi

Good fintech products reduce anxiety instead of adding more screens.

Fi showed me how much product quality comes from taste and focus. I worked close to founder-level priorities on Wealth Builder, a feature built to create traction and make investing feel less intimidating.

Worked on one of the most important marketing and traction-building product bets

Built Android features around wealth, AI-assisted experiences, and consumer clarity

Learned how good fintech products reduce anxiety instead of adding more screens

Chapter 03

Founding chapter / Founding mobile engineer

Ownly / Rapido

Real teams do not wait for perfect timing.

Ownly was raw startup energy. I joined as a founding mobile engineer, took responsibility across surfaces, and learned how to ship when the product, team, and assumptions are all moving at once.

Helped build Android, iOS, and web foundations using Kotlin Multiplatform and Compose Multiplatform

Designed and shipped a full restaurant POS in 20 days, which went live and processed real orders in its first month

Took ownership beyond my lane and learned how fast reality exposes weak product assumptions

Chapter 04

Current chapter / Android Engineer

PhonePe

Money movement teaches product judgment quickly.

PhonePe taught me how serious product work feels when money is involved. I work in a fast-moving, high-ownership pod around DigiMetal, where reliability and speed both matter.

Shipped DigiGold and DigiSilver features for 700M+ registered PhonePe users across India

Built across DigiGold and DigiSilver journeys where trust, clarity, and edge cases matter

Took ownership of flows that needed product judgment, debugging depth, and calm execution

Restro AI

Restro AI is an idea I keep coming back to.

Restaurants already have software. Most of it still does not help them think ahead. The idea is simple: give restaurant teams a calm operating layer that can read demand, inventory, staffing, and waste before the day gets away from them. I want it to feel less like another dashboard and more like a second brain for the person running the floor.

Restaurant intelligence

Tomorrow's rush preview

Currently in early access with 20+ restaurants on the waitlist.

7:40 PM

Projected dinner rush

-23%

Waste risk

Demand curve

sample

AI note

Prep 14% more paneer before 7:30 PM

Signature projects

Some of my favorite projects started as random late-night ideas.

The good ones survive outside demo videos. I care about what made the product difficult, what the system had to handle, and whether the experience felt useful when it left the prototype.

Restaurant intelligence

Restro AI

Restaurant events

Orders, inventory, staff, waste

Signal layer

Clean, normalize, detect patterns

AI planner

Forecast and recommend actions

Operator UI

Calm decisions before rush hour

Product

The idea is simple: give restaurant teams a calm operating layer that can read demand, inventory, staffing, and waste before the day gets away from them.

Engineering

The product should feel less like another dashboard and more like a second brain for the person running the floor.

Hard part

A restaurant tool has to respect rush hour. It cannot make operators parse complexity when the floor is already moving.

Impact

A current build shaped by restaurant workflows, operational pressure, and product empathy.

Next.jsAI systemsForecasting UXDashboards
Product philosophy

I care a lot about products feeling alive.

Not loud. Not overdesigned. Just useful, quick, thoughtful, and a little memorable. I like building with people who care about the same details users may never name but always feel.

01

Product before polish

I like polish, but only after the core problem is honest. Pretty screens do not save confused products.

02

Speed with taste

I enjoy moving fast. I care even more about whether the thing feels thoughtful when someone finally uses it.

03

Calm beats clever

The best products usually feel obvious after someone else has done the hard thinking.

04

Build past the demo

Some of my favorite projects started as random late-night ideas. The good ones survive outside demo videos.

Android

Kotlin, Compose, lifecycle, performance

AI UX

Agents, orchestration, recommendation surfaces

Product Systems

Flows, metrics, trust, feedback loops

Web Apps

Next.js, TypeScript, responsive interfaces

Data Products

Dashboards, forecasting, operational signals

Reliability

Edge cases, recovery, calm failure states

Let's build

If you are building something interesting, I would probably like to hear about it.

Especially if it needs someone who can think through product, write the code, notice the details, and still keep the room calm when things get messy.