Strategic Technology Leader
I help mission-driven organizations close the gap between what gets built and how it gets delivered — translating engineering reality into programs that get funded, governed, and actually work.
Strategic technology leader. Two decades turning mission-critical intent into delivered systems — across defense, national security, and government technology.
Track record
- $19M+
- Documented savings
- 45%
- Efficiency gains
- 160+
- Staff trained
- 100%
- FISMA compliance
FAC-P/PM · Defense Acquisition Corps · 20+ years federal service
Where I operate
Engineering fluency
I can evaluate architecture, delivery, and code quality on the merits, not from a status slide. That comes from years of actually building and reviewing systems, including the safety-critical kind. It means I understand the tradeoffs a team is really facing, and I can tell a genuinely hard problem from an excuse.
Acquisition & program execution
I translate a real need into a program that can be funded, governed, and defended, then drive it through to something delivered. I know how statements of work, contract structure, and the federal acquisition machinery quietly decide whether good technology ever ships. Most of my work is making that machinery serve the mission instead of grinding against it.
Mission assurance under stakes
I've led software quality and mission assurance in environments where the cost of a defect is measured in more than a ticket: defense, national security, and other settings where the system has to work the first time. That experience shapes how I judge risk and what I'm willing to call finished. The standard doesn't relax when the stakes do.
Latest writing
The translator problem
Technical teams and program teams rarely fail because someone is wrong. They fail because no one owns the space between them. On the rarest and most underrated role in any serious program.
Most government software fails at the SOW, not the standup
The decisive failures in government software happen in the contract language, months before any team writes code. Where it goes wrong, and what good acquisition actually looks like.