Security operations is one of the hardest product spaces to work in: high stakes, high noise, and users who are too busy to tolerate anything that slows them down. I worked on the products that sit at the centre of that workflow, from how alerts are generated and triaged to how investigations are run and communicated. Part of the challenge was that the team I was building for was also the team I was embedded with, which meant the gap between what we were building and whether it actually worked closed very quickly.

Incident response is one of those services where the product and the delivery are inseparable. The tools analysts use during an active incident shape the quality of the response, the speed of containment, and what the customer experiences. Building the product layer for an IR service means thinking about tooling, workflow, and communication simultaneously. That combination is more interesting to me than most pure product work.

The interesting question in enterprise security right now is not "can we ingest more data?" but "can we make the data we already have actually useful to the person staring at it at 2am?" I spent time working on that question at the platform level: what does a security operations platform look like when it is built around the analyst workflow rather than around the data pipeline? That meant working across detection, investigation, and response as a connected system, not as separate features.

Most security products are built for the security team at a large enterprise. Logpoint was building for the security team at a company that could not afford a large enterprise security stack. That constraint makes every product decision harder and more interesting. I worked across SIEM, endpoint detection, and anomaly detection, which gave me a view of how these capabilities need to connect to actually reduce work for an analyst rather than add to it.

Before product management was my job title, I started a company in Nepal to bring digital infrastructure to schools in areas that did not have it. The work was equal parts operations, fundraising, community negotiation, and improvised engineering. It did not end the way I hoped, but it taught me more about what it actually takes to ship something useful to people with real constraints than anything I have done since.

A stock portfolio tracker I built to manage investments across multiple brokers in one place. Pulls live data from broker APIs, stores daily snapshots, and has an AI layer that analyses each position and lets me chat with my portfolio. Built on Cloudflare Workers, KV, and Workers AI.

A travel diary I keep with my wife. We move around a lot and eat well — this is where that goes. Part journal, part food log, part archive of places we have been. Still being built.

This site. Built with Astro, deployed on Cloudflare Workers. Content is plain Markdown files — drop a file in, it appears on the blog. The design is meant to feel calm and considered rather than polished.