I'm a senior software engineer with eight years designing and shipping systems across payments, compliance, conversational AI, e-commerce, and logistics.

Currently building the engine room of a modern payments stack at Paymid Limited — intelligent gateway routing, PCI-DSS-compliant integrations, failover orchestration, and the dashboards that make all of it observable.

I work end-to-end — schema → API → UI → deploy → on-call — and I optimise for the engineer reading this code in two years.

Architected an intelligent gateway-selection system: automated failover, load balancing, smart retry logic, real-time transaction optimisation, and a gateway health-monitoring dashboard.

Measurable lift in payment success rates across web and mobile checkout. PCI-DSS compliant.

_{↑   PAYMENT SUCCESS RATE 15+   GLOBAL GATEWAYS PCI-DSS   COMPLIANT WEB  +  MOBILE   CHECKOUT}

Transformed a single-tenant compliance platform into a multi-tenant architecture — preserving data isolation and per-tenant configurability while unlocking scale across enterprise clients.

_{saas   architecture   migration}

Built aggregation pipelines extracting actionable insight from Statements of Work, vendor audits, and third-party feeds using NLP-driven analysis. Five high-impact features shipped end-to-end.

_{nlp   automation   aws}

Centralised onboarding & compliance dashboard with regulatory-grade auditability. Introduced an express onboarding journey that reduced user friction without sacrificing rigour.

_{kyc   compliance   dashboards}

Real-time conversational sync across Messenger, WhatsApp, Telegram, Facebook posts/comments, and Web — with seamless human handover and a Web SDK for third-party embedding.

_{chatbot   socket.io   omnichannel}

Clarity second. Cleverness last.

In regulated domains the cost of being clever exceeds the cost of being boring. Optimise for the engineer reading this code in two years.

Every dependency will fail.

Designs assume failure. Observability proves it. Runbooks operationalise it. Pagers stay quiet because the system catches itself.

Schema · API · UI · deploy · on-call.

The handoff between layers is where bugs live. I follow features end-to-end, then keep showing up when production behaves strangely.

I'm open to thoughtful conversations about payments infrastructure, compliance tooling, multi-tenant architecture, and senior individual-contributor / staff engineer roles.

If you're building in any of those spaces and want a second pair of hands on the system, the fastest paths to reach me are over →