Portfolio

Selected work — built and shipped.

A curated selection of client projects, research systems, and engineering products spanning machine learning, robotics, software, and hardware design. Each one started with a hard problem and ended with something that actually ran.

40+
Systems shipped
9+
Years experience
18+
Client organisations
All WorkMachine LearningRoboticsSoftwareHardwareResearchMLOps
Software·2022

Kepler — Open-Source Motion Planner

Modular C++ motion planning library with Python bindings and ROS 2 integration. Used by three research groups, cited in 12 papers.

Machine Learning·2025

Atlas Energy Demand Predictor

Temporal Fusion Transformer-based forecasting pipeline for grid-scale energy management. 18% MAPE reduction over baseline model.

Robotics·2025

Pulse Perception Stack for L4 AVs

Multi-modal sensor fusion pipeline for adverse weather autonomous driving. 28ms inference, +41% rainy-weather mAP over previous model.

MLOps·2024

Orion Model Monitoring Platform

End-to-end MLOps platform for drift detection, retraining triggers, and explainability dashboards. Deployed across 12 production ML models.

Hardware·2024

Bionic Prosthetic Socket

Patient-specific prosthetic socket designed using parametric CAD and topology optimisation. Produced via selective laser sintering in PA-12 nylon.

Research·2024

Mira Quadruped Gait Policy

Sample-efficient RL policy for quadruped locomotion over unstructured terrain. ETH Zürich collaboration, published at IEEE ICRA 2024.

How I Work

From first conversation to shipped system

Every engagement follows a consistent process — enough structure to keep things on track, flexible enough to adapt to what the problem actually needs.

01

Discovery & Scoping

We begin with a deep dive into the problem. I ask the uncomfortable questions, audit what you already have, and define a realistic technical plan with clear deliverables and success criteria.

02

Research & Prototyping

Before any production code, I build a minimal prototype to de-risk the core technical assumptions. This phase usually surfaces the real problem — which is often different from the stated one.

03

Build & Evaluate

Clean, documented, testable code. Weekly check-ins. Continuous evaluation against the agreed success criteria. I don't disappear into a build phase and resurface with a finished product.

04

Handoff & Support

Every engagement ends with a comprehensive handoff — code, documentation, evaluation report, and a 4-week post-launch support period. Your team should understand what they have and be able to maintain it.

Ready to start a project?

I take on a small number of serious engagements each quarter. If your problem is genuinely hard, I'd love to hear about it.