About

I keep enterprise infrastructure running, and I build my own to understand it deeper.

By day I own a multi-region, multi-redundant enterprise output platform on Azure for a large global organization. It serves thousands of devices and users across four global regions, with geo-routing that sends each user to the closest region and redundancy at every layer so a regional problem doesn't take the business down. I'm the single global escalation point for the platform.

I helped migrate it from on-premises into Azure, and I've done the network and firewall work behind it, including catching a configuration issue that could have caused wide-reaching outages under real load. I also push past day-to-day operations: I made the business case to leadership for a non-production environment that mirrors production across regions, so changes get tested before they ever touch anything real. They approved it and we built it.

The results I care about are the measurable ones. I cut platform-related support ticket volume 38% year over year by stabilizing the operating model. The account's annual customer survey came back top-tier with my name on it, and I contributed to a five-year renewal. I've grown from field technical support to global platform owner over six years.

Off the clock, I run the patterns myself. My homelab started as a way to watch movies and turned into a 9-node Kubernetes cluster on Talos Linux, managed with ArgoCD, running around 38 services under GitOps. Control plane, GPU scheduling, storage, networking, CI/CD, the security scanning that yells at me when I commit something dumb. When I wanted DNS to stop being a manual chore, I wrote a Go tool for it and shipped it as open source.

How I work

I direct AI agents to implement, and I own the engineering. Architecture, standards, integration, the decision to throw out a solution and start over, that's me. The model types faster than I do; it doesn't decide anything. This isn't vibe coding. I reject a lot of what gets generated, and everything ships through linting, tests, and review before it's real.

If the AI went away I'd be slower, not stuck. I've contributed features to projects like OPNsense in a language I didn't know when I started, which is the part most people skip: you still have to understand the system to direct the work well.

I care more about whether something works at 2am than whether it looks clever in a slide. I'd rather tell you what I've actually validated than pretend I'm certain about something I haven't.

Skills

Microsoft AzureAzure Front DoorApplication GatewayLoad BalancingCloud MigrationKubernetesGoDockerGitOpsArgoCDTerraform / OpenTofuAnsibleCI/CDTalos LinuxInfrastructure as CodeNetwork SecurityLinux

Recognition

If you're building infrastructure and you want someone who can learn a new stack fast and move quickly without shipping garbage,let's talk.