Cloud & Platform Engineering

Most of my platform work is on AWS: landing zones, networking and identity, container platforms on ECS and EKS, and the managed data services that products sit on, such as Aurora PostgreSQL, DocumentDB, OpenSearch and S3. It’s all Terraform, it all goes through CI/CD, and it’s observable from the first day.

The aim is a paved road: one governed starting point, so product teams build on the platform instead of rebuilding it each time. When that works, a new product is running in hours, with security, quality gates and monitoring already in place.

Recovery is part of the platform

A platform isn’t finished until you know how it comes back. I design backup, immutability and recovery in from the start, and test them, instead of leaving them to a runbook nobody has tried.

Where I’ve done it

• A global pharmaceutical company: technical lead for a multi-tenant AWS Data & AI platform. About 25 products run on it, each started from the same blueprint, with its own Terraform, GitHub Actions pipelines with SonarQube quality gates, and Datadog observability, in under a working day instead of weeks.
• A major UK energy provider: led the design and build of an immutable, cloud-native recovery platform across AWS, GCP and Azure, so the business could keep operating if it were ever hit by ransomware.
• A global media and publishing company: built the AWS landing zone and moved the core publishing platform onto Amazon EKS.
• AWS: as a Senior Solutions Architect, ran Well-Architected reviews and helped customers and partners migrate SAP, Java EE and big data workloads.