Backend EngineerLagos, NGRemote
I design and stabilize backend systems where correctness matters. Most of my work is in distributed systems, APIs, and infrastructure: the operational problems that show up after software reaches production.
Currently founding backend engineer at Intense Group UK, where I own the backend that tracks brand deals, processes creator payments, and manages IP rights: the financial and operational backbone for thousands of creators.
open to senior backend roles
I came up close to the product. Early on it was internal tools and a CRM for a real-estate firm: software meant to make a business actually run. Then payments at Motopay, where I owned the money flows: sending between people, paying merchants, buying in-app. The kind of code that has to be right every time, because someone’s wallet is on the other end.
The deeper I went, the more I cared about what sat underneath the features instead of the features themselves. At Mainstack that looked like the plumbing most people never see: a gateway routing the whole platform, a media pipeline on AWS, and an old course-and-billing system buried in a 4,000-file codebase that I took over and quietly stopped from breaking. Less about shipping something shiny, more about building something you can understand and trust to hold up.
building
Intense Group backend NestJS
studying
TypeScript internals Mike North
next
DB storage engines Pavlo / CMU
also
Deutsch A2 · Chess
When your API gateway becomes an accidental monolith
On what a gateway should and shouldn’t own, and the rule I use to keep it honest
Next: idempotency keys and webhook retry logic, and why payment integrations are built the way they are
all writing