About

Most engineering organizations have the same problem. They have talented people doing good work, but the work doesn't connect to outcomes. Features ship. Metrics don't move. Strategy lives in a slide deck nobody references after Q1 planning.

I build the operational systems that fix this. I connect short-term execution to mid-term OKRs to long-term strategy so that teams know why they're building what they're building. I design AI-enabled workflows that eliminate coordination overhead. I create the operating rhythms, decision frameworks, and feedback loops that let engineering leaders focus on strategy instead of status updates.

The goal is simple: make the organization a force multiplier for every engineer in it. Give people clarity, remove friction, measure what matters.

I stay technical because it makes me better at operational design. When you understand the friction of building something, you make better decisions about how to organize the work around it.

My background spans modernization in regulated industries. Wealth management, specialty pharmacy. I've taken rigid legacy systems and rebuilt them into scalable, cloud-native architectures. I've designed event-driven data pipelines, built AI-powered meeting workflows with Claude Code and MCP integrations, and shipped native iOS apps.

I'm pursuing an MBA at Saint Joseph's University while taking courses in OKR frameworks, system design, and GIS. Learning is a professional practice, not a phase you grow out of.

A junior developer deleted our entire production site from Azure. The whole thing. Gone.

We had SEC regulations requiring a live site with investor information. We had backups, but they weren't stored optimally for quick restoration. The team was panicking.

I coordinated the restoration, kept the team focused, and we got the site back up. But the real work started after. We ran post-incident exercises, built guardrails to prevent it from happening again, and redesigned our backup system. We went from hours to minutes for full application restoration.

Good operational systems don't prevent every problem. They determine how fast you recover and whether you learn from it.

The screen is not the real world. Clarity comes from stepping away.

You can usually find me fly fishing for trout in Pennsylvania streams or training with sandbags, kettlebells, and rope flow. Fly fishing teaches patience with complex systems. You observe, adapt, and refine. Physical training is how I reset. Both translate directly to handling pressure and solving hard problems.

I started my career in the Marine Corps as an Ammunition Technician. That experience taught me how to operate in high-pressure environments, communicate with clarity, and build trust with teams. It gave me a bias toward action, structure, and accountability that still shapes how I work.

But it doesn't define what I build. What defines my work is a belief that engineering organizations can be dramatically better with the right systems in place. Not more process. Better process. Outcome-focused strategy, AI-assisted workflows, and data-backed decision making.