Selected work, with context.

Replacing scattered vendors with one trustworthy stack.

Engineering teams across the company were each integrating their own email, SMS, push, and in‑app providers — paying for overlapping vendors, writing the same retry and templating logic from scratch, and operating each integration independently. I designed and led a centralized notification platform: a multi‑tenant Go service with a typed template registry, Asynq‑backed queues, and a small Next.js console for operators.

The hard parts weren’t the channels — they were the boundaries. Per‑tenant rate limits, idempotency keys that survive provider retries, audit logs engineers can investigate, and a migration path that let teams move one event type at a time. We landed on a service that product and marketing teams could both trust, and the failover plus suppression handling improved delivery reliability by about 18%.

Moving teams from third-party tooling to an internal service.

Before adopting the File Management Service, most teams and products relied on a third-party platform for uploads and delivery. Other implementations were fragmented across products, with inconsistent storage patterns and no standard direct API-to-API integration for service workflows.

I led the design and build of a multi‑tenant file management service that gave teams one owned integration surface for uploads, signed URL issuance, virus scanning, lifecycle policies, and CDN-backed delivery.

The platform shipped with strict tenant isolation, predictable URL semantics, direct API-to-API access, and an upload SDK that made the secure path the easy path. Teams could migrate from the third-party platform and consolidate fragmented implementations behind the shared service, reducing third-party costs and removing duplicated code. For customers, it provided a delivery layer fast and dependable enough for product-facing assets.

Supporting 30+ payment methods while targeting 99.99% reliability.

I worked on a multi-market, multi-currency checkout that helped individuals, businesses, and multinationals accept payments from customers globally through more than thirty payment methods. Each market introduced different regulatory requirements, processor behavior, currency rules, payment preferences, and customer expectations, while the checkout still needed to feel like one coherent product.

I led work on payment method orchestration, fallback logic, multilingual experiences, and the runtime state machine that holds a transaction together while a user moves between providers. A modular architecture allowed us to introduce new markets, currencies, and payment methods without turning the checkout into a collection of one-off flows.

The work expanded merchant payment options while moving toward a 99.99% payment reliability target. It also contributed to stronger customer retention and revenue growth by making the checkout more relevant across currencies, payment preferences, and customer contexts.

Making Nigeria’s historical record easier to preserve and explore.

Much of Nigeria’s newspaper history has remained difficult to access: physical copies deteriorate in libraries, and finding a particular story can require travelling to an archive without knowing whether the right publication or date is available. Archivi.ng turns that uncertain, time-consuming process into an experience anyone interested in Nigerian history can begin with a few clicks.

As Lead Product Engineer, I shape the public experience across 75,000+ pages of historical material: search, advanced filtering, collections, editorial storytelling, and Context by Archivi.ng, an AI-assisted tool that helps people make sense of the archive through source-cited answers. The product serves researchers and journalists, but also students, educators, and anyone curious about Nigeria’s past.

The user-facing product rests on a core archiving operations pipeline. Our work spans collecting physical newspapers, cataloguing and scanning them, processing and uploading the resulting pages, attaching useful metadata, and making the material searchable and accessible online. Building both the operational system and the discovery experience has required careful product decisions across preservation, data quality, search, and trustworthy AI-assisted interpretation.