Helping build Autodarts.

At Autodarts, my engineering work spans firmware, infrastructure, AI, streaming and analytics. It brings together the things I enjoy most: understanding a product, working across its different layers, and making those layers work together.

From devices to the platform.

Firmware and infrastructure ask different questions. On a device, you have to think about its constraints and how it behaves in the real world. On the platform, you have to think about how services run, communicate and recover when something goes wrong.

I like working across that boundary. A decision in one part of a product can change what another part needs to do. Understanding both sides helps me reason about the whole system.

AI, streaming and analytics.

These are also part of my work at Autodarts. Each brings a different engineering concern: how AI fits into a useful product experience, how streaming behaves under real network conditions, and how analytics helps us understand what is happening.

What interests me is how those concerns connect. A feature needs more than an implementation: it needs infrastructure that supports it and enough visibility to understand its behaviour.

Engineering with the product in mind.

This is why I describe myself as an engineer by trade and a product guy at heart. I enjoy the technical details, but I want to understand what they make possible for the person using the product.

Helping build Autodarts is part of that broader approach, alongside building Merrin and delivering software for clients. The setting changes; the interest in the whole product stays the same.