Cloud computing
A systems view of reliability, security, cost, and developer experience rather than isolated infrastructure tasks.
Focus 03 · Cloud engineering
I treat cloud as a system where reliability, security, cost, and developer experience have to work together.
01 / What I bring
Cloud engineering is more than provisioning resources. It is the work of making a large, changing environment understandable and sustainable for the people who operate it.
02 / Working model
The goal is not a pile of policies. It is an operating model teams can understand and use.
Map the environment
Surface the constraints
Balance cost and reliability
Keep operations visible
03 / Selected work
The broader portfolio connects cloud practice to platforms, identity and access, infrastructure, and organizational controls.
A systems view of reliability, security, cost, and developer experience rather than isolated infrastructure tasks.
Make tradeoffs visible, keep change affordable, and design systems teams can operate and evolve.
Local-first system design with provenance, auditable context, and a rebuildable data model.
04 / Production evidence
The cloud lens is grounded in systems that had to support ownership, migration, security operations, and cost-aware reliability.
Led a team of engineers building an AWS Organizations metadata system that made account ownership and fragmented cloud information usable across operations, finance, and security.
Drove roughly $5M in annual cloud savings by identifying orphaned, underutilized, and oversized resources and driving accountable remediation across the AWS environment.
Moved thousands of non-standard AMIs into a security-scanning workflow for SecOps, with several components developed using AI assistance. The work saved tens of thousands of dollars in scanner licensing and server costs.
Supported a high-volume CVE workflow with AMI remediation, scripted health validation, closure checks, and account-specific reporting.
Led a 12-person engineering team through an AWS security incident response, coordinating with SecOps and senior leadership to contain the incident, investigate affected access, and harden the organization.