Staff Cloud Engineer.
Nine years building and running Azure infrastructure at scale. Most of my work is the unglamorous kind that shows up on a bill: right-sizing what is oversized, replacing pipelines nobody wants to touch, and making platform migrations happen without anyone noticing they happened.
There is deliberately no contact method on this page. Your resume lists a personal phone number and a Gmail address, and neither belongs on a public page unless you decide it does. Tell me how you want to be reached, whether that is an address on this domain, a LinkedIn link, a GitHub link, or nothing at all, and I will add it.
Everything else here comes from your resume. Read it over and tell me what to cut or reword.
Annual Azure savings, a 46% reduction across the resources involved, from right-sizing SQL Elastic Pools, consolidating AI Search from 6 SU to 1, and lifecycle policies over 9 TB.
Cut in Kubernetes CPU requests across 20 AKS workloads, driven by 30 days of Prometheus data, with no measurable performance impact.
Microservice repositories moved from Azure DevOps Classic pipelines to one unified YAML multi-stage pattern with Helm, retiring 96 legacy pipelines.
Downtime on a platform-wide domain migration spanning 20+ microservices, Kubernetes secrets and every auth flow that depended on them.
Before that, desktop support at Carnival and an IT internship at Avalex Technologies. BS in Information Technology, University of West Florida, 2017, including a project with the Global Cyber Alliance testing DNS response policy zones on AWS. AZ-104 since 2019.
AKS administration, Helm, NGINX Ingress and Gateway API, Container Apps with .NET Aspire, resource right-sizing from real metrics rather than guesses.
Azure DevOps YAML multi-stage pipelines, GitHub Actions, Release Flow branching, branch policies that make the path from work item to production auditable, DORA metrics.
Terraform and Bicep, including how modules find and call each other once a repository has hundreds of files. There is a whole page on this site about that.
Application Insights with distributed tracing, KQL dashboards, token and consumption tracking for AI workloads, and the cost work that follows from actually being able to see usage.
WAF traffic forensics across Azure Front Door policies, dependency remediation with Sonatype IQ, Entra ID, Intune, and RBAC designed to survive an audit.
PowerShell, C#, Python and Bash. Ticketing automation, ETL into Snowflake, and a Copilot extensibility framework of custom agents and reusable skills used across 30+ repositories.
A plain English explanation for people who know technology but do not work in it, built around the real Terraform that puts this site on the internet. It quotes its own source and walks through it line by line.
Read it →A rhythm game that builds its own charts. Instead of a fixed note track it runs live onset detection on whatever audio you share from a browser tab, so it plays along to your music. No backend, no build step, no dependencies.
Play it →The practitioner version of the infrastructure page. How modules reference each other at scale in both languages, with the failure modes that only appear once a project is large. Dense on purpose.
Read it →Tetris, Snake, Minesweeper, Asteroids and nine more, all in the browser on the same free static web app, with a shared leaderboard behind one small function. Built to prove a point about what a host will serve.
Go and play →Everything here is static files on Azure Static Web Apps, described by about twenty lines of Terraform and deployed with one command. It costs nothing a month to run. The only resource on the bill is a storage table holding a few kilobytes of game scores, which prices out below a cent.
The infrastructure page is not a write-up about some other project. It prints the exact file that created the thing you are reading it on, and the whole site can be destroyed and rebuilt from it in about a minute.