I build the systems that turn technical possibility into customer adoption.

My background

At Twilio, I grew from the founding engineer of a developer content function into a Director leading a 10-person organization. My work spanned the Developer Blog, Developer Hub, Code Exchange, and the experiences connecting product discovery to implementation.

I helped grow Developer Blog organic views by approximately 900% within my first 18 months. As a Director, my organization’s work contributed to 20% year-over-year growth in developer signups through organic discovery and education.

Before Twilio, I engineered enterprise platforms for clients including Microsoft, Campbell’s, and H-E-B, with migrations involving more than a million posts and digital assets. That engineering foundation still shapes how I lead: I can set the strategy, work through the technical decisions, and build alongside the team.

How I work

I start by finding where people get stuck. What are they trying to accomplish? What do they need to understand? What makes the next step harder than it should be?

Then I bring together the people, product experiences, and technical resources needed to improve that journey. That has meant revitalizing developer properties slated for retirement, redesigning how customers discover working code, and prototyping ways to experience APIs before creating an account.

I define success early and connect the work to measurable behavior: discovery, signups, activation, and continued use.

What I care about

I care about making technology useful to the people it is supposed to serve. Clear explanations matter. So do working examples, thoughtful interfaces, and teams that follow through after launch.

The goal is to help people make progress, then build the systems that make that progress repeatable.