Case studies
Most of my work belongs to the companies I built it for. These write-ups describe the shape of each problem and the engineering approach taken, in generalised terms, with the confidential parts left out.
How to read these. Every professional case study below is sanitised. Technologies, systems and responsibilities are exactly as recorded on my CV. Architecture figures are conceptual: they show the conventional shape of a system of that description, not any employer’s internal design. No proprietary source code, infrastructure detail, customer data or confidential business metrics appear anywhere on this site.
Systems built inside companies. Written up as case studies rather than repositories, because the code belongs to the organisations that own it.
FinTech · Java & Spring Boot
Led backend development of a funds-transfer service operating across 8+ partner banks, plus the mobile-money integration that extended the platform into MTN's ecosystem.
FinTech · Node.js, Java & Laravel
Integrated 14+ VAS billers (airtime, electricity, betting) into a B2B middleware, and built the aggregation platform and reporting service underneath them.
PropTech · Microservices, React Native & MLOps
Lead software and DevOps engineer: in-house backend microservices, a React Native app on iOS and Android, an engagement model served through TensorFlow Serving, and the CI/CD and cloud infrastructure underneath all of it.
Logistics · Laravel, Kotlin & IoT
Architected a full freight management system and its Kotlin mobile application, integrating third-party tracking APIs and IoT logistics data to support dynamic delivery routing.
GovTech · Python, NLP & Backend Systems
Backend systems for two state tax-automation programmes, including an NLP model for extracting insight from financial data. Earlier, the front end of a state public procurement portal.
Placeholder, awaiting content
This section is reserved for publicly available projects and open-source contributions, kept deliberately separate from the professional work above so that nothing implies company code is public.
It is intentionally empty rather than filled with invented entries. Public repositories can be added as content files without touching the design, see content/case-studies/.
Contact
I’m open to senior and lead engineering roles internationally, backend, full-stack, architecture and platform work. The fastest route is email; LinkedIn works just as well.