backend brain. full stack hands.
i build systems that stay correct when everything tries to break them.
full stack engineer obsessed with the stuff under the hood: concurrency, idempotency, rate limiting, and failure-safe API design. i like building things that don't fall over at 200 simultaneous requests, and shipping them from spec to production without the drama.
200+ concurrent bids handled, exactly one valid winner per date
500+ documents processed through an OCR + extraction pipeline
90%+ field extraction accuracy
~40% fewer wrong LLM answers after adding RAG
languages
backend
frontend
data
cloud & devops
ai & ml
| zone | the full list |
|---|---|
| backend & distributed | Fastify · REST design · system design · distributed systems · concurrency control · rate limiting · idempotency · multitenancy · BullMQ |
| data | PostgreSQL · MongoDB · Redis · Neon · Supabase · pgvector · Row Level Security |
| security & auth | JWT · RBAC · OAuth · webhooks · payment gateways · SSRF-safe request validation |
| ai & agents | RAG · LLMs · multiagent systems · embeddings · semantic + vector search · OCR · Claude Code · MCP |
giving back, one PR at a time.
| project | what i shipped |
|---|---|
| Apache Magpie | trimmed skill context by 24% (7/7 evals) and cut routing metadata by 38% without losing safeguards |
| Kestra | replaced 55 any usages across 10 TypeScript/Vue files with proper types, all checks + 109 unit tests green |
| OWASP cve-lite-cli | fixed semver diagnostics for below-range, above-range and union-gap mismatches, with regression tests |
01 correctness first. speed second. flexing third.
02 if it can fail, design for the failure.
03 retries should be safe. always.
04 simple beats clever.
05 ship it, then make it better.
just clean commits.