Complexity,
made clear.

Own critical systems

I take responsibility for important systems from design through production and operations, and I stay long enough to see the results of my decisions.

Make them simpler and cheaper

I remove avoidable complexity in code and cloud infrastructure, improve performance, and make better use of the engineering budget.

Learn the business

I want to understand the product, its customers, and its economics, so that technical decisions support where the business is going.

I am a Staff Software Engineer and former Head of Engineering with 20 years of experience building and delivering software products and data platforms. My work spans SaaS, data observability, insurance, telecommunications, and e-commerce.

At Kensu, I led cloud and multi-tenant transitions, supported hiring and mentoring, and broadened ownership across engineering and operations. I reduced AWS infrastructure and operational costs by 70% and QA-reported bugs by 60%. At Crisp, I cut production incidents from about one a month to about two a year. Those incidents often meant reprocessing petabytes of data at high cloud cost and taking several engineers away from product work. I also built the semantic model registry that gives the company’s AI agents trusted, account-specific business data.

I work from system design through implementation and operations, while sharing context and building ownership within the team. My hands-on experience covers Kotlin, Scala, Python, Go, and TypeScript across AWS, GCP, and on-premises environments. I use AI extensively and with discipline: by company metrics, my productivity lift over my pre-AI baseline is 7.5×, against a 5.65× median for senior+ engineers. AI writes the code and the tests; I keep the engineering judgment: what to verify, where to look closer, and what ships.