Engineer by training, builder by temperament.

I'm an engineer by training and a builder by temperament. I studied computer science at IIT Bombay, and since then I've mostly worked on the parts of software that nobody notices until they break: data pipelines, payment reconciliation, payroll, notification systems.

Most recently that was at Meta, on the reliability and data quality of a pipeline handling millions of records. Before that I was at Rippling and Fincent, where the systems moved money, and where "mostly correct" was not a state anyone would accept.

What I care about

Systems that hold. I like the unglamorous work of making something dependable: defining what "working" means, measuring it, and finding out it's broken before a user does.

Building to learn. I spent six months as an Entrepreneur in Residence at Entrepreneur First, testing ideas against real customers and discarding most of them. It rewired how I think about what's worth building. The fastest way to learn whether an idea is good is usually to put a small, real version of it in front of someone.

The business underneath. I'm as curious about why a company works as how its software does: business models, incentives, where the margin comes from, and what makes something worth investing in.

AI, practically. Less the discourse, more the question of what these tools change about how one person can build.

Why this site

I didn't want a portfolio that I'd update once every job search. This is a working headquarters: finished things live in work and build, unfinished thinking lives in think, and the things I try, including the ones that fail, are logged in explore. The now page says what currently has my attention.

If something here is useful to you, or wrong, tell me.