Work

I've been solving problems with software, professionally, for 10+ years now. And somehow, problems keep on piling. In retrospect, my career spans four distinct phases across product engineering, developer experience, leadership, and data engineering.

Product engineering phase

Currently, I'm in my product engineering phase: joined Jam as a founding engineer, and have gone from 50K to 200K+ MAU (and over 13M total jams) that are tackling bugs more efficiently. During this time, I led foundational work on the core product — led the migration to MV3, redesigned core extension for performance and reliability that ended up driving the baseline reliability (for core product flows) up the 97%+ band, an uptick of over 5x of initial baseline. Currently working on new things.

DevEx phase

Before that, I had a DevEx phase at Microsoft. I was a core contributor to an esbuild fork that reduced inner-loop build times by 97% (from 10+ min to <30s) for an org of 500+ engineers, plus a ~100x speed-up for all esbuild users running large monorepo graphs. Landed dozens of high-impact client-side performance fixes as part of a high-stakes org goal, alongside the Edge team. I also served as the technical lead on behalf of Outlook Web in a cross-organization initiative, integrating 3rd-party apps into Outlook Web.

Bootstrapping phase

In a past life, I had my CTO phase: grew a 20-person engineering team at an emerging consulting firm, closed the first $100K deals, and wrote an opinionated batteries-included framework to streamline server-side development.

Data engineering phase

Before that, in my data engineering phase, I built way too many offline and online data pipelines for high-stakes operations in finance[✶][✶] and telco[✶].