Skip to content

Open to frontend rolesBased in Nigeria, working remotely

Gideon
Adeniran

Frontend engineer with 2+ years building web applications in React, Next.js and TypeScript: multi-role platforms, complex product workflows and reusable component systems.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • Turborepo
Local time WAT

About me

Hi, I'm Gideon

A frontend engineer with 2+ years of experience building multi-role platforms, complex product workflows and reusable component systems.

Tech Stack

I work in TypeScript across the React and Next.js ecosystem: multi-app Turborepo platforms, typed API clients and shared component systems. I have also shipped custom WordPress and WooCommerce builds.

I work remotely across most timezones

I'm based in Lagos, Nigeria, and work with remote teams.

Contact me

How I work

I care about code a team can keep working in: typed contracts between frontend and API, shared packages instead of copies, and conventions that are written down. I write up the decisions I make so the next person does not have to guess.

  • JavaScript
  • TypeScript
  • React
  • Next.js
  • Vite
  • Tailwind CSS
  • shadcn/ui
  • Radix UI
  • Material UI
  • Zustand
  • Node.js / Express
  • Turborepo
  • NX
  • Jest
  • React Testing Library
  • Git

B.Sc. Computer Science, Federal University of Technology, Minna · 2019 – 2025

Contact me

Selected work

Work & Experience

Six products, newest first, from multi-app platforms to a custom storefront. Open any folder for the full case file.

Recent workFrontend EngineerOct 2026 – PresentRemote · Lagos, Nigeria

IntelSpringsExperiential learning platform

A practice-first learning platform for students and professionals in finance, tax and related fields. Four Next.js apps for learners, instructors and administrators, built on a shared platform with a server-side session layer. I build the frontend on my own.

  • A backend-for-frontend proxy that keeps access tokens in httpOnly cookies and out of page scripts
  • A course builder with drag and drop, a constrained rich-text editor and autosave
  • Certificates with a server-rendered QR code and a public verification page
  • One Docker image recipe that builds and ships any of the four apps
Product
Practice-first learning for finance and business professions
Apps
Learner, instructor, institution admin, staff console
My focus
Session layer, course builder, certificates, release path
Ownership
Sole frontend engineer
Status
In development, pre-launch
  • Next.js 16
  • React 19
  • TypeScript
  • Turborepo
  • Tailwind CSS 4
  • TanStack Query
  • dnd-kit
  • Tiptap
  • Docker

Frontend EngineerOct 2026Remote · Lagos, Nigeria

ThatPurpleDotCustom WooCommerce storefront

A storefront for a fashion house with three brands that share one store, one bag and one checkout. I designed and built the custom theme and the commerce plugin behind it, with no page builder.

  • Theme for presentation, plugin for commerce rules: anything that must survive a redesign lives in the plugin
  • A shipping engine in plain PHP for Lagos areas, other Nigerian states and international zones
  • Brand rules enforced in the editor, quick edit, bulk edit and the REST API
  • Accessible dialogs, menus and accordions, tested in a real browser
Product
Three-brand fashion storefront
Build
Custom theme and commerce plugin
My focus
Architecture, shipping, brand rules, accessibility and tests
Status
Live
  • WordPress
  • WooCommerce
  • PHP
  • TypeScript
  • Vite
  • Tailwind CSS 4

Frontend EngineerSep 2026Remote · Lagos, Nigeria

SandwichMulti-application job board and HRMS frontend

A recruitment and HR platform: a candidate job board, an employer hiring workspace and an HR management app, all in one Turborepo. I built the frontend: the shared packages the apps stand on, the data table, the API and cache layer, and the portals themselves.

  • Shared UI, API-client, query, utility and security packages used by every Next.js app in the repo
  • A data table with client, server and cursor pagination behind one API
  • Retry rules by status code, and cancelled requests that are never mistaken for server errors
  • Cursor paging and cache patching so pipeline changes show at once without flicker
Product
Job board, employer ATS and HRMS
Apps
Candidate, employer, HRMS, admin, two marketing sites
My focus
Shared platform packages, data table, API and query state
Ownership
Sole frontend engineer
  • Next.js 16
  • React 19
  • TypeScript
  • Turborepo
  • Tailwind CSS 4
  • TanStack Query
  • OpenAPI codegen
  • zod

Frontend EngineerJun 2026Remote · Lagos, Nigeria

FilmporteFilm distribution platform

A pay-per-view platform where independent filmmakers publish, price and premiere films, and audiences buy tickets and watch protected streams. I worked on the film page architecture, region-aware pricing and playback reliability.

  • Split a 953-line client-side film page into a server-rendered shell with small client islands for the player and checkout
  • Region-aware pricing with request types that make an invalid payload a compile error
  • Fixed playback failing to resume after a page refresh
  • Entitlement, ticketing and gift-voucher flows that survive sign-in and stale data
Product
Pay-per-view cinema for independent film
Apps
Viewer, producer dashboard, admin, landing
My focus
Film page architecture, pricing, playback and tickets
Team
Wider frontend team, alongside a senior engineer
  • Next.js 15
  • React 19
  • TypeScript
  • TanStack Query
  • Zustand
  • zod
  • Mux Player
  • Tailwind CSS

Frontend EngineerMar 2026Remote · Lagos, Nigeria

PZ NexaConsultancy website with a headless CMS

The website for an African market strategy and advisory firm. I built it end to end in Next.js and connected it to Sanity, so the team publishes strategies and insights without a developer, with newsletter issues pulled in from Substack.

  • Sanity CMS with an embedded Studio at /studio, typed schemas and generated query types
  • Strategy and insight pages served from the CMS, refreshed daily, with paging that keeps filters in the URL
  • A one-command migration that moved the existing hard-coded content into the CMS
  • Newsletter issues fetched from Substack in validated batches that stay under Next.js cache limits
Product
Strategy and advisory consultancy site
Content
Sanity CMS and Substack
My focus
Build, CMS connection, content model, design system
Ownership
Sole frontend engineer
  • Next.js 16
  • React 19
  • TypeScript
  • Sanity
  • GROQ
  • Tailwind CSS 4
  • zod
  • Motion

Frontend EngineerFeb 2026Remote · Lagos, Nigeria

BamBamLoadMulti-application e-commerce SaaS

A B2B marketplace for sand and building materials in Nigeria, run as one Turborepo of Next.js apps for buyers, suppliers, admins and the public site. I built supplier and admin management workflows and the table and modal patterns they share.

  • Shared data table with a server-pagination mode, matching loading skeletons and tooltips that show only when text is cut off
  • Product, order and team modals on parallel and intercepting routes, so every modal has its own URL and still opens over the list
  • A delete flow that turns into an archive recommendation when a product is tied to existing orders
  • One typed ROUTES object and one zod schema convention across the buyer, supplier and admin apps
Product
B2B building-materials marketplace
Apps
Buyer, supplier, admin, public website
My focus
Supplier and admin workflows, shared table and modal patterns
Team
Small team, alongside a senior engineer
  • Next.js 16
  • React 19
  • TypeScript
  • Turborepo
  • Tailwind CSS 4
  • TanStack Query
  • TanStack Table
  • zod

Internal tools

Built for the team

Tools I made to make day-to-day work on large frontends calmer. The first one answers a question every team building against a moving backend keeps asking: what actually works right now?

v1.0.0TypeScriptNext.jsTurborepoClaude Code plugin

integration-status

One typed source of truth for what the frontend can actually do against the backend.

A small package for JavaScript and TypeScript monorepos. Every app's screens and every ask to the backend live in one typed data file. From that data it generates a markdown report that lint keeps current, and a status page each app can serve behind a flag.

In use in two client monorepos, across eight Next.js apps. Packaged as a Claude Code plugin.

localhost:3000/integration-status

Candidate app

Updated 2026-01-15 · staging backend

  • 12

    Connected

  • 6

    Partly connected

  • 2

    Ready to wire

  • 3

    Blocked

  • 4

    No backend

ModulesOpen asksClaimed
  • Sign in and OTPAccountConnected
  • Job searchJobsConnected
  • ProfileAccountBlocked
  • Saved jobsJobsPartly connected
  • MessagesInboxNo backend
BugOpenHigh · logged 2026-01-15

Profile update fails with a 500

Where
PATCH /api/users/me · /settings/profile
What
Accept a partial body on PATCH /api/users/me. Today any request without phone returns 500.
Why
People cannot change their name or photo without also re-entering their phone number, and the error gives them no hint.
Illustrative data

01The problem

  • Several Next.js apps were being built against a backend that was still being built too.
  • Nobody could say quickly which screens really worked against staging and which were still on mock data.
  • Backend issues were spread across chats, tickets and memory, often without the endpoint, the exact request or the reason it mattered.
  • A hand-written status doc helped, but it went out of date as soon as someone forgot to edit it.

02The idea

  • Treat integration status as data, not prose: one typed package lists every module and every ask.
  • Each ask says where (endpoints, screens), what (the exact request) and why (what it breaks for people).
  • Generate the doc and the status page from that same data, so they cannot disagree.
  • Make lint fail while the generated doc is out of date.

03What it gives a team

  • One answer to 'what is connected?', for every app, in a page you can open in a meeting.
  • Backend engineers get precise asks, grouped by priority, with a button that copies one as a ticket.
  • A claimed fix stays unconfirmed until someone has measured it on staging.
  • Typos fail the build: duplicate ids, links to unknown asks and missing dates are rejected.

Contact

Let's talk

Hiring for a frontend role, or have a product to build or improve? Send a note and I'll get back to you.

Open to frontend roles

Usually replies within a day.

Email

Based in
Lagos, Nigeria
Local time
WAT