About Me
I started in enterprise incident response in 2011 and have worked on production readiness and operational resilience ever since. Over time my focus moved from surviving incidents to preventing them, which mostly means building measurement teams actually trust and defaults they don't have to think about. Each role below taught me something I still use.
📊 Keep the instinct, replace the implementation (Finnish retailer, Loyalty platform)
A 12-month consulting engagement. The team was already tracking availability in a monthly Excel sheet. The shape of that report was right. The plumbing underneath it wasn't. So I kept the report and rebuilt what fed it: SLOs defined as code, a Splunk application normalising five observability sources into one view, burn rate alerting wired to on-call, and a status page leadership reads without asking an engineer. Read the case study.
⚡ Make the safe path the default path (Zapier)
As Cloud Infrastructure Team Lead I led the team that brought 100,000+ AWS Lambda functions under managed runtime upgrades: standardised Terraform modules, plus a canary tool that rolled back automatically when an upgrade misbehaved. Functions on deprecated runtimes fell by 95% and nobody had to remember to be careful. Published on the AWS Architecture Blog. I also wrote the on-call and operational readiness standards that let dozens of teams own their own services.
🎮 Structure beats heroics (Unity)
Designed Unity Finland's incident management process from the ground up, taking them from ad-hoc firefighting to something structured enough to scale as the organisation grew.
🎯 What you cannot observe, you cannot defend (Paddypower Betfair)
Ran incident response for one of Europe's largest online betting platforms, where peak load arrives on a fixture list rather than as a surprise. Built observability and resiliency for the betting exchange and the private OpenStack cloud underneath it.
🖥 The cheapest incident is the one that never happens (Rackspace)
Managed incident response from London for Rackspace's largest accounts across Europe, where every minute of downtime landed on someone's business. Owned capacity planning and operational resiliency for the hosted estate, which is the unglamorous work that stops the call coming at all.
🏦 I learned reliability where there was no margin (Dell/EMC)
Customer Engineer handling SAN/NAS storage incidents for major banks and financial institutions. Downtime there wasn't a degraded experience, it was a financial and regulatory event. It set the bar I have worked to ever since.
🤝 Ideas get better when you defend them in public (Community)
Co-founder of the SRE Finland meetup group, where I regularly present on incident management and post-mortem practice.