What I do
I work with systems that are supposed to just work — even when things get messy.
I’m a Digital Systems Engineer with over six years of experience keeping high-traffic, customer-facing platforms running. Most of what I do happens behind the scenes – watching systems, responding to incidents, coordinating fixes, and making sure services stay up when people actually need them.
I like working close to production and dealing with real problems. I want to know how a system behaves under load, where it tends to fall apart, and how small, deliberate changes can make it more reliable over time. Incident response, observability, dashboards, process improvements – these are just part of the job, not things I drop into a CV to sound impressive.
I started in IT administration, which gave me a solid grounding in how infrastructure, access, and operations work in practice. That background still shapes how I approach problems: calmly, step by step, with a focus on stability rather than fast fixes that break something else later.
How I work (and a bit beyond work)
Over the years I’ve often sat between engineering teams, product, and business stakeholders – translating between the three and making sure nothing gets lost in the process. I care about clear communication, predictable systems, and solutions that actually hold up in production.
I tend to do well in environments where ownership is clear, responsibility matters, and reliability isn’t optional. I prefer steady improvements and processes that help teams move faster rather than slow them down.
Outside of work, I’m drawn to things that reward patience over speed – Formula 1, strategy games, a bit of sim-racing, and getting out on my bike when the weather allows.
If you want to work together, explore an opportunity, or just talk shop about systems and reliability – feel free to reach out.