Cloud and platform engineering
Foundations, workload architectures, and the platforms teams use to run them.
Senior Cloud & Platform Engineer
I own the foundation, the pipeline, or the API edge.
I design and build the cloud platforms, automation, and production systems engineering teams run on. One platform I built and operated covers 12 AWS regions and more than 150 accounts. After its recommendations were remediated, running cost came down by up to 35 percent. Product onboarding that took four to six weeks became one click.
Taking independent work now. I keep the number of engagements small so I can stay hands-on from architecture through production. I work in your cloud account, under your NDA.
- 12AWS regions
- 150+Cloud accounts
- 35%Lower running cost after remediation
From a cloud enablement platform I built and operated.
01
What I build
Cloud foundations, platforms, automation, and the engineering systems products run on.
Infrastructure automation
Repeatable provisioning and infrastructure as code, across cloud and SaaS providers.
Data engineering
Pipelines, event-driven ingestion, and analytical datasets a team can trust.
API and service platforms
Service foundations generated once, so the next team writes the product.
Cloud modernization
Existing estates improved through architecture, governance, reliability, and cost.
02
Selected work
Systems I have built. Client names stay off this site.
- 01Cloud enablement platformUp to 35% lower running costA platform I built and operated across 12 AWS regions and more than 150 accounts.Platform
- 02Landing zone automationFour to six weeks → one clickA product enters a governed cloud environment in one action, not a multi-team queue.Onboarding
- 03Automated service foundationsThe next service starts on the platformInfrastructure, delivery, and operational wiring generated with the service. Canary included.Service platform
- 04Data and event platformA producer writes only if it passesEvent-driven ingestion into Iceberg, with schema and quality checks before the write.Data platform
03
Technical range
The kind of engineering, then a few tools that stand for it.
Cloud architecture and infrastructure
Cloud foundations, workload architectures, and production environments across AWS, Azure, and Google Cloud.
AWS · Azure · Google Cloud · Networking · IAM · Kubernetes
Platform engineering and cloud automation
Reusable platforms and automated workflows that give teams a reliable path from infrastructure to production.
EKS · AKS · GKE · ECS · Serverless · Platform automation
Infrastructure as code and automation
A core part of how I build. Infrastructure as code across cloud and SaaS providers, including AWS, Azure, Google Cloud, Okta, and Confluent, so change stays repeatable, governed, and maintainable.
Terraform · CloudFormation · Atlantis · GitOps
Data engineering and analytics
Pipelines, streaming and batch processing, transformation, storage, and the datasets and reports a team actually uses.
Kafka · Confluent · Glue · Athena · Iceberg · Airflow · QuickSight
API and service platforms
Automated service foundations: infrastructure, structure, configuration, delivery, and operational wiring. Canary deployment included by default.
Python · FastAPI · REST APIs · API platforms · CI/CD
Security, identity, and governance
Identity, access, secrets, encryption, and multi-account controls built into the platform, not bolted on as a product list.
IAM · KMS · Secrets · Organizations · Control Tower
CI/CD and developer delivery
Delivery systems that connect source control, infrastructure, testing, deployment, and production.
GitHub Actions · Jenkins · GitLab CI · Bitbucket Pipelines · CodePipeline · Atlantis
Databases and storage
Application databases and cloud storage across transactional, distributed, and analytical workloads.
PostgreSQL · MySQL · CockroachDB · RDS · DynamoDB · S3
Observability and operations
Monitoring, metrics, and enough visibility to operate a system after it is live.
Prometheus · Grafana
Backend engineering
Supporting work: Python services, REST APIs, event-driven systems, and serverless applications. The practice is the platform.
Python · FastAPI · Serverless
04
What you can engage me to own
Platform and engineering leads who need a cloud foundation, a data platform, or a service platform owned through to production.
I focus on outcome-driven platform work rather than open-ended ticket execution.