Hi, I am
Also known as eazecodes
Product engineer with four years of shipping software people actually use — with a keen passion for scalable, robust systems and the schemas, queues and payment paths that hold them up.
4+
Years building
11
Products shipped
5
Teams
2
Ends owned
I'm Ezekiel — a product engineer in Lagos. I build the whole thing: React and React Native on the surface, Node.js and Django underneath.
What I enjoy most is the part that has to scale — schemas, queues, caches, and the auth and payment paths that quietly decide whether a product survives its own growth. I'd rather spend a day on the tables than a quarter on migrations that undo them.
Right now I'm at Roov, a property tech company, working across the mobile app and the Node.js services behind it — listings, search, and the workflows that hang off them. Before that: Learnpally, RentAnything and EkoPages, where I owned the parts products quietly die on — Paystack and Stripe reconciliation, JWT and OAuth 2.0, role-based access control, and BullMQ workers.
Lately I've been learning AI — building with models rather than just calling them, and working out where they genuinely earn their place in a product instead of being bolted on.
I own features end to end — the data model, the endpoints, and the screen that consumes them, so nothing gets lost in a handoff.
Web apps · Mobile · Design-to-ship
The half nobody sees: schemas, queues, caches, and the auth and payment paths that decide whether a product survives its own growth.
Node.js · Django · Postgres · Redis
Cross-platform apps that feel native — consistent UX across iOS and Android, and push delivery that fires once instead of four times.
React Native · Expo · Firebase
Four habits that decide whether what I ship still works a year later.
Most product bugs are data-model bugs in a costume. I'd rather spend a day on the tables than a quarter on migrations that undo them.
Webhooks arrive out of order, jobs retry, networks lie. Anything touching money or state gets keyed so a replay is a no-op.
Clever code is a liability at 2am. Predictable structure, clear names, and tests around the parts that move money.
Access control enforced at the data layer, not in components. Slow work pushed onto a queue before it costs anyone a request.
Four years across property, learning, marketplaces and commerce.
Products I've shipped across payments, learning and commerce.
FinTechDigital savings circles with Naira wallets, a double-entry ledger, Paystack funding, and automated payout rounds.
SaaS · EdTechLed the team building a full-stack learning platform — queue-backed background jobs, Prisma data layer, and a Next.js frontend.
EdTechE-learning platform across web and mobile. Course management, Paystack payments, background jobs for email and video processing, and PostHog analytics.
E-commerceEducational platform teaching African children about the SDGs through illustrated stories, courses, and blended learning programmes.
EdTechUniversity learning management system covering course delivery, assignments, assessments, and student progress tracking.
A focused set I reach for to ship fast, reliable products across web and mobile.
Frontend & Mobile
Backend & Data
Platform & Tooling
Most of my spare cycles go one of three places.
Learning
Models, retrieval and evals — the parts that survive a demo, not just the ones that impress in one.
Playing
Mostly blitz. It rewards thinking two moves past the obvious one, which is more or less the job.
Lurking
Where I find out what broke in the ecosystem this week, usually before the changelog says so.
Got a product to build, a team to strengthen, or just want to argue about schema design? My inbox is open — I usually reply within a day.