Backend Engineer — Node.js · TypeScript · Redis
I build backend systems that stay correct under load —
networked services, distributed state, and infrastructure other engineers build on.
- Backend services designed for concurrency correctness — shared state that holds under simultaneous load
- Distributed systems patterns: rate limiting, caching strategies, API contracts, event-driven queues
- Infrastructure that runs independently and lets other services call into it — not an importable library
- AI-native development workflow with GitHub Copilot and Claude for architecture decisions and faster delivery
TypeScript Node.js Express Redis Lua k6
A standalone rate limiter other services call into over the network — not a library. Built for shared state, atomic correctness, and zero-restart config changes.
| Throughput | 500+ req/s sustained under k6 load — correctness gate exits non-zero if allow-count exceeds configured limit |
| Concurrency | Atomic Lua/EVALSHA scripts inside Redis — eliminates race conditions that application-level locking cannot prevent |
| Architecture | Dual-plane design: data plane (/check) and control plane (/admin) communicate only through Redis — zero router coupling |
| Config | Per-client algorithm (token bucket / sliding window), burst size, and window size hot-swappable at runtime via PUT /admin/clients/:clientId |
Languages & Runtime
Backend & Infrastructure
Expanding
Currently: Tollgate Phase 4 — distributed mode across multiple Redis nodes
