Skills & Expertise
What I solve, how I think, and the tools I reach for.
What I Do
Keeping Global Operations Running
When you're responsible for 700+ locations across 100+ countries, the job isn't knowing how servers work — it's knowing which decisions keep 12,000 endpoints running at 99.98% uptime and which ones cost you a weekend. I've spent nearly three decades learning the difference.
I've managed a 2,000-server data center, led global platform migrations, and made the infrastructure decisions that kept a worldwide testing operation running through every crisis, upgrade cycle, and M&A integration that came along.
Tools that got it done: Windows Server, Azure hybrid cloud, Hyper-V, Citrix, HP OpenView, SiteScope
Modernizing Platforms Without Breaking the Business
Legacy systems don't retire themselves, and "just migrate everything" isn't a strategy. The real skill is knowing what to retire, what to keep, and how to sequence a multi-year transition without disrupting the operation that's paying the bills.
I led a $10M+ platform investment that retired aging Citrix VDI, Windows Server 2008, and Windows 7 infrastructure in favor of a hybrid Azure platform — while the business kept running. The result was a 30% reduction in support volume and a fleet that could actually be managed at scale.
Tools that got it done: Azure, Windows 10/11, SCCM, Intune, Citrix (decommission)
Making Security Part of the Architecture
Security reviews shouldn't be the part where someone tells you everything you built is wrong. I work security into the architecture from the start — whether that's replacing insecure HTTP function keys with Azure Event Hub SAS-based ingestion at enterprise scale, or implementing CSP headers and timing-safe authentication in an open-source project.
I've collaborated on cybersecurity audits, hardened production systems, and made compliance-driven platform decisions where the security choice and the business choice were the same thing.
Tools that got it done: Azure Event Hub, CSP headers, SRI hashes, rate limiting, input validation, API authentication
Eliminating Work That Shouldn't Exist
The best automation isn't about the pipeline — it's about looking at a process where your team flies to 150 sites a year and asking "why?" I've re-engineered field deployment processes, built CI/CD pipelines, and replaced manual workflows with systems that let distributed teams move faster without adding headcount.
The pattern is always the same: find the manual work that's eating time, figure out what it would take to eliminate it, and build the system that does.
Tools that got it done: GitHub Actions, Jest, rsync, systemd, global ticketing systems
Building Teams That Deliver Across Borders
Technology decisions are only as good as the teams executing them. I've built and led technical teams across six countries, selected and stood up a 60-person nearshore deployment team in Costa Rica, and managed the vendor relationships and budgets that kept everything funded and accountable.
The hardest part of global operations isn't the technology — it's getting people in different time zones, languages, and cultures aligned on the same priorities and delivering against the same standards.
Tools that got it done: leadership, vendor management, budget management ($10M+ platform investments), executive reporting
Building Software That Solves Operational Problems
I'm not a software engineer by training — I'm an operations leader who started building the tools I wished I had. Using AI-assisted development, I've built production-grade applications that solve real problems I've lived with for decades. Every commit carries a Co-Authored-By trailer identifying the AI tool used. Full transparency in a new way of working.
The value isn't the code. It's knowing what to build because you've spent 29 years on the receiving end of tools that didn't quite solve the problem.
Tools that got it done: Node.js, Express, Bootstrap 5, MariaDB, Claude Code, GitHub Copilot, Gemini, Warp.dev
How I Work
I work the way I'd want someone to work alongside me: practical, documented, and focused on outcomes.
Understand First
I don't start building until I understand the environment, the constraints, and what "done" actually looks like. Assumptions are expensive.
Document Everything
If it's not documented, it didn't happen. Clear runbooks, decision records, and setup guides every time.
Build to Last
No clever hacks. No fragile workarounds. Build it so the person maintaining it at 2 AM doesn't have to call you.
Iterate and Ship
Working software beats perfect plans. Ship something real, get feedback from actual users, and improve from there.
Tools I Use
Technologies shift with the project. These are my defaults.
Infrastructure
Azure Windows Server Hyper-V Docker TailscaleDevelopment
Node.js Express JavaScript Bootstrap MariaDBDevOps
GitHub Actions systemd rsync Linux cPanelAI Tools
Claude Code GitHub Copilot Gemini Warp.devSee It in Action
These skills come to life in the projects I'm building. Take a look.
View Projects Send a Message