About

I am an engineering leader and full-stack builder based in Lancashire. I build product software for workflows where mistakes carry operational or user consequences: support engineers need to reason about messaging issues, users need to review AI-assisted document changes before mutation, and developers need to inspect model-assisted code changes before applying them.

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 working under data-governance constraints, support teams investigating delivery issues, and product teams depending on operational systems to behave predictably. I like building the parts of a product that make those moments less ambiguous.

Most of my interests sit somewhere between messaging infrastructure, application engineering, document workflows, AI agent tooling, 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.

Experience

The fuller timeline lives on the experience page. My work has centred on product engineering in systems with operational consequences: governed data handling, workflow tools, delivery investigations, support escalation, release readiness, team leadership, and ownership transitions. That includes computer science teaching and research, university platforms, medical AI tooling, digital health software, freelance product delivery, and messaging infrastructure at Emarsys, an SAP company.

My current independent work is more public because I own the products end to end. Masterful CV is a live product for CV and application workflows. Consortio is a pre-user-launch CLI prototype for comparing coding-model approaches to repository tasks. Employer work is summarized at the level of domain, responsibility, and broad outcomes rather than implementation detail.

What I tend to build

• Messaging, workflow, document, and platform systems where ownership and state are visible.
• Product tools that show the important artifacts: document previews, application workflows, agent diffs, verification output, 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 product workflows with visible state and ownership
• AI-assisted engineering with verification output and human-controlled delivery

Get in touch

If you want to talk about engineering leadership, hands-on full-stack work, AI-assisted engineering workflows, product systems, or reliable 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 work.