Selected Work
Twenty-plus years of infrastructure and cloud leadership, distilled into four engineering pillars. This is the hands-on work behind every Ace Cloud Guru engagement — the code, the platforms, and the migrations that came before the consultancy.
The Pillars
Every migration touches all four. I don't hand them to four different teams — I architect across them.
Python
Python is the glue in my migration practice: parsing Azure Migrate assessment exports into prioritized wave plans, driving the Azure SDK for bulk provisioning and validation checks, and building the small, sharp tools that turn a 400-row spreadsheet into an executable runbook.
At Rheem, I paired this kind of automation with GitHub Copilot agents and standardized engineering SOPs across a 15-person team — deployment cycles fell from nearly a month to under a week, roughly a 75% improvement in delivery speed.
.NET
Legacy .NET is where most enterprises' technical debt lives — Web Forms, WCF, Framework 4.x. I modernize these workloads onto Azure App Service, Container Apps, and AKS: strangler-fig refactors, framework upgrades, and cloud-native rewrites where the ROI justifies it.
Every modernization is scoped against the 6 Rs — rehost, replatform, refactor, rearchitect, rebuild, or replace — so the technical path always serves the business case, not the other way around.
Terraform
Every Azure landing zone I design is Terraform from day one: modular, environment-promoted, policy-guarded. I govern IaC the way enterprises need it — remote state, plan/apply discipline, module versioning — so platform teams inherit infrastructure they can actually operate.
This is the foundation I set at enterprise scale: identity, networking, security, and compliance expressed as code, reviewed like code, and deployed through CI/CD.
Kubernetes
Container platforms done right: AKS cluster architecture, GitOps delivery, and workload migration from VMs to containers. I treat Kubernetes as a product — paved-road namespaces, policy, and observability — not a science project.
For teams adopting containers during a migration, this means day-two operations are designed in from the start: upgrades, scaling, and cost control, not just day-one deployment.
Representative Engagements
Rheem Manufacturing · 2025–2026
Led a 15-engineer team (7 on-site, 8 offshore) through an enterprise-wide migration from on-premises infrastructure to Microsoft Azure — 130+ applications migrated in the first year. Drove adoption of AI-assisted engineering (GitHub Copilot agents, standardized SOPs), cutting deployment cycle times by roughly 75%. Architected and governed Azure infrastructure across identity, security, networking, IaC, and CI/CD.
Lemongrass Consulting · McKesson · 2024
Principal Cloud Solution Architect and technical lead for McKesson's enterprise SAP HANA migration from on-premises to Microsoft Azure — a three-phase initiative across QA, Performance, and Production. Architected the full Azure footprint (Key Vault, VMs, VNets, NSGs, load balancers, Application Gateway, NetApp Files), with Azure Migrate and Azure DevOps CI/CD orchestrating replication, testing, and production cutover at enterprise scale.
Microsoft · 2019–2022
Four years as a customer-facing Azure Cloud Solution Architect at Microsoft — the role that built the presales-to-delivery muscle behind Ace Cloud Guru: technical discovery, solution architecture, migration planning, and executive stakeholder alignment across enterprise Azure adoption.
Client-confidential details available on request. Specific project names and metrics shared under NDA.
Free 30-minute consultation — migration, modernization, or just a second opinion on your cloud bill.