Services

What I work on

I work in four main areas, detailed below. Based in London, I work with clients across the UK. I work remotely by default, adding a regular on-site day where useful.

The engagement and pricing page details how I scope, agree on, and price work across all four areas.

DevOps Engineering

CI/CD, automation, and GitOps — making releases routine instead of risky.

Site Reliability Engineering

Observability and reliability as measurable properties, not luck.

Platform Engineering

The internal platform other engineers build on, standardised and self-service.

Cloud Infrastructure

Architecture and provisioning on AWS, defined as code and version-controlled.

How this works

01
Get in touch
A message with roughly what you need — the contact form or email both work.
02
A short call
Enough to understand the systems involved and whether it's a fit, on either side.
03
Scope and start
Agree what's in scope and how the engagement runs, then get to work.

Also open to

Platform or observability audits — a fixed-scope review rather than an ongoing placement.
Ad hoc work — a one-off fix or a short piece of work as it comes up, outside a running engagement.

Questions

Remote or on-site?

Either — depends on the engagement. Comfortable with a regular on-site day where that’s required.

Long contracts only, or shorter work too?

Both. Work is usually bought a piece at a time — a broken pipeline, an environment to build, a cluster to sort out — with a monthly block of days available where that suits better. Longer placements also fit. How it’s scoped and priced is on the engagement and pricing page.

Which tools do you use day to day?

Kubernetes, Terraform, Ansible, Prometheus/Grafana/Loki, GitLab CI. Happy to work with what’s already in place rather than pushing a preferred stack.