Teaching
Most courses teach you to run commands. Almost none teach you to make the decision.
You can learn kubectl in a month. Knowing which of forty possible answers fits a particular team's size, skills and deadline takes years — and it's the thing that separates an engineer who can build a platform from one who should be trusted to design it. That's what I teach.
1:1 mentoring
- Who
- Engineers moving from DevOps into platform or architecture roles
- Format
- Fortnightly sessions, ongoing
We work on your real systems, not exercises. You bring a decision you're stuck on or a design you're unsure about; we work through it the way a senior colleague would — options, trade-offs, and the reasoning written down. Between sessions you build, and I review.
What we cover
- Architecture decision-making and how to defend a design
- Kubernetes beyond the certification syllabus — multi-tenancy, networking, upgrades
- Reading a system you didn't build
- Writing the artifacts that get you treated as an architect
Team workshops
- Who
- Platform and infrastructure teams, 4–12 people
- Format
- One to three days, remote or on-site
Taught against your actual stack rather than a generic lab, which means the examples are your services and the exercises leave you with something you keep. I'll spend time before the workshop understanding what you run, so the day isn't spent on things you already know.
What we cover
- Kubernetes in production — what breaks and why
- GitOps and progressive delivery with Argo CD
- Terraform module and landing zone design
- Cloud-native networking: CNI, service mesh, Gateway API
- Observability and SLOs that mean something
Architecture coaching
- Who
- Teams with the skills who keep making decisions they later regret
- Format
- Monthly, ongoing
Not training — a standing review. I sit in on your significant design decisions, ask the questions nobody in the room is incentivised to ask, and help the team build the habit of recording why. Most teams don't need more knowledge. They need a process that makes their existing knowledge show up at the right moment.
What we cover
- Architecture decision records as a working practice
- Design review facilitation
- Post-incident reviews that produce design changes, not more alerts
- Technical debt registers leadership will actually fund
Rates on request. Tell me the format and the group size and I'll send a quote.
Want to talk about training?
Tell me who's being trained, what they already know, and what you want them to be able to do afterwards. That last one is the question most training briefs skip.
Stockholm, Sweden (CET) · Comfortable overlap with European hours and US East Coast mornings