About Me
25 years of hands-on infrastructure experience
From physical network cables to cloud-native architecture — and still digging to root cause every time.
My Story
Built from the ground up
I started my career as a Network Engineer and Systems Administrator — managing Linux environments, physical switches, and on-premise servers long before "the cloud" was a common phrase. That foundation gave me a way of thinking about infrastructure that most cloud-native engineers never develop: understanding what is actually happening at every layer of the stack.
Over time I moved into software development, writing backend services and automation tooling in Python, Go, and others. That stretch taught me how engineers think and what they need from the infrastructure running under them. It changed how I communicate and how I design systems.
Today I work as a Cloud Engineer and SRE, bridging development and operations. I help teams migrate to AWS, harden their architecture, and stop hemorrhaging money on cloud spend they never intended to run.
The foundation
Network Engineer and Systems Administrator
Linux (Debian, RHEL), core networking, physical infrastructure, and building the habit of reading logs others skip.
The evolution
Software Developer
Backend services and automation in Python, Go, PHP, and Ruby. Learning to think like the engineers whose code I would later be running.
The present
Cloud Engineer and SRE
AWS architecture, Kubernetes, Terraform, Datadog — and making sure cloud bills reflect what the business actually needs to run.
Now
Independent Consultant
Working directly with engineering teams and CTOs on cloud consulting and cost optimisation. No account managers. Just the work.
Approach
What I bring to your team
Specific strengths that come directly from how my career developed — not from a vendor certification path.
Full-stack infrastructure thinking
I understand what happens at every layer — from kernel networking to Kubernetes scheduler decisions. That context lets me find problems that specialists who only know one layer will miss.
Automation first
Infrastructure as Code is not a preference — it is the only way I work. Terraform and Ansible for reproducible, auditable environments. If it cannot be committed, it does not exist.
Legacy migration without drama
I have done the hard migrations — complex legacy systems to AWS, lift-and-shift to re-architecture — without taking the business offline in the process. The scars are useful.
Cost as a first-class concern
Cloud spend is not an afterthought. I embed cost awareness into every architecture decision — reserved instances, rightsizing, tagging hygiene, Datadog log pipelines — before the bill surprises you.
Tooling
Technology I work with daily
AWS
EC2, EKS, RDS, S3, IAM…
Kubernetes
EKS, self-managed, Helm
Terraform
IaC, modules, state mgmt
Datadog
Observability, cost audits
Ansible
Config mgmt, provisioning
Python and Go
Automation, tooling, APIs
Linux
Debian, RHEL, Ubuntu
Docker
Containers, Compose, ECR
Outside Work
Beyond the screen
When I am not looking at dashboards or writing Terraform, I prefer activities that require the same patience and precision — just without the on-call pager.
Cycling and hiking
New trails, open air, no Slack notifications.
Scale modeling
Assembling plastic kits — aircraft, trucks, and military vehicles. The same patience required for a good infrastructure design, applied to 1:72 scale.
Cinema
A good film is the best way to disconnect and reset.
Ready to work together?
Whether you need a cloud architecture review, a cost audit, or someone to embed with your team on an ongoing basis — let's talk.
Get in Touch