Origin
Discipline isn’t inherited. It’s operational.
Sixteen years of Special Forces communications, crisis infrastructure, and operational leadership built the instincts I lead with today. This isn’t background—it’s the operating system beneath every platform decision, team structure, and architecture trade-off I make.
Formation
Where it comes from
The environments changed—classified networks, humanitarian crises, air assault operations, personal reckoning—but the pattern held: build what doesn’t break, lead through ambiguity, and treat every system as load-bearing. These are the eras that shaped it.
Formation
Where it comes from
The environments changed—classified networks, humanitarian crises, air assault operations, personal reckoning—but the pattern held: build what doesn’t break, lead through ambiguity, and treat every system as load-bearing. These are the eras that shaped it.
Formation
Where it comes from
The environments changed—classified networks, humanitarian crises, air assault operations, personal reckoning—but the pattern held: build what doesn’t break, lead through ambiguity, and treat every system as load-bearing. These are the eras that shaped it.
Curious how this translates?
Sixteen years of building systems where failure wasn’t an option—now applied to enterprise platform engineering.









Curious how this translates?
Sixteen years of building systems where failure wasn’t an option—now applied to enterprise platform engineering.









Curious how this translates?
Sixteen years of building systems where failure wasn’t an option—now applied to enterprise platform engineering.












