Software Engineer - Systems & Infrastructure
I build production systems for startups and growing businesses - API, database, frontend, payments, and the infrastructure they run on. Not just the code. The system.
SCROLL
I build production systems for startups and growing businesses - end to end. That means database design and API architecture on one end, and VPS provisioning, Nginx configuration, and SSH hardening on the other, with the frontend and payment integration in between. Most engineers hand off deployment. I own it, because a feature that isn't running safely in production isn't finished.
Over the past three years that's meant designing event-sourced order state machines for a logistics platform, building an escrow-based payment system for a service marketplace, migrating a static site to a full MERN application, and shipping AI-driven features on top of GPT-4o - resume scoring, provider matching, inline suggestions. Different domains, same discipline: understand the system before touching the code.
Not just the code - the system.
Five engagements, one pattern: inherit ambiguity, design the system, own it through to production. Read it like a log - select an entry.
Cloud warehousing & last-mile logistics platform, Lagos pilot · sole backend engineer
AI-powered service marketplace, sole technical decision-maker · built alongside contract work
EdTech platform, remote · full-time · sole technical lead, directed one junior developer
AI-powered career platform · ~100-person company across engineering, product, and operations
Internal factory management system · greenfield build
Three systems built end to end - architecture, implementation, and the infrastructure underneath.
The stack, cross-sectioned - from interface to the decisions underneath. Select a layer to open it.
Interfaces built for the people who use them.
Provider and customer dashboards for Servyst, a mobile-first rider UI for Kriwheel built for low-end Android devices on slow connections, and Figma-to-production delivery accurate to the pixel at LoubbyAI and The Factory Place.
APIs and services that hold up under real traffic - and the auth layer guarding them.
The modular-monolith NestJS backend at Locoomo, the escrow-based marketplace API at Servyst, and OAuth/OTP onboarding flows built at LoubbyAI.
Schemas and queries designed for correctness first, speed second - speed still matters.
PostGIS-backed proximity search at Locoomo, Redis caching for high-frequency reads at TRIIBE and Servyst, and roughly a 20% API latency reduction through query tuning at The Factory Place.
The part most engineers hand off. I provision it, harden it, and carry the pager.
Production VPS provisioning and hardening for Servyst, TRIIBE, The Factory Place, and my own client acquisition system - Nginx, SSL/TLS, fail2ban, SSH hardening - with zero downtime incidents to date.
Decisions that hold up after the demo - enforced in CI, not just in a doc.
The event-sourced order state machine and CI-enforced module boundaries at Locoomo; the escrow release logic and GPT-4o provider-matching system at Servyst; provider-agnostic payment adapters across Paystack, Stripe, and Flutterwave.
University of Nigeria, Nsukka
Experience, technical skills, key projects, and education - the same source of truth this site is built from.
Open to remote roles worldwide, and on-site opportunities where it makes sense. Reach out directly.