Get in touch
Playbook
Frequent questions
Direct answers on how I lead, build, and make decisions at scale
How do you approach leading engineering in highly regulated environments?
Compliance and reliability aren’t obstacles to speed—they’re the constraints that make speed safe. I define architectural boundaries and integration contracts early so teams can iterate with autonomy instead of waiting for permission.
What does “systems over heroics” mean in practice?
It means building organizations where consistent delivery comes from foundations—automation, clear interfaces, ownership—not from individuals pulling all-nighters to save a release. Heroics don’t scale.
How has your military background shaped your engineering leadership?
It set the standard that failure has real consequences. That changes how you assess risk, build trust, and design systems. The specifics are different—platforms instead of networks—but the discipline is the same.
How do you handle architectural debt in a growing organization?
I make the business case that debt is a revenue problem, not a technical one. That reframing creates space to invest in foundations. From there, every sprint spent on stability reduces the cost of every sprint that follows.
What kind of challenges interest you most?
Regulated platforms at scale, distributed teams navigating complex governance, and organizations ready to shift from reactive delivery to resilient engineering. High stakes and real constraints—that’s where I do my best work.