Full-stack developer
Lagos --:--Remote
I’m Chijioke — a full-stack developer who designs the data model, builds the API, and sweats the interface. Below are products I took from idea to shipped.
(04)
The part people actually touch — built to survive real use, not just a demo.
Animation as structure rather than decoration: scroll, type and WebGL on one clock.
The API and the jobs behind it, including the unglamorous scraping and scoring.
Schema first. The model decides how much the next six months cost.
(06)
Swipe the work
012026
A storefront for my sister's handmade-footwear brand. Customers browse the catalogue, order made-to-measure pairs, and follow each one from the workshop bench to their doorstep.
022026
Scrapes listings across the web, scores each role against your skills and taste, then tracks every application from saved to signed.
032026
Turns a plain-language description of a screen flow into an editable diagram, checks it against a library of real app patterns, and flags the screens you forgot to design.
042026
A personal publishing platform end to end — admin dashboard, rich-text editor, and an email pipeline — built around one writer instead of an editorial team.
052026
Compresses phone photos on the spot and stitches them into a lightweight PDF. No account, no upload wall, just a file you can send.
062026
A wedding site with a real deadline — RSVP tracking, guest details, and a countdown — built for two people who aren't developers.
The order of things
It starts as a problem I actually have — a messy job hunt, a wedding with a deadline, screens I forgot to design.
Before a line of interface: what are the things, and how do they relate? This is the decision everything later is stuck with.
The contract, typed end to end, so the interface can never ask for something the data cannot answer.
Where it stops being records and starts being something you would actually use without a disclaimer.
On a real domain, with someone's money or someone's wedding riding on it. That part is not a detail.
(05)
01Engineering
Owning the schema, the API and the interface at once changes which decisions turn out to be expensive — and it is rarely the ones you budgeted for.
(who)
I like owning the whole picture — schema, API, and the interface on top.
My work usually starts as a problem I actually have — a messy job hunt, a wedding site with a deadline, screens I forgot to design. I build the thing, then sand the edges until it’s something I’d hand a friend without a disclaimer.
On the front I reach for React, Next.js, React Native and TypeScript; behind it, Python and FastAPI over PostgreSQL and MongoDB. I care about performance, honest copy, and interfaces that get out of the way.
