Favour
Max-Oti.
Web Experience Engineer
I build full-stack web applications that are fast, maintainable, and precise - from React frontends to NestJS APIs and the infrastructure in between. Five years shipping real products for real companies across Africa and beyond.
Builder, musician, systems thinker.
A dedicated space for the face behind the work, tuned to sit comfortably beside the engineering story.
I'm a full-stack engineer who cares equally about what the user sees and what runs underneath it.
My work spans the full delivery chain - React and Next.js frontends, NestJS and Laravel APIs, PostgreSQL and MongoDB data layers, and Docker-based deployments behind Cloudflare and Traefik. I've built SaaS platforms, e-commerce backends, and mobile apps, and I've taught backend development to the next generation of engineers.
I believe great engineering is invisible. It should feel natural, load instantly, and handle edge cases without drama. That conviction shapes every technical decision I make - from data model design to animation timing.
Sole engineer building and maintaining the company's SaaS platform - from database schema to deployment pipeline.
Teaching Node.js, Express, REST API design, and database fundamentals to students entering the industry.
Technical lead for client engagements - scoping requirements, providing IT support, and managing WordPress deployments.
Built and maintained the e-commerce backend and CRM integrations for a travel booking platform.
Contributed to backend system development using Node.js and GraphQL. First exposure to production-scale microservices.
Early-career role building React frontends and Laravel backends, plus client-facing technical support.
Open source is how I stay honest.
I treat open source as a way to practice engineering in public: clear code, useful defaults, better documentation, and small decisions that other people can inspect, reuse, or challenge.
The philosophy is simple: build things that lower friction for the next person. That might mean a starter API, a deployment pattern, a clearer README, or a tiny fix that saves someone else an hour of guesswork.
What I set out to achieve is not noise or vanity metrics. I want a body of work that proves I can collaborate in the open, explain tradeoffs clearly, and leave projects easier to understand than I found them.
Open to full-time roles, freelance projects, and interesting conversations about hard engineering problems.