// Software Engineer · Distributed Systems
Building distributed systems and large-scale infrastructure that hold under load, at scale, in production.
About
Most backend systems are built to pass code review — not to survive production.
Latency creeps. DB connections exhaust. A webhook fires twice and an order duplicates. The tracking system that handled 5 carriers quietly breaks at 32. Engineers patch symptoms. Few design for root causes.
That gap is where I work. As Founding SWE at Openleaf, I design and ship fault-tolerant distributed systems: high-concurrency tracking engines, event-driven microservices with exactly-once delivery, large-scale PostgreSQL schemas built for multi-tenant load.
I'm also a competitive programmer — ICPC Asia-Taiwan, India Rank 3 — which means data structures and algorithms aren't theory. They show up in every system I design: O(n²)→O(n+m) tag-matching, two-tier cache TTL selection, connection pool sizing under concurrent load.
Open to SWE3 opportunities at companies that care about correctness, scale, and engineering craft.
Experience
Skills
Engineering Highlights
Production-grade pricing system with hierarchical geographic lookup across 6 tiers, 40+ charge types, and bidirectional route matching. Zero pricing errors serving 13+ logistics carriers.
High-concurrency shipment tracking at concurrency=128. Two-tier Redis caching eliminates serial DB round-trips. Parallelised terminal-state writes minimise per-job latency.
Event-driven order pipeline with exactly-once delivery semantics via SQS FIFO. Optimised from O(n²) to O(n+m) tag-matching, tuned connection pooling, eliminated all N+1 lookups.
Contact
Open to SWE3 opportunities at top-tier tech companies. If you're a Google recruiter or building distributed systems at scale — I'd love to connect.