Measure first. Ship the smallest thing that moves the number. Prove it moved.

I'm a senior software engineer with seven years of building web applications that people use to do their jobs — not demos. Most of that time has been spent somewhere in the TypeScript, React, Next.js and Node stack, with enough time on the backend and infrastructure side that I'm comfortable owning a feature from the database schema to the focus ring.

I started at Paytm Payments Bank, building internal tools for around 1,500 branch staff working on networks that made every kilobyte count. That's where I learned that performance is a user-facing feature and that data integrity bugs are the ones that cost you sleep. At Jio I moved between a React front end, a Node BFF and Python services on Azure, and spent a lot of time on the seams between them — including a long hunt for intermittent 504s that ended with correlation IDs and keep-alive tuning.

At Trajector I architected a Message Center that unified communications across three portals and three lines of business on a shared database. It now carries around 10,000 messages a day for roughly 6,000 daily users and has taken about a thousand support hours a month out of phone and email queues. It's the piece of work I'd most want to be asked about.

Right now I'm building in the direction I find most interesting: retrieval systems and event-driven backends. That means a RAG stack on Postgres and pgvector, and a chat service modelled twice — once through a RabbitMQ broker and once as a gRPC contract — to understand the tradeoff properly rather than from a blog post.

I keep a rule for my own résumé: if an interviewer could corner me on a line in two minutes, either I build it this week or I cut it today. The same rule applies to this site.