Profile

About

Engineering leader and full-stack software developer based in Lancashire, UK.

Location
Lancashire, UK
Contact
Email

I am a hands-on full-stack product engineering leader who likes product-minded engineering, dependable systems, AI-assisted delivery, and tools that earn their place.

Most of my interests sit somewhere between messaging infrastructure, application engineering, AI agent workflows, developer experience, and the quieter end of the web. I tend to prefer systems that are easy to inspect, easy to operate, and easy to revisit six months later without needing to reverse-engineer my own choices.

That bias comes from working on software that had to serve real people in fairly unglamorous moments: students trying to find library material, clinicians and researchers handling medical data, support teams chasing delivery issues, and marketers depending on SMS or email credits to behave predictably. I like building the parts of a product that make those moments less ambiguous.

Experience

The fuller timeline lives on the experience page. The short version: I have worked across computer science teaching and research, university platforms, medical AI tooling, digital health software, freelance product delivery, and messaging infrastructure at Emarsys. The current version: I am independently driving Masterful CV and Consortio end-to-end; AI-agent orchestration is central to Consortio, while product, architecture, integration, and release decisions stay with me.

The work has usually sat close to real operational pressure: catalogue search used by students and staff, medical-data workflows, SMS campaign tooling, partner APIs, delivery incidents, credit systems, and cloud-native messaging infrastructure.

What I tend to build

  • Messaging, workflow, and platform systems with clear ownership.
  • Product tools that show the important artifacts, including agent diffs, CV exports, application workflows, verification evidence, and operational status.
  • Interfaces that feel lightweight even when the underlying system is not.

How I like to work

Readable code, tight feedback loops, and boring tools used well. For personal work: static output, plain text content, and only enough interactivity to help the reader.

Areas I keep returning to

  • Messaging infrastructure and event-driven systems
  • Developer tooling and typed APIs
  • Durable interfaces for operationally important workflows
  • AI-agent-assisted engineering and verification

Get in touch

If you want to talk about engineering leadership, hands-on full-stack work, AI-assisted delivery, product systems, or operationally important software, I would be glad to hear from you. The quickest way to reach me is email; you can also see what I am working on now or browse my projects.