Engineering Work
Not screenshots. Systems with constraints, trade-offs, and consequences.
Case studies from a multi-tenant mobility platform — covering money, access, observability, fraud controls, and dispatch under time pressure.
- 01
Multi-Tenant Wallet & Payments Infrastructure
From debugging silent payment failures to architecting a reconciliation-first wallet system across five payment providers.
Payments / Ledger · 2023 — 2025→ - 02
Driver Promotions with Fraud Detection
An incentive system designed on the assumption that users will try to game it — with geofence integrity enforced in SQL.
Fraud / Spatial SQL · 2024→ - 03
Role & Permission Architecture
One admin panel, many teams, none of whom should see the same things — with permissions as configuration rather than code.
RBAC / Multi-tenant · 2025→ - 04
Ride Event Logs
Every support ticket was an archaeology problem. A domain event stream that answers who did what, from where, and when — for rides nobody can reproduce.
Observability · 2026→ - 05
Driver Dispatch Under Timeouts
Finding a driver is a search problem with a clock on it — expanding rings, batched offers, and a retry loop for when the answer is 'not yet' rather than 'no'.
Dispatch / Queues · 2025-2026→
Portfolio Principle
Every case study answers the same four questions.
01
Problem
What failed or needed to scale?
02
Architecture
Which design protected the invariant?
03
Trade-offs
What did the choice cost?
04
Lessons
What would I do differently?