Loading
Oluwaseun David Ajiboye, software engineer. I design and build complete products: the interfaces people use, the APIs and data behind them, and the servers they run on.
Open to engineering opportunities
Move to x-ray · Scroll to see inside ↓
(01) Approach
I take products from a rough idea to live in people’s hands. Interfaces that feel effortless, APIs that make sense, data that stays correct, and the deploy that ships it. Every layer, one engineer, so nothing gets lost in the handoff.
(02) Selected work
Ten products across payroll, hospitality, health, media and commerce, each built end to end. Every case study covers the problem, what I built, and where it stands today.
Workforce and payroll workflows need clear tenant boundaries and a reliable history of sensitive changes.
I built the application backend, including tenant isolation, scoped access, maker-checker approvals, effective-dated compensation data, and durable outbox/inbox processing.
Customers needed a straightforward way to discover chefs, arrange bookings, and place shop orders.
I delivered the full-stack application, including booking and shop flows, server-derived prices, Paystack payment verification, retries, and transaction status reconciliation.
Issuers need to create credentials in batches and give recipients a way to verify them later.
I built a visual credential editor, asynchronous batch-issuance flows, and cryptographic signing and verification features.
(03) Why me
Most products stall in the gaps: between design and build, frontend and backend, “it works on my machine” and live. I close those gaps by owning the whole thing, and I build each layer like it's the one that matters most.
What you get
Interface, API, data and deployment come from the same head, so nothing gets lost between handoffs and nobody waits on another team.
Fast, responsive and accessible, with motion where it earns its place. You’re scrolling through the sample right now.
Payments verified on the server, reviews for sensitive changes, retries and history where they matter. The unglamorous parts, done properly.
Clear scope, honest status at every step, and documentation the next engineer can actually use.
(04) Capabilities
Bring me a napkin sketch, a half-built app, or a workflow your team has outgrown. I'll help shape what's worth building, then design, build and launch it across every layer.
What I do · 01 / 05
From a rough idea to something live in people’s hands. I shape the first release with you, then design and build every part of it: screens, APIs, data model and deployment.
What I do · 02 / 05
Fast, responsive, accessible frontends with the polish that makes a product feel considered: thoughtful motion, rich editors, even WebGL when it earns its place, like this site.
What I do · 03 / 05
APIs and data models that mirror how the business really works: multi-tenant access, approvals for sensitive changes, effective-dated records, background jobs and events that survive retries.
What I do · 04 / 05
Wire the outside world in safely: Paystack and Flutterwave with server-side verification and reconciliation, WhatsApp messaging, AI with structured outputs and human handoff, signed proofs.
What I do · 05 / 05
Content and admin tools that let clients publish, manage and operate without calling an engineer, then a clean deploy on infrastructure that’s easy to hand over.
(05) Process
I start with the problem, the people affected, and the constraints around the work.
I clarify the requirements, tradeoffs, scope, and milestones before implementation.
I map the main user and system workflows before committing to an implementation.
I implement the agreed features with attention to validation, maintainability, and the needs of the system.
I check important user journeys and edge cases, then address issues found during review.
I prepare the software for its next environment and document relevant handover and operating steps.
(06) Tools of the trade