The story so far
4+ years. Multiple industries. Systems used by tens of millions of people. Here's how I got here.
While most of my classmates were still doing assignments, I was already deep in real client work — building a restaurant management system during my third year of engineering. It was messy, challenging, and exactly what I needed. That early experience taught me something most developers learn years later: real systems have real edge cases, and the only way to get good at building them is to build them.
I started my career as a MEAN stack developer and moved fast. Within a couple of years I became the product owner for a food delivery SaaS — a white-label platform that multiple businesses ran their operations on. I was the one managing the roadmap, shipping new features, and sitting on architecture calls with clients across the world. It wasn't just code. It was ownership. That shift — from writing features to being responsible for a product — changed how I think about software permanently.
When the blockchain wave hit, my organisation leaned into it and so did I. I got involved in case studies, architecture explorations, and ended up building both a decentralised exchange and a centralised exchange. It was a different class of engineering problems — consensus, on-chain logic, trust without intermediaries. I came out of it with a much deeper appreciation for distributed systems and what it takes to build software where the stakes of getting it wrong are very high.
When AI started moving fast, I moved with it. I joined a firm focused on AI and public sector work. My first project was enterprise document search — a real problem: organisations sitting on hundreds of thousands of documents with no good way to find what they needed. We started with basic context matching, evolved it into semantic search with document summaries, and it has now grown into a full platform with team workspaces and AI agents. Watching a product mature from a rough idea into something people actually depend on — that never gets old.
The project that put scale into perspective for me was a public sector fuel pricing platform. Fuel stations across the country submit updated prices to a central portal. Citizens use it to find the cheapest fuel nearby. We built that system. Today it serves 69.9 million citizens. There is no staging environment that prepares you for that. You either build it right or you find out at the worst possible time. We built it right.
I organise GDG Rajkot — a Google Developer Group with 900+ active members. We run bi-monthly events covering everything from AI and cloud to open source and career growth. In the last year alone, we've served 2,500+ participants across our events.
Organising a community has made me a better developer. You learn fast when you have to explain things clearly, invite the right speakers, and build something people keep coming back to. The teaching sharpens the thinking.
I'm an outdoors person at heart. On weekends you'll find me on a bike ride into the hills — no destination, just roads and open sky. Exploring new places resets something in me that no amount of coffee or focus music can.
I also love gaming with friends — the kind that requires actual coordination and ends in someone blaming the lag. And I'm quietly obsessed with analogue and automatic watches — the engineering in a mechanical movement is its own kind of beautiful.
What this means for your project
Years of owning a product means I look at every feature through the lens of what it's actually for — not just whether it works.
From high-traffic SaaS to systems serving tens of millions of people. I know what decisions come back to haunt you and which ones are fine to defer.
I use AI to move faster on real problems — not to look current. Every engagement I take on benefits from that directly.
Book a free 30-minute call. No pitch, no pressure — just a conversation about what you're building.
Book a Free CallView ServicesRead the Blog