01 / Introduction

David Collom

I help engineering organisations build platforms their developers can rely on.

I came into platform engineering through software development and still prefer to stay close to the code. Much of my work has been about removing avoidable delivery and operational work across betting and gambling, manufacturing, logistics, defence, security, professional services and e-commerce environments.

02 / Evidence

A few things I've worked on

These are three concrete examples from different points in my career. The project page has more detail on what I owned, built or contributed.

01Platform delivery

3 to 6 weeks → 1 to 2 hours

Reduced environment delivery from a multi-week request process to a repeatable internal platform workflow.

02Operational scale

400+ Award-winning e-commerce sites

Built and supported the infrastructure and automation behind a large, PCI-conscious hosting estate.

03Community contribution

KubeCon + ArgoCon

Spoken at KubeCon, ArgoCon and community events about Kubernetes cost, reliability and lessons from real incidents.

03 / Contexts

Built across demanding contexts

The common thread has been operational pressure: regulated systems, high-traffic platforms, customer-facing delivery and environments where downtime or manual process becomes expensive quickly.

Betting & gambling

Kubernetes platforms, service reliability and automation for teams working around highly visible production systems.

Manufacturing & logistics

Public web systems, reporting, ERP, CRM and warehouse-facing integrations backed by production infrastructure.

Defence & security

Cloud-native security, platform architecture and delivery work in environments where assurance and governance matter.

Professional services

Customer expectation management, success planning, design and implementation, mentoring, tutoring and technical training.

04 / Focus

What I tend to work on

01

Platform engineering

Internal platforms that take recurring delivery work out of tickets and give teams a supported route to production.

02

Developer experience

Finding the awkward parts of build, delivery and operations, then fixing them with the teams who use them every day.

03

Reliability & automation

Kubernetes operations, GitOps and automation for systems that need to be understandable when something goes wrong.

04

Technical leadership

Architecture and technical direction backed by prototypes, code and a clear account of the trade-offs.

05 / Philosophy

"I like finding work that engineers have learned to put up with, then working out whether the platform can remove it. Sometimes that means code; sometimes it means fixing the process around the code."

I still like getting hands-on. Architecture decisions tend to improve when the person making them has recently had to debug the result.

06 / Connect

Working through a difficult platform problem?

If the problem involves Kubernetes, developer platforms or too much manual operational work, I'm always happy to compare notes.