Gaming · Production · 6 months
ESL — Tournament Automation
When manual data prep ate hours per tournament config.
Problem. New streaming pipelines needed bootstrapping data extracted manually from messy documents. Slow, error-prone, blocking tournament launches.
What I built. A 4-microservice architecture combining LLM-based parsing with graph-solver reasoning. Templates matched, edge cases handled automatically. Solo design and implementation.
Outcome. 2–3 hours per config dropped to 5 minutes. Errors caught pre-production. Launches no longer blocked.
Stack: Python · LLM APIs · graph solver · Scala microservices · AWS
