Abdulmujeeb Oluyede, product engineer
I build the systems products run on.
Full-stack engineer who lives in the backend: multi‑tenant platforms, payments, queues, and realtime that stays up.
Hofwamshofwams.com
Lead engineer / 2024.12 to now
Ticketing, RSVPs, check-in and catering forecasts for event organizers, with Stripe Connect payouts.
- organizers
- 100+
- published events
- 50+
- tests
- 1,370+
Selected work
Most of it is private client work, so the case studies describe the engineering rather than link to code. Numbers are counted from the repositories.
Hofwams
Lead engineerhofwams.com
Ticketing, RSVPs, check-in and catering forecasts for event organizers, with Stripe Connect payouts.
- organizers
- 100+
- published events
- 50+
- tests
- 1,370+
OnchainSuite
Software Engineeronchainsuite.com
Retention and CRM for Web3 teams. I shaped the architecture, own the web app and cut hosting costs by 58%.
- hosting cost cut
- 58%
- organizations using it
- 10
- costly vendors replaced
- 4
Online Campus
Backend and DevOps engineerebschool.org
Learning platform for a business school: course sales, timed quizzes and verifiable PDF certificates.
- students
- 10+
- endpoints
- 117
- tests
- 350
Hospital platform
Backend engineerLive at a hospital in the Netherlands
Operations platform for a hospital in the Netherlands. I built its real-time notifications, a Google Drive-style document system with granular permissions, and roster locking.
- in hospital use
- Live
- systems owned
- 3
- person team
- 7
OmniGuard
Full-stack engineerIn development
Operating system for private security firms. Every firm runs in its own database, with live incidents over SSE.
- endpoints
- 340
- entities
- 69
- ADRs
- 19
Also shipped
Multichannel sales outreach. I built the campaign engine, threaded inbox and the Next.js client.
Django, Celery, Postgres, Redis
Trade compliance SaaS. I taught it to read tariff books from 10 countries and parse the UN dangerous goods list.
NestJS, AWS Lambda, Step Functions, DynamoDB
In their words
From founders and teammates I've built products with.
AbdulMujeeb restructured the backend while keeping existing API endpoints working. He made payment retries safe from duplicate charges, built payment reconciliation so we could recover orders that got stuck after a successful charge, and handled concurrent orders to prevent overselling. He's the kind of backend engineer you can trust with a critical part of your product and count on to make it better.
Abdulazeez AtandaFounder and CEO, Asoebi AfricaMujeeb was there from day one at OnchainSuite. He wrote the first lines of both our dashboard and our backend. When we needed to move production from Render to DigitalOcean and Coolify, he spent his weekends on the Docker setup and wrote the cutover runbook we followed to switch over. I’d recommend him to any team that needs a full-stack engineer who can also be trusted with their infrastructure.
Obafemi JoshuaCTO, OnchainSuiteRead the case studyWhen MJ joined, HOFWAMS was still an idea. He led the product’s architecture and development, frontend and backend, and built what our organizers rely on: tickets, RSVPs, QR check-in and direct payouts. When organizers were leaving events stuck in draft, he simplified setup and more of them went live. I would especially recommend him to early-stage startups that need an engineer who can do more than just write code.
Paul OlatunjiFounder and CEO, HOFWAMSRead the case studyWhen Emjay joined, we had a project with several key features still outstanding, including Drive and patient-facing modules. He took full ownership of those builds and immediately raised our speed of delivery. Day to day, Emjay is highly independent: he owns features end to end, delivers on time, and asks only the questions that matter. I’d recommend him without hesitation for any full-stack development work.
ThankGod AjayiDirector, Tactology GlobalRead the case studyExperience
Five years across startups and remote teams, moving steadily from frontend into backend systems.
BSc Industrial Chemistry, University of Ilorin (2015). Moved into software engineering in 2020 through self-directed study.
Full Stack Engineer, Tactology Global
2025 to now, Remote, full-time
Backend engineer on a hospital platform in the Netherlands (real-time notifications, a permissioned Drive, roster locking), then OmniGuard, a multi-tenant system for security firms.
Software Engineer, OnchainSuite
Oct 2025 to now, Remote, part-time
Retention and CRM for Web3 teams, used by about 10 organizations and agency partners. Shaped the architecture, started the web app, cut hosting 58% with a self-hosted VM, and review the team's pull requests.
Lead Engineer, Hofwams
Dec 2024 to now, Remote, part-time
Lead the build of an event platform used by over 100 organizers: Stripe Connect payouts, a race-safe credit ledger, QR check-in, and the web and admin apps.
Backend Engineer, Asoebi Africa
2023 to 2025, Lagos
Rewrote a messy, outdated NestJS e-commerce API before launch while its endpoints stayed live. Made Paystack payments reliable: stored webhooks, retries, no double charges, post-payment work in a background queue. Cut search latency from 800ms to 350ms.
Backend Engineer, RunIt
2022 to 2023, Lagos
Logistics backend in Django, built from scratch. A Haversine rider-matching algorithm cut map API costs by about 30%.
Frontend Engineer, HostVille
2021 to 2022, Lagos
Built React and Next.js apps, with code-splitting, image optimization and caching for fast first loads.
About
I'm a product engineer who spends most of my time below the API line. I design the data model, the queues and the failure modes first, then build the product on top, usually in Next.js.
Most of what I build shares one shape. Hover or tap any part of it.
Hover or tap a node to see what I build there.
Correct before clever
Money never double-charges, tenants never see each other's data, and the invariant lives in the database write, not in a hopeful if statement.
Assume the network lies
Webhooks arrive twice or never. Every handler is idempotent, every queue retries, and a reconciliation job catches whatever still slips through.
Write the decision down
Architecture decision records with the load at which to revisit them, so the next engineer knows why, not just what.
Get in touch
Hiring for a backend or product engineer, or need a system that holds up once real users arrive? Tell me about it.