About Me.

Now

I'm a Lead Frontend Engineer at Razorpay, where I look after the platform side of the dashboard's frontend. Most of what I do sits underneath what anyone actually sees: the build pipeline, CI, and the architecture that keeps a large frontend quick to ship. Developer experience is the part of the product I care about most.

Platform and build

In practice that means microfrontends over module federation, keeping Webpack and SWC builds honest, and scaling our GitHub Actions setup so CI does not slow down as the codebase grows. A lot of my time goes into the unglamorous numbers, load times, build cycles, deployment delays, because those are the ones every engineer on the team feels every day. I work across Node and Express wherever the frontend has to meet infrastructure.

Scale and system design

The part I enjoy most sits lower down: system design, and the architectural calls that decide whether something holds up once it grows. I would rather spend the time getting the shape of a system right than patch around one that was never built to scale, and that tends to mean thinking about the low-level pieces well before most of the code exists.

Agentic systems

More recently I have been building agentic systems: harnesses, agents built on Claude Code, knowledge bases wired into our infra layers, and Playwright integrations that let those agents run end to end. Some of that has turned into what we call the ADLC, an agentic development lifecycle, which is roughly where I think SDLC is heading. It is the most interesting problem space I have worked in.

Away from the terminal

I draw, play piano, and keep a few side projects running, usually React Native apps, AI integrations, or a bit of system design I want to understand properly. I like mentoring too. Teams get better when people talk openly and keep learning, and I would rather help someone level up than sit on what I know.