I'm a senior engineering manager who has spent the last nine years obsessed with one problem: how do you make engineering teams ship better software, faster?

I started in defense manufacturing at General Dynamics, where software ships on physical hardware and a defect downstream can cost millions. I built CI/CD pipelines, scaled a DoD software factory on AWS and Kubernetes, and learned to coordinate teams of teams against large-scale delivery plans. Then I moved to PHIL, where I built an automated environment factory, redesigned change management around GitOps and ArgoCD, and took the team to hundreds of deployments per day.

That background is why my work in agentic systems looks different from most. I didn't pivot to AI — I applied the same engineering discipline to a new set of tools. I designed structured experiments, defined a measurement framework that prioritizes quality, then speed, then cost — in that order — and built a production agentic SDLC that changed how my team ships software.


I work hands-on with engineering teams navigating AI adoption. Not advice from the outside — I do this work daily and can help you skip the expensive mistakes.


AI Adoption Strategy

I help you find the high-leverage AI opportunities hiding in your existing workflows — not the ones that look good in a deck, the ones your team can actually ship. You get a roadmap grounded in your engineering maturity, not a wishlist.

Agentic System Design

I've built production agentic SDLCs from scratch. I can help you design yours — from agent architecture and tool-use patterns to the evaluation framework that tells you whether it's actually working.

Engineering Team Enablement

I embed with your team to build the internal capability that outlasts my engagement. Developer tooling, agentic workflows, measurement strategy, and the shipping culture that ties it all together.

Let's talk →