Guardrails and permissions
Policies, scoped credentials and approval gates so AI tools can only reach what they should, with every action logged.
I lead the infrastructure, the team and the process that keep systems up.
Over a decade in infrastructure, from racking servers on a datacenter floor to leading IT and systems infrastructure. I turn one-off systems into a uniform, documented, automated platform that a team can run with confidence.
I started on the datacenter floor, racking servers and cabling networks, then spent years as a Linux systems administrator keeping production running. Today I lead IT and systems infrastructure: the systems themselves, the people who run them, and the process that keeps them predictable.
The work I enjoy most is turning a collection of one-of-a-kind systems into a uniform platform. That means configuration management instead of hand edits, monitoring that catches problems first, and documentation good enough that anyone on the team can pick up a task.
I still stay close to the technology. The hardest network and OS problems tend to land on my desk, and I like it that way. I believe problems should be raised early and in the open, and that a reliable system is a well-understood one.
Owning technology decisions end to end: what to build next, what it costs, and who we partner with.
Monitoring, configuration management and documented process across hundreds of systems, with less tech debt every quarter.
Meeting SOC 2 and PCI requirements and hardening internal and public-facing systems, with EDR and vulnerability scanning for detection and remediation.
Hiring and leading an infrastructure team, training staff on Linux and networking, and presenting to customers.
Software and infrastructure follow the same workflow. Servers, network config and deployments live in Git, so every change is reviewed, tested, repeatable and easy to roll back.
Code, configs and playbooks in Git. No hand edits on servers.
Merge requests with peer review and AI-assisted adversarial review.
CI/CD runs linting, tests and security checks on every change.
Ansible applies the same result every time, in stages.
Monitoring confirms health, and rollback is one revert away.
I bring AI into infrastructure work the same way I bring in any system: scoped access, clear rules and a review step before anything reaches production.
Policies, scoped credentials and approval gates so AI tools can only reach what they should, with every action logged.
Packaging team runbooks and standards as reusable agent skills, so AI follows the way we already work.
Using AI as an adversarial code reviewer and to probe our own systems, finding weaknesses before anyone else does.
Connecting systems through their APIs, and building and hosting MCP servers that give AI tools safe, scoped access to internal data.
Eagle Scout. Led 40 scouts through a 200+ hour service project for a public school, and ran weekly meetings for 60+ scouts as Senior Patrol Leader. It is where I learned to plan, delegate and follow through.
Open to conversations about infrastructure leadership, reliability and building calm, well-run IT.