About

I’m Shambhu, a software engineer who kept wandering out of the codebase. I started on the backend — APIs, databases, system design — and found I cared just as much about the question that comes before any of it: should we build this at all, and why does it matter to the business?

So I started owning that question. On the products I work on, I’m the person shaping what we build and what we deliberately don’t — running the discovery, making the calls on scope and tradeoffs — and then building a good part of it myself. That combination is the whole point of this site: I can go from a business problem down to the API, and back up, without losing anything in translation.

How I think

Most bad products solve the wrong problem well. I’d rather spend a day understanding the real problem than a week building the wrong solution beautifully. Being able to build quickly is exactly what lets me say no to building the wrong thing — the cost of a feature is clearest to the person who has to ship and maintain it.

How I work

I like small teams, tight feedback loops, and decisions written down. I’m comfortable in the ambiguous early part — talking to users, framing the problem, arguing about priorities — and comfortable in the part where someone has to make it real. I try to leave both the product and the people around it a little clearer than I found them.

Where I’m headed

I want to own products end-to-end and build things people rely on. Right now that means product engineering and product ownership; over time it means building companies. This site is where that work will live.

If you’re hiring for product, building something early, or just want to compare notes —let’s talk.