I’m an engineering leader who moves between architecture, code, customers, and teams—turning ambiguous problems into scalable, reusable systems people can understand, build, and trust.
I create clarity, coach judgment, and get my hands dirty wherever the team needs me.
A robot says, "beep boop" + "bang"
Strategic Engineering Leader | Architecture, Technical Vision & Boots-on-the-Ground Engineering · Colorado (Remote)
I stay close enough to architecture and implementation to understand the work, while creating the context and trust for other engineers to own it. I think about engineers by the leverage they create—not only by title or discipline—and build teams where those different strengths compound.
Who is the user? What are they trying to accomplish? What evidence do we have, and what are we assuming? Before code hardens an idea, I want the team to understand the architecture and constraints—or use a focused experiment when building something is the fastest way to learn.
Exceptional engineers do not all look or work alike. Some reduce ambiguity and test the art of the possible; others turn those lessons into durable, maintainable systems. My job is not to make everyone the same. It is to give those strengths room to sharpen one another.
Speed without enough understanding is false speed. Rigor that takes too long for the business to act on is not useful either. I build the context, tools, and operating mechanisms that help teams exercise good engineering judgment sooner.
My ethos is to pair servant leadership with business judgment: create the clarity and trust that let different strengths compound around work that creates value. It also means being willing to say, “I don’t know yet—let’s ask the people who can know,” then staying accountable for turning what we learn into an executable plan.
These projects began with real constraints: an unclear path, customers blocked before they could see value, or an ambitious launch without a credible delivery plan. I stayed with the problem from the first questions through architecture, delivery, validation, and learning.
Designed and implemented the AI-assisted feasibility system.
Replaced a four-to-eight-week feasibility cycle that could include an incorrect proof of concept with an architecture-first options and limitations review before implementation.
Read the case studyArchitected and built mdai-labs from start to finish.
Reduced sandbox evaluation to five minutes through a fully self-service workflow that uses synthetic data to demonstrate the efficacy of MDAI solutions.
Read the case studyHelped conceptualize Octant from the ground up.
Enabled marketing and product collaborators to modify frontend content through a JSON-driven content layer without depending on routine engineering changes.
Read the case studyThe human story matters first. These are a few of the proof points behind it—across organizational leadership, technical coaching, and systems built to hold up under pressure.
Built and ran the engineering practice from roadmap through delivery, hiring 12 engineers and three contractors while establishing Jira-grounded Monte Carlo forecasting for predictable delivery.
Go deeperThe team documented error codes and troubleshooting guidance in a customer-facing table, helping open-source users resolve known failures without first creating a support ticket.
Go deeperArchitected an elastic commerce foundation now supporting 180M+ annual orders, with follow-on systems scaling to 1.5M TPS.
Go deeperI spend my personal time with my family—a joyful, chaotic, hands-on mix of coaching, cooking, tinkering, building, and learning as we go.
Personal time is where I get to be curious for no reason other than joy: making things, teaching what I know, learning with my kids, and refusing to pretend cardio is fun.