01 / Interfaces
APIs that read like documentation
Predictable resources, honest status codes, errors a client can actually branch on. The contract is the product.
Software engineer / System design
I build the load-bearing half of software — the APIs, schemas and services that have to stay standing when nobody is watching them.
mostly Node & Postgres, occasionally Mongo when the shape fits
Building scalable software systems, one API at a time
What I do
01 / Interfaces
Predictable resources, honest status codes, errors a client can actually branch on. The contract is the product.
02 / Data
Relational where relationships matter, document where they don't. Constraints in the database, not only in the application.
03 / Systems
Multi-tenancy, auth boundaries, payment flows. The parts that are expensive to change once real users depend on them.
Selected work
An online storefront and staff dashboard for an over-the-counter chemist in Okaishie, Accra. No stock column — stock is derived from the batches that arrived, so expired boxes stop counting on their own.
A secure, scalable backend for a multitenant e-commerce web application where users browse and purchase products from multiple vendors across a single platform.
The backend for the University of Ghana Gym's subscription management system — digitalising a manual process so members can buy and manage subscriptions online, at any hour.
Next
I'm interested in backend work, system architecture, and anything that forces me to grow as a software engineer.