Full-stack developer
Web · Mobile · Systems
I build the whole system — the screen you tap and the server that answers it. Six layers deep, one developer.
Component systems, design tokens and motion — built once, shared across web and native. Accessibility lives inside the component, not in a later cleanup pass.
State machines, validation and domain logic that live in one place and stay honest — the same rules running on the client, on the server, and in the test suite.
Typed endpoints, versioned contracts and real auth. REST where it fits, GraphQL where it earns its keep, WebSockets when the data cannot wait for a refresh.
Relational where it matters, document where it helps. Indexes chosen on purpose, queries measured before they ship, and caches that expire exactly when they should.
Containers, pipelines and monitoring so releases stop being events. If it is not observable it is not finished — logs, traces and alerts ship with the code.
Every project below is shown as a core sample — a vertical slice through the stack, marked with how deep I actually went on each one.
An online Quran academy for UK families. Course booking, a student learning portal, and a 2,500-page Quran library — all run from one headless CMS.
Driver-side delivery app with offline queueing, live route updates, and a dispatch console operators actually like using.
Support desk with SLA timers, routing rules and a full audit trail — built for the messy cases teams hit in week three.
A lightweight event SDK and the ingest pipeline behind it. Batched, retried, and honest about what it drops.
Hiring for a team? Email is the fastest way in. Have something to build? Send the details — I reply to everything.