01 / About
Lead Platform Engineer with nearly a decade of experience building and scaling cloud infrastructure, specialising in AWS. Passionate about using technology to drive the renewable energy transition, with a track record of leading cloud modernisation and automation initiatives for large-scale, mission-critical platforms. Skilled in architecting resilient, high-performance systems, optimising for scalability, cost, and operational efficiency. Experienced in leading engineering teams, fostering a culture of innovation, and translating complex technical challenges into real-world impact.
02 / Stack
- AWS
- Terraform
- OpenTofu
- Docker
- Kubernetes
- Helm
- ArgoCD
- Python
- Bash
- Linux
- Cloudflare
- Datadog
03 / Principles
Don't be the bottleneck
If a deploy or an incident can only be sorted by me, I've done something wrong. I'd rather write it down and pair on it until the team doesn't need me in the room.
Pick the boring option
I'd rather use the managed service and the tool everyone already knows. Clever setups are fun right up until you're the one debugging them at 3am.
Make the right way the easy way
Nobody reads the wiki page on how to set a service up properly. If the template already has logging, alerts and sensible defaults, people just use it.
Check the graphs first
Before I start cutting costs or chasing a slow endpoint, I want to see the numbers. Half the time the problem isn't where everyone assumed it was.