kula

AI Systems Engineer — Agent Platforms · LLM Infrastructure · Audio/Video ML

📍 Seoul, South Korea (UTC+9) ✉️ kula9055@gmail.com

60s → 263msagent hot path, ~150× faster, A/B-verified
2nd placenational copyright org's AI-music-detection procurement
3 days → 5 minAI video production pipeline, sole engineer
5M+ recordskeyword search migrated to pgvector semantic search
P1 criticalBinance bug bounty — accepted report (Bugcrowd)

I build AI systems that survive contact with production. Twenty years shipping software; the last three spent entirely on the part most engineers skip — latency budgets, provider failover, evaluation harnesses, and the infrastructure that keeps an agent answering in under 10 seconds instead of 39. I read the codebase before I propose the plan: my last provider migration shipped as two environment variables per service instead of a multi-repo rewrite, because an audit showed all three AI surfaces already shared one hook pattern.

Selected Work

AI Agent Platform — venture-backed marketing SaaS (contract, ongoing)

Next.js · DeepSeek/Gemini · pgvector · PostgreSQL · LiteLLM · Docker

AI-Generated-Music Detection — national copyright organization bid (2nd place, procurement evaluation)

Python · PyTorch · ONNX · FastAPI · Demucs · Docker

Cenema — AI video automation platform (CTO / sole engineer)

TypeScript · Cloudflare Workers · Inngest · Gemini · Kling

AI travel planning platform (contract + equity, ongoing)

Earlier (2004–2024)

How I Work

Spec-first: every change starts as a written proposal with the problem, the measured baseline, and what I'm explicitly not touching. Never claim an optimization without an eval behind it.