Work
Anonymized until we have permission to name names. Each story is a problem, what we built, and what changed.
01 — Cloud migration
Moved a company’s operation of the entire product platform off a manually managed VPS onto automated Kubernetes on AWS EKS. Zero-downtime deploys, autoscaling, scale-to-zero for cost, Kubernetes events, and event sourcing as the backbone. They went to the cloud. The name stays off the page.
Outcome: production kept running through the cutover; capacity and cost now follow traffic.
02 — Same-day delivery platform
Built the courier-network integration for a platform that orchestrates same-day prescription delivery. Companies without their own drivers could pick external couriers at order time, with live rates from multiple courier APIs. AWS serverless, event-oriented, talking to several external systems. Client unnamed.
Outcome: same-day delivery as a product, without standing up a private fleet.
03 — 1,000 years of Metropolitan Archives
For the Metropolitan Archives, digitized holdings spanning a thousand years were made searchable: metadata, extracted content, indexed and filterable, so a query comes back in sub-second time and anyone who needs the record can have it immediately.
Outcome: the respective Metropolitan Archives can serve the archive instantaneously instead of as a slow lookup.
04 — Multi-tenant SaaS core
Designed a hybrid schema-isolation engine with explicit tenant context, safe background work, and operational tooling for a growing SaaS platform.
Outcome: stronger isolation and a predictable path for onboarding and scaling tenants.
05 — Monolith decoupling
Separated a high-traffic workflow behind stable contracts, shadow traffic, and observable migration checkpoints while the existing product stayed live.
Outcome: independent deployment without a risky big-bang rewrite.
Operational constraint
Practical intervention
Measured change