Muiz Oyebowale
I build the parts nobody sees, and that's exactly how I like it. I've got your backend.
not all heroes wears cape, some quietly build infrastructure that keeps working when it matters.
Who is this?
A backend engineer who cares about the parts of a product that only get noticed when they break. I build APIs, data pipelines, payments, and queues. I keep them reliable, correct, and boring, so nobody has to think about them. And I'm pointing the same attention at AI and ML.
Selected work
Projects as case studies.
All projectsGalleria: Event Photo Sharing Powered by Face Recognition
2026 · completeAn event photo platform where attendees scan their face once and get back only the photos they're in, built on RetinaFace detection, ArcFace embeddings, and an async Celery pipeline that processes uploads at scale.
Settle: Payment Collection Infrastructure for Nigerian SMEs
2026 · completeA virtual-account payment collection platform built on Nomba's APIs, with automatic per-customer reconciliation, calendar-correct recurring billing, and a developer API the dashboard itself runs on.
Flint: Background Job Scheduler Built From Scratch
2026 · completeA priority-queue job scheduler with DAG workflows, retry backoff, a dead letter queue, and real-time updates, with no Celery and no external broker.
Career
Where I've done this.
HNG Internship, Anvila & Insighta Labs
InternshipTech Lead / Backend EngineerApr 2026 to Jun 2026
Tech lead over an 11-engineer backend and frontend team building Anvila, an AI-agent manifest generator, shipped in under a month. Alongside that, built Insighta Labs solo: a demographic-intelligence API with dual OAuth and a rule-based natural-language query parser.
- Led both backend and frontend delivery. 4 backend engineers, 7 frontend, while remaining the top individual contributor on the frontend myself.
- Owned database design across the entire team; every engineer extended schemas I originally built, keeping the data layer consistent as the team scaled.
- Built the prompt-to-manifest generation pipeline and its event-publishing layer. The path that turns a user's prompt into a set of customized AI-agent manifest files. 30+ manifests generated in production use.
- Owned all frontend-to-API integration and built several of the marketing pages.
Taskingdom
ContractBackend DeveloperJul 2025 to Jan 2026
Task-based gaming platform with real-money payouts. Four distinct user roles (regular, VIP, business, influencer), strict permission boundaries, and abuse-prevention logic that had to survive both ephemeral and long-lived tasks.
- Designed the abuse-prevention layer: a hybrid Redis-TTL + join-table storage strategy that prevented reward farming across task resets, regardless of whether tasks were short-lived or non-expiring.
- Built the webhook layer linking third-party game outcomes to internal payouts. Game ends, condition checks, reward fires, all idempotent.
- Co-designed core schemas (user, task, reward, role) and the permission system that enforces what each user type can see and do.
- Moved heavy operations onto Celery workers behind Redis. User-facing endpoints stopped paying for image processing and external API roundtrips.
Meerge Africa
ContractBackend EngineerDec 2024 to Jul 2025
Multi-service food commerce platform connecting vendors, suppliers, and delivery operations. I owned the Supplier service end to end and stepped in as acting lead when the engineering lead left.
- Designed and led the Supplier service from scratch: supplier lifecycle with four explicit states (pending, approved, rejected, suspended), full audit logging, and admin tooling. 500+ suppliers, ~50 products each at pilot.
- Acted as backend lead for 8 weeks across a 7-engineer team. Reviewed architecture decisions, unblocked contributors, kept shipping. Also designed scoped JWT for safer service-to-service calls.
- Refactored bare-except blocks and swallowed exceptions into structured error handling with consistent response shapes and full logging. Silent failures became traceable, on-call became less painful.
- Reviewed PRs across all three backend services (Supplier, Delivery, Kitchens), keeping conventions consistent across an evolving codebase.
HNG Internship, Sitelytics
InternshipBackend EngineerOct 2025 to Dec 2025
Finalist in a globally competitive engineering internship, contributing to Sitelytics, a website analysis platform for non-technical users. Selected among ~309 finalists from 22,000+ interns.
- Built the Admin system from scratch as sole contributor: role-based access control, user monitoring, scan tracking, admin-managed content.
- Built the platform notification system end to end (retrieval, deletion, email delivery) and the helper utilities that standardized notifications across services, removing the inconsistent handling that existed before.
- Contributed to the async website-scanning pipeline using background workers and Server-Sent Events for real-time scan progress in the UI.
- Reviewed code across a 15-engineer backend team; held the bar on consistency during fast iteration. Acted as temp team lead for one sprint.
stack
The tools I reach for.
Languages
Frameworks
Data
Infra
Writing
Notes from the field.
All writingThe Art of Git Is Dying
Commits used to tell the story of how software got built, funny messages and all. Now a whole feature lands in one commit with thousands of lines, and git has quietly turned into a sync button for GitHub instead of a record of how the work actually happened.
Why I Built My Own Rate Limiting Library for FastAPI
I was using SlowAPI for rate limiting in a FastAPI project and kept running into the same friction points. So I built fastlimit: here is what bothered me and what I did about it.
My Experience With HNG: Two Tasks That Stuck With Me
Looking back at two tasks from the internship, one solo backend stage on Insighta Labs and one team project called Anvila, that ended up being harder than expected, and what I actually walked away with.
Contact
Let's build something that has to work.
I'm open to backend engineering roles. Production systems, APIs, and data pipelines that have to stay up. A good conversation about systems works too.