A backend engineer's notes on three years of keeping the lights on — across fintech, logistics, med-tech, ed-tech, and e-commerce.
Over three years, I have worked on production backend systems for teams that could not afford to be surprised. At MAP Systems the work was event-driven microservices — the kind that spend most of their time being unremarkable. At Uhunger it was APIs carrying more than 10,000 monthly transactions, where every failed call meant a customer left waiting. The brief changes; the discipline doesn't.
I work in two ecosystems and switch between them without ceremony: Java with Spring Boot and Kafka where the domain calls for it, and Node.js with NestJS and Express where it doesn't — both paired with relational databases I trust to outlast me. I have built and maintained payment systems, wallets, and secure transaction flows integrated with Paystack, Flutterwave, VFD and Dotai. Reliability and data integrity are not the glamorous parts of the job; they are the job.
My core focus is backend engineering, system design, and service reliability. I am frontend-capable when a sprint asks for it, but the work I return to is architecture, infrastructure-aware design, and the long middle of maintainability — the years between ship and rewrite.