Invest1 publisher2 min readPublished
Meta's AI chief credits evaluation systems, not raw intelligence, for agents beating 100 engineers
Alexandr Wang told a Y Combinator audience that a swarm of Meta agents scheduled by cron beat 100 engineers on specific tasks, and he credited the evaluation system for the result. Meta paid $14.3 billion for Scale AI.
The Investor · Invest desk

What happened
- Meta Chief AI Officer Alexandr Wang said a swarm of the company's AI agents outperformed a team of 100 human engineers on specific tasks.
- The agents keep persistent memory in markdown files and are scheduled through cron jobs, the Unix task scheduler in use since the 1970s.
- Meta acquired Scale AI, which Wang founded, for $14.3 billion, and he became Chief AI Officer in June 2025.
- Meta's Muse, known internally as Hatch, is a single agent for email, scheduling and payments across applications, set for public release in September 2026.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- exposure The argument that evaluation decides the outcome values the kind of asset Meta bought, and the man making it founded the data labeling and AI infrastructure company at the centre of the deal.
- constraint Copying the setup requires work that can be cut into loops with output an agent can grade, so teams whose success criteria are not written down have nothing to hand the loop.
- precedent With Y Combinator running its own QM multi-agent harness in-house, a founder pitching an agent product should now expect to be asked for the grader.
The $14.3 billion Meta paid for Scale AI, set against the 100 engineers in the only comparison Wang has offered, works out at $143 million per engineer beaten [14]. The deal bought data operations and a research bench as well, so the division is unfair to it.
Saying that evaluation decides the outcome is saying where the money should go, and it comes from a founder whose previous company's business model revolved around making AI systems measurable and accountable [11]. Wang kept the boundary tight. According to CryptoBriefing's account of the conversation, he said the agents outperformed engineers "on specific tasks" with "the right evaluation system" [8].
Which model the loops call, how long they ran, and what the compute cost do not appear in that account [15]. Two readings fit the gap equally well. Either the scheduling and the grading are the difficult part, or a frontier model absorbs the difficulty and the loop keeps it aimed at something checkable.
The account credits the result to robust evaluation methods, the ability to run continuously, and a feedback architecture that lets the agents improve without human intervention [6]. Taken at face value, that sends the next increment of engineering attention to graders, logs and schedulers instead of another point of model capability. The plumbing is free, so the budget question is about everything upstream of it.
The narrow version of the claim is the one I would back: where a task has a written success criterion, a loop that runs all night and checks its own output will outproduce a queue of people who each need a ticket and a review. The wide version, that swarms beat teams, rests on one report of what was said on a stage [2]. Two results would tell against the narrow version too: a task list whose items turn out to be trivially checkable, and loops that stop working when the model underneath them is swapped.
What to watch
- Whether Muse ships publicly in September 2026 with payments enabled, or slips.
- Whether Meta publishes the task set and success criteria behind the 100-engineer comparison.
- Whether any second account of the Startup School conversation corroborates the figure.