The practice / software engineer

I keep this page in sync with what I have actually shipped.

Software engineer in Nigeria building backend systems for fintech, payments, and data products. I take software problems from initial requirements through architecture, implementation, and production deployment.

Quick facts

Role
Full-stack software engineer
Based in
Nigeria, working with clients remotely
Available for
Freelance, contract, and consulting

What I actually do

I work across the full stack: React frontends, C# and Python backends, PostgreSQL databases, and Linux infrastructure on AWS. For fintech and payment teams, I focus on clear APIs, safe integrations, and production systems that are easy to operate.

Recent work has a strong AI and data component: RAG pipelines with local embedding models and vector databases, LLM integrations for document analysis, and privacy-preserving alternatives to cloud-dependent tools. I apply OWASP security practices throughout, from input validation and authentication to server hardening and security headers.

I can join a team for a specific build, take a product from zero to launch, or improve an existing system. I prefer projects where engineering quality matters and where there is a real problem to solve, not a feature to check off.

Areas of expertise, with proof

Each claim is backed by a shipped system.

  1. 01

    RAG pipelines and AI-powered tooling

    Retrieval-augmented generation end to end: crawling and ingesting source data, chunking and embedding with local models, vector storage and retrieval, reranking, and LLM synthesis with cited output.

    Proof / Reddit Research Tool
  2. 02

    API tooling and developer experience

    Developer-facing tools that respect time and data: offline-first storage, non-blocking background processing, and testing interfaces that avoid the usual CORS friction.

    Proof / YASP
  3. 03

    Production-safe infrastructure tooling

    Deployment and operations tooling designed around failure recovery: automatic rollback, integrity verification, and dry-run modes for anything that touches production.

    Proof / WinService.Deploy
  4. 04

    Privacy-first, local-first software

    Tools where sensitive data never leaves the user's device or network, without giving up the polish of a hosted alternative.

    Proof / PDF Read Aloud

Fintech and payments

Payment flows need clear states and recoverable failures.

A successful request is only one state. Teams also need explicit handling for retries, duplicate webhooks, timeouts, rejected requests, and the investigation that follows. I do not present a shipped payment product on this site. The proof is adjacent: API governance, failure-safe deployment, real-time data pipelines, and privacy-first applications.

Have a project

Built, improved, or shipped.

Send a brief description of what you are building and I will get back to you promptly.

Email me