easyOpenAIAnthropicGlean

Parse a JSON-lines file of LLM logs and aggregate tokens generated per request.

Real LLM logs are JSONL, not JSON, and real log files have a malformed line halfway through. The warm-up that screens whether you can stream a file and aggregate without one bad record nuking the whole run.

Updated Aug 2026 · Grounded in real Forward Deployed Engineer interview loops and written to a senior-engineer editorial bar.

20 answers per topic instead of 10, plus saved progress and bookmarks · no cardor unlock all 548 remaining answers · ₹2,000 / $25

Every answer, concept and course, every paper breakdown, all published video lessons, hands-on FDE Lab missions, Premium PDF guides and companion files, the full practice-test bank and work-sample downloads. Referral Premium excludes guide PDFs and their companion files.

6 months · One payment · No auto-renewal

Study alongside free video lessons.

Keep practising

Next in this trackWrite a generator that yields fixed-size batches from a large iterator for streaming inference.Premium Next in this trackMaintain a sliding-window average over a stream of metrics, like tokens/sec.Premium Next in this trackGiven ground-truth and predicted labels, compute precision, recall, and F1 from scratch.Premium

FEDITOR'S NOTE

The discriminator is the malformed line. Candidates who call json.loads on the entire file fail immediately because JSONL is one object per line, not an array. The ones who then forget to wrap per-line parsing in a try/except crash on the first truncated write, which in production is the line your batch job died on. A senior answer counts skipped lines and keeps going.

DISCUSSION · 0

No comments yet — be the first to share your approach.