Engineering, leadership, and building things that matter.

I started in software because I wanted to understand how things work, and then to build them. Over time, the interesting problems moved outward: from a function, to a system, to a team, to an organization, to the question of whether what we were building mattered at all.

That progression took me from hands-on engineering and architecture into engineering management and CTO-level technology leadership, in international environments and across complex products. It did not make me less technical. It made me more careful about which technical decisions deserve attention.

I believe great engineering leadership sits at the intersection of four disciplines: people, technology, product, and delivery. I care about developing engineers and future leaders, designing architectures that keep options open, and making sure engineering effort turns into outcomes people actually value.

I also keep building. Working on my own product keeps me close to modern software engineering, AI, and the commercial reality of shipping something people pay for.