Skip to content
FOA.

Open to full-stack and AI engineering roles

Falola Olufemi Adedeji

I build products where being wrong is expensive — and I hold model output to the same standard.

Full-stack engineer with five years shipping user-facing products across fintech, edtech, and consumer SaaS. Frontend architecture in React, Next.js, and React Native; backend in Go, Node.js, and NestJS. The through-line is the part nobody demos: explicit states, honest error surfaces, and claims a reviewer can check instead of taking on trust. Now applying that standard to AI, where a statistics degree turns out to be the useful half.

See selected workRésumé
Faster page loads
25%
RevHero frontend rearchitecture
Fewer re-renders
30%
Scholé state-management overhaul
Faster data retrieval
20%
Scholé admin dashboard
Engineers mentored
3
Frontend lead at Scholé

Figures from named engagements. Nothing aggregated.

01 — Selected work

Four engagements, in depth.

Fewer projects, described properly. Each entry says what the product is, what I actually did, and where the numbers come from.

01

Finaive

Frontend, then Full-Stack Engineer (Contract)

Jan 2024 — Present

finaive.com

AI-assisted escrow marketplace, web and mobile

An escrow marketplace of verified sellers, with an AI shopping assistant that helps buyers find and vet them.

Started as lead frontend — secure transaction workflows, dispute and status tracking, the dashboards on top of them, and complex UI on the React Native app. Since mid-2026 I work across the whole stack: Postgres schema and migrations, Supabase edge functions, and the Next.js app. Built the interface for the AI shopping assistant, including billing that warns a buyer before a new search is charged and says plainly when a failed one wasn't.

  • Next.js
  • TypeScript
  • Supabase
  • PostgreSQL
  • React Native
“Femi's work on our AI-powered escrow platform exceeded all expectations. His ability to translate complex business requirements into elegant technical solutions is remarkable.”
Uwabor Henry — CEO, Finaive

02

Scholé Labs

Lead Frontend Engineer

Jun 2024 — Sep 2025

scholelabs.com

Multi-role school management dashboard

One dashboard serving three distinct audiences — administrators, teachers, and students.

Frontend lead: set development strategy, enforced performance and code-quality standards, and mentored three junior engineers. Spearheaded the core dashboard from wireframes to production, then reworked client-side state with Redux Toolkit and React Query to cut redundant fetching and render churn.

Faster data retrieval
20%
Admin dashboard
Fewer re-renders
30%
State-management rework
Engineers mentored
3
Frontend team
  • Next.js
  • React
  • Redux Toolkit
  • React Query
“Working with Femi has been outstanding. He not only writes clean, maintainable code but also mentors junior developers effectively. His leadership on our dashboard project was instrumental to its success.”
David Oluwaloni — CEO, Scholé Labs

03

RevHero

Frontend Engineer — direct, then via RevStar Consulting

Jun 2025 — Sep 2026

Ground-up UI redesign and frontend rearchitecture

A revenue platform whose interface had outgrown its original structure.

Led a full UI redesign and rebuilt the frontend on React, Next.js, and TypeScript — replacing ad-hoc styling with a responsive design system that improved usability and accessibility. Partnered with product and UX to keep the visual direction anchored to user feedback, and drove consistency across product modules.

Faster page loads
25%
Frontend rearchitecture
  • React
  • Next.js
  • TypeScript
  • Design systems
“Olufemi transformed our entire frontend architecture. His expertise in React and Next.js helped us achieve a 25% improvement in load times.”
Viktoryia Dainiak — Product Manager, RevHero

04

Reals SPV

Frontend Developer

2023

realsspv.com

Data-plan purchasing with live payment flows

A consumer platform for buying mobile data, wired to payment gateways and third-party vendors.

Built the responsive web platform and integrated payment gateways alongside third-party data-vendor APIs. Focused on the unglamorous part that decides whether a payment product works: explicit transaction states, honest error surfaces, and feedback that tells the user exactly where their money is.

  • React
  • Redux Toolkit
  • Payment gateways

Code you can read

ledgerpay

Go · PostgreSQL · personal project

A payments API built around a double-entry ledger, to get the parts of money movement right that are invisible when they work and unrecoverable when they don't. Not production card rails — a study of the correctness patterns real payment systems depend on.

  • Double-entry ledger with overdraft protection enforced by row-level locking (SELECT … FOR UPDATE)
  • Idempotent charge retries keyed on client tokens, so a repeated request cannot double-charge
  • Transactional outbox for event delivery — no lost webhooks if the process dies mid-write
  • HMAC-SHA256 signed webhooks with retry and dead-letter handling
  • Runs as five services under Docker Compose, with CI on every push

Go · PostgreSQL · Docker · GitHub Actions

Live demoRead the source

dispute-triage

Python · Amazon Bedrock · personal project

An LLM classifier for payment disputes, built the other way round: calling the model is the easy half, so the project is really the evaluation harness that decides whether its output is good enough to act on. The best prompt scores a perfect macro F1 — which the repo reports as a problem rather than a result, because a benchmark everything passes has stopped measuring anything.

  • 90 hand-written labelled disputes across six categories, with tests that fail if a class thins out or the deliberately ambiguous cases go missing
  • Precision, recall and F1 implemented rather than imported, and macro-averaged — the rare classes are the expensive ones to get wrong
  • Off-format and unparseable answers are scored as wrong, never quietly dropped; only an exact label token is accepted
  • Two prompt versions scored on the same set, with a diff that names the individual cases whose verdict moved
  • A zero-cost keyword baseline runs in CI, so the harness and its regression gate are exercised on every push without credentials
  • Paid runs estimate their spend up front and refuse to exceed a cap, and a failed sweep retries only the cases that failed

Python · Amazon Bedrock · pytest

Read the source

Also shipped

  • FridayApis

    Server-rendered frontend for a developer API platform. Integrated cryptocurrency, translation, and currency-exchange services with resilient error handling; improved initial load performance and SEO.

    Next.js · SSR · REST APIs

02 — Experience

Where the work happened.

One current engagement: a long-running part-time contract with stated hours. Everything else is closed out with real end dates.

  • Jan 2024 — Present

    Current

    ~10 h/week

    Frontend, then Full-Stack Engineer (Contract)

    Finaive·Lagos, NG / MD, USA

    • Work across the full stack since July 2026 — Postgres schema, Supabase edge functions, and the Next.js app — shipping features including service requirements agreed before payment rather than after, buyer Trust Profile verification, and dashboard rails that adapt to how experienced a buyer is.
    • Write and apply schema migrations paired with down-migrations, so changes ship with their rollback.
    • Built the interface for the platform's AI shopping assistant: TrustScore-ranked sellers returned as cards inside the chat, and per-search credit billing that shows the balance, warns before a new search is charged, handles an insufficient balance, and tells the buyer when a failed search wasn't charged.
    • Led frontend development from 2024 — secure transaction workflows, dispute and status tracking, the migration from Vite to the Next.js App Router, and complex UI and critical fixes on the React Native app.

Earlier

  • Oct 2025 — Sep 2026

    Full-Stack Engineer (Contract)

    RevStar Consulting·Tampa, FL

    • Delivered features end to end across frontend and backend layers within a cross-functional consulting team of engineers, AI engineers, and product managers.
    • Assigned to RevHero — continued the frontend work started under a direct contract, after the engagement moved onto RevStar.
    • Supported integration, testing, and release activities to keep production deployments stable.

  • Jun 2025 — Oct 2025

    Frontend Engineer

    RevHero·Tampa, FL

    • Led a ground-up UI redesign, introducing a responsive design system that improved usability and accessibility.
    • Rebuilt the frontend on React, Next.js, and TypeScript — improving maintainability and cutting load times by over 25%.
    • Partnered with product managers and UX designers to align the visual direction with user feedback and business goals.
    • Engagement continued under RevStar Consulting from October 2025.

  • Jun 2024 — Sep 2025

    Lead Frontend Engineer

    Scholé Labs·Lagos, NG

    • Set frontend development strategy, mentored 3 junior engineers, and enforced code-quality and performance standards.
    • Spearheaded the core school management dashboard for administrators, teachers, and students — improving data retrieval time by 20%.
    • Implemented state management with Redux Toolkit and React Query, reducing application re-renders by over 30%.

  • Sep 2023 — Dec 2023

    Frontend Engineer (Contract)

    FridayApis·Remote

    • Built and maintained SSR applications with Next.js for a developer-focused API platform, improving initial load performance and SEO.
    • Integrated cryptocurrency, translation, and currency-exchange APIs with resilient data handling.

  • Aug 2021 — 2023

    Freelance Web Developer

    Self-employed·Remote

    • Designed and built custom sites and applications for small businesses and personal brands.
    • Owned the full lifecycle: requirements, client communication, timelines, and deployment.

03 — Current focus

Taking product engineering into AI.

I'd rather show you what I'm learning than imply I've already mastered it. This is what's actually on my desk right now.

  1. 01In progress

    AWS generative AI certification

    Working through the AWS generative AI certification track — foundation models, prompt engineering, retrieval-augmented generation, and the Bedrock service surface, alongside the AWS and Docker fundamentals that give it somewhere reliable to run.

  2. 02Active

    A statistics degree, pointed at AI systems

    My degree is in statistics, which turns out to be the useful half of this move. Sampling, inference, and experimental design are what separate a model that demos well from one that holds up — and they apply at the application layer, not just in training.

  3. 03Next

    Evaluation over impressions

    Working toward labelled evaluation sets, precision and recall reported per class, and prompt versions scored against each other rather than eyeballed. Calling a model is the easy half; proving its output is dependable is the part worth being good at.

  4. 04Active

    AI features in production products

    At Finaive I built the interface for its AI shopping assistant — ranked results inside the chat, and billing a buyer can trust: a warning before a search is charged, and a clear message when a failed one wasn't. The next step is the evaluation behind it.

04 — About

How I work.

I started in graphic design, moved into frontend because I wanted the things I designed to actually run, and ended up owning full-stack delivery. That route left me with a bias I still work from: the interface is where a product either earns trust or loses it.

Most of what I've shipped lives in domains where being wrong is expensive — escrow payments, school records, data purchases. So I care disproportionately about the parts nobody demos: explicit loading and error states, honest empty screens, and messages that tell a user where their money or their data went.

I've led a small frontend team, which mostly taught me that setting a readable standard and reviewing against it beats being the person who writes the most code. I'm now pointing all of that at AI engineering, because the interesting reliability problems have moved there.

My degree is in statistics, which sat quietly under the product work for years and has become the most useful thing I have for that move. The hard part of shipping AI isn't calling the model — it's knowing whether the output is actually good, which is a measurement problem before it is an engineering one.

Credentials

  • Generative AI certificationAmazon Web Services · In progress

Education

  • B.Sc. StatisticsFederal University of Agriculture, Ogun State · 2023
  • NCE, Computer Science / MathematicsFederal College of Education, Ogun State · 2017

Based in

Lagos, Nigeria · WAT (UTC+1)Same working hours as Berlin, Paris, and Amsterdam — full overlap with European teams, and afternoons overlap with US Eastern.

Stack

Languages
TypeScript, JavaScript, Go, Python
Frontend
React, Next.js, React Native, Redux Toolkit, React Query, Tailwind CSS
Backend
Node.js, NestJS, Supabase, Express, REST APIs
Data
PostgreSQL, MongoDB
Platform
AWS, Docker, Git, CI/CD
AI (learning)
Amazon Bedrock, RAG, Prompt engineering

05 — Contact

Let's talk.

I'm open to full-stack and AI engineering roles, and to project work where the problem is interesting. Either form below reaches me — the direct email is faster.

Availability

Lagos, Nigeria · WAT (UTC+1)Same working hours as Berlin, Paris, and Amsterdam — full overlap with European teams, and afternoons overlap with US Eastern.