I design and build the systems products run on — APIs, data models and the architecture underneath. Backend by default, full-stack when it helps, on-chain when it earns its place.
Systems designed to outlast their first version — architecture, backend, and the migrations in between.
Data models, multi-tenancy and permission layers designed so a product can grow without a rewrite — the part that decides what you will be able to build in two years.
NestJS and TypeScript services, from authentication and role hierarchies through queues and background jobs to the REST APIs your frontend teams build against.
When a system built for the original vision can no longer carry where the product has gone: diagnosis, a replacement design, and the migration to get there.
Wallet authentication, smart-contract integration and SDK work — bringing on-chain capability into a product where it genuinely earns its place.
A platform I designed the architecture for and built the foundation of: a configurable workflow engine, multi-organisation affiliations, offline-first sync for field agents and cross-organisation collaboration. Private codebase.
Notes on tech, fitness, and the things I discover.
Hiring for a platform or backend role, or sitting on a system that has outgrown its foundations? I’d like to hear about it.
Start a conversation
