ML Debugging: Parse Conversation Data, Then Fix an LLM Project

Also reported as Debug LLM Project: Find 3 Bugs · ML Code Debugging

MLE / ResearchScale AILast reported March 2026Low Frequency
Reported
3× across candidate reports
First seen
July 2025
Last reported
March 2026
Reported outcome
mixed

Problem Overview

A 60-minute ML round in two parts, done in one session. First you write a simple parser for conversation data; then you are handed a complete LLM project, run it, and find and fix its bugs. This stand-in plants three. Part 1 — Parse the conversation data. Write parse_conversations(raw), which…

  • The rest of the problem statement — full requirements, constraints, and edge cases
  • Approach and trade-offs — what passing candidates did, and the mistakes that sink people
Unlock the full Scale AI catalog
Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Scale AI question.
Unlock with Pro
Already a member? Sign in
Verified Source
Every question is reconstructed from multiple independent candidate reports. Verbatim follow-ups, not invented ones.
Codex Fact-Checked
Technical claims, formulas, and scale numbers are reviewed against primary sources.
Interviewer Follow-ups
The exact follow-ups reported by candidates, with the trigger that prompts each one — plus the mistakes that sink people.
Is this helpful?