Raheem Kawojue

Logistics and commerce platform where backend correctness, money movement, and real-time operations all matter. I owned the system end-to-end: server, every web frontend, SDKs, architectures, and infrastructure, from early MVP through production scale as lead backend, then Head of Engineering, and now CTO and co-founder. The frontend fleet is 6+ production apps: waysdrop-admin, waysdrop-api-dashboard, waysdrop-affiliate, waysdrop-web, waysdrop-crm, and waysdrop-global-admin, plus partner portals and mobile wrappers for a total of 9 Amplify deployments. Led zero-downtime migration of all servers and databases from Railway to AWS: 4 RDS instances, 3 EC2 with 2 Elastic IPs, 2 Load Balancers, ElastiCache for caching, 2 Lambda functions with EventBridge Schedulers, 9 Amplify deployments, 2 ECRs, 3 CloudFront distributions, S3 for storage, 2 Secrets Managers, SES for email, and 2 WAF & Shield layers, everything instrumented with CloudWatch. Published 3 reference architectures on GitHub covering the location service, HTTP logger, and API key gateway, plus the courier matching algorithm writeup so the engineering decisions are legible, not just claimed. Authored 6 official platform SDKs in Dart, Node.js, Go, PHP, Rust, and Python so merchant and courier integrations ship in hours, not weeks. The AI layer is a production ops surface, not a demo chat box. A Claude/Qwen support agent with 80+ tools runs live on WhatsApp and Telegram and executes ops from a prompt. A notification decision agent chooses when and how to reach someone: push, email, SMS, or in-app, including new products, cart reminders, a nearby store, and holiday greetings. An activation and retention agent creates promos and pulls abandoned users back. Under that sit H3 geospatial courier matching, multi-rail wallets (Paystack, Nomba, Stripe, DVA, escrow), and 15+ Bull queues that keep delivery, payments, KYC, and webhook workloads moving outside request paths.

• Platform server (entire codebase)

  The ~5M-line NestJS monorepo I built end-to-end: services, domain models, auth, payments, matching, queues, WebSockets, webhooks, audit, and every internal API the frontends and SDKs call.

• Frontend apps × 6+

  Contributed to 6+ production web frontends: waysdrop-admin, waysdrop-api-dashboard, waysdrop-affiliate, waysdrop-web, waysdrop-crm, and waysdrop-global-admin — plus partner portals — all deployed to AWS Amplify.

• Support agent

  Claude/Qwen ops agent with 80+ tools on WhatsApp and Telegram. Users and staff prompt it; it executes across the platform.

• Notification agent

  Decision agent that picks channel, timing, and copy: push, email, SMS, or in-app. New products, cart reminders, nearby stores, holiday greetings, and the rest of the lifecycle.

• Activation & retention agent

  Brings abandoned users back. Creates promos, drives sessions, and decides what to say so people who left the app have a reason to open it again.

• AWS migration (zero downtime)

  Full stack migration from Railway to AWS with zero downtime. 4 RDS, 3 EC2 with 2 EIPs, 2 ALBs, ElastiCache, 2 Lambda + EventBridge schedulers, 9 Amplify deployments (all 6+ frontends + portals), 2 ECRs, 2 CloudFront + WAF/Shield, S3, 2 Secrets Managers, SES, CloudWatch across the board.

• Location service architecture

  Reference architecture and writeup for Waysdrop's geospatial location service: H3 courier matching, geofencing, real-time tracking, and high-throughput location ingestion on AWS.

  repo: github.com/kawojue/waysdrop-location-architecture
• Courier matching algorithm

  Multi-stage reactive pipeline for assigning deliveries to couriers: H3 res-7 spatial pre-filter on Redis SETs, parallel fleet/promotion/route matching via forkJoin, 3 allocation strategies (SEND_TO_ALL / NEAREST_ALL / NEAREST_ONE_BY_ONE), eligibility filters (decline cooldown, request caps, collection favorites), and Bull worker scheduling with 8 sequential stages from data prep through push notification dispatch.

  repo: github.com/kawojue/waysdrop-courier-matching-algorithm
• HTTP logger architecture

  Reference architecture for Waysdrop's distributed HTTP request logger: structured logging, correlation IDs, log aggregation on CloudWatch, and replayable audit trails across every service boundary.

  repo: github.com/kawojue/waysdrop-http-logger-architecture
• API key gateway architecture

  Reference architecture for Waysdrop's API key gateway: rotation, scoped permissions, rate limiting, audit logging, and SDK integration across all public merchant endpoints.

  repo: github.com/kawojue/waysdrop-api-key-architecture
• Platform SDKs × 6

  Official SDKs for Waysdrop's public API in Dart, Node.js, Go, PHP, Rust, and Python. Typed clients, auth helpers, retry policies, and release automation so integrations with merchants, couriers, and partners ship in hours instead of weeks.

Crypto payment infrastructure built so merchants can accept stablecoins without taking on wallet UX or custody complexity. Co-founded and built from zero: a merchant dashboard and gasless checkout on top of a NestJS API, backed by an audited smart-contract settlement layer across five EVM chains: Base, Polygon, Arbitrum, Optimism, and BNB. The contract layer covers direct and relayed checkout, no-wallet deposit addresses, reusable customer wallets, escrow with dispute resolution, ERC-20 subscriptions, programmable payments like vesting, timelocks, and threshold triggers, donation campaigns, and cross-chain swaps, all fee-metered through a central token registry with oracle safety checks. Deterministic CREATE2 factories give merchants and customers the same wallet address on every supported chain. Non-custodial throughout: funds settle directly to merchant wallets; Opsettle never holds them.

• Merchant dashboard & gasless checkout

  Merchant-facing dashboard plus hosted checkout for links, invoices, customers, and gasless payment flows on any supported wallet.

• NestJS payment orchestration

  Backend modules for payment intents, ledgering, webhook delivery with retry/replay, relayer coordination, and merchant-facing APIs.

• Settlement contract suite

  TokenRegistry, MerchantRegistry, PaymentSettlement, PayoutRouter, Escrow, SubscriptionManager, and ProgrammablePayments with oracle-backed fee checks.

• Identity, wallets & execution

  EIP-712 merchant consent, ERC-4337 account abstraction, deterministic CREATE2 wallets, no-wallet deposit addresses, and cross-chain swap routing.

Agricultural commerce platform built to move farmers and merchants from offline coordination into a safer, searchable, payment-backed marketplace. As CTO and co-founder in a three-person founding team, I owned backend architecture, built the NestJS backend with one colleague, paired on the Next.js customer and merchant frontends with another colleague, and single-handedly designed and shipped the admin dashboard. Users get a built-in wallet with bank transfers, card payments, and instant payouts via Paystack and Bull-driven payout queues, replacing screenshot-based confirmation with an auditable payout flow. Farmers and buyers chat directly inside the app to negotiate prices and share product specifications. An interactive map and geo-radius filter lets merchants source produce by distance and price. Real-time listings, price comparison, photo-based produce uploads, and verified buyer offers complete the commerce loop from listing to secure payment to delivery.

• Built-in wallet & payouts

  Secure in-app wallet with bank transfers, card payments via Paystack, and instant merchant payouts queued on Bull.

• In-app negotiation chat

  Direct chat between farmers and merchants: price negotiation, product spec sharing, and offer counter-signing on listings.

• Geo-radius discovery & maps

  Interactive map with geo-radius filtering so merchants source produce efficiently by distance and price.

• Listings, verified buyers & offers

  Farmers list produce with photos and pricing; verified buyers send offers; admins moderate the whole flow.

• Admin dashboard

  Built solo: user and listing moderation, payout operations, KYC review, dispute resolution, marketplace analytics, and super-admin controls.

Two-sided services marketplace connecting clients with professionals. As CTO I architected and delivered the backend from scratch: the full job lifecycle, escrow-based payments on Paystack (charges, transfers, webhooks), concurrency-safe wallet withdrawals, SSE job discovery with relevance ranking, in-app chat, KYC gating (NIN/CAC), and TOTP 2FA.

Cross-border e-commerce marketplace built on Payshiga's payment and wallet rails. I led product and backend: a multi-vendor catalog with HS customs codes, vendor-split checkout priced with live FX from Payshiga quotes, dual logistics providers (Shiip and Topship), HMAC-signed vendor sync from Payshiga business webhooks, and payment confirmation from Payshiga charge events queued through Bull.