Guest: Yu Kuai, Mercor's first engineer born in China, previously an engineer at Google, Two Sigma, and Citadel; roles at the time
Host: Qu Kai
Originally published: September 6, 2025 | Duration: 50 minutes 13 seconds
Edited: October 18, 2026 | Official episode
Mercor was initially described as AI recruiting, then as data labeling. Yu's explanation is more specific: its longer ambition concerns labor matching, while AI model companies currently have particularly urgent, well funded demand for expert feedback. The objective need not have changed, even though the entry point narrowed.
The useful question is how demand, professional supply, evaluation, and fulfillment connect. The official description mentions reaching $100 million in annual revenue; the conversation more precisely describes moving from a $1 million to a $100 million annualized revenue run rate in eleven months. Annualizing the current pace does not mean collecting $100 million over those eleven months. These contemporary figures were not audited.
1. Experts help define good work, as well as perform it
Listen: 01:57–06:39 and 18:48–19:43. Yu lists doctors, lawyers, engineers specializing in particular languages, and people combining unusual disciplines or languages. A model company may know something is wrong without knowing how to evaluate medical or legal answers systematically. It needs judgment as well as labor.
Qu initially imagines experts setting standards for less specialized labelers. Yu explains that the same experts may do both: when models can answer ordinary questions, evaluators need stronger capabilities too. The work shifts from mechanical labeling toward explaining which answers are inadequate and what a model should learn to do.
Yu compares evaluation with a model's product requirements document: researchers need a target for further improvement. The analogy explains value without making expert opinions automatically correct. Task definitions, disputed cases, and subsequent performance still need checks.
Retaining evaluation assets also differs from reusing them across customers. Yu says some projects and experts must remain separated. Standards remaining with a platform do not grant unrestricted permission to resell private data or entire question sets.
2. Matching is an entry point; customers also buy lower coordination costs
Listen: 06:44–08:47 and 15:10–15:28. At recording, the business primarily served enterprises rather than offering universal self service. Customers paid Mercor, which paid experts. Beyond recruitment, it handled hours, quality, international payments, and disputes.
With a hundred engineers on a project, customers need to know who completed the work, whose quality is inadequate, and whom to renew. Experts in different countries may encounter payment or record problems. This coordination helps explain why customers might continue using the platform after meeting candidates: they are buying an ongoing service.
Repeat business is not simply a speed contest. Previous successful placements create confidence in the next engagement. Speed and trustworthy quality together form the product, rather than faster delivery of résumés. The episode does not provide complete contracts or margins, so the structure alone cannot establish high profits.
Editorial inference: A marketplace funnel should extend through task acceptance, completion, disputes, and payment. Rapid registration with unreliable fulfillment can merely enlarge the coordination burden.
3. AI interviews need job criteria; identity and quality need further checks
Listen: 09:01–15:28. Questions reflect résumés and role requirements, with people able to add questions and scoring criteria. A roughly twenty to thirty minute video produces a navigable transcript. Recruiters can jump to a statement and observe communication details that text does not fully preserve. The system evaluates and ranks candidates against defined requirements.
A video does not prove every professional capability. Whether scores predict delivery needs subsequent task feedback; speaking style cannot simply stand in for ability. Yu also describes ordinary automation checking identification and public records. An applicant borrowing a real mathematics competition winner's name illustrates why a plausible résumé is insufficient.
Comparing multiple answers can help detect anomalies. However, different answers are not automatically wrong, especially where professionals reasonably disagree. Treating consensus as truth risks rejecting unusual correct solutions.
Supply acquisition is not entirely automatic either. Referrals account for an important portion of registrations, while scarce specialists may require professional forums and events. The cited surgeon rate of $400 per hour and $5,000 referral reward were examples for particular roles then, not current job offers. Historical search difficulty, urgency, and negotiation also influence prices. High prices alone do not establish quality.
4. Fast decisions require noticing and correcting mistakes a week later
Listen: 24:26–35:13. Yu discusses founders' communication skills, early hires from established firms, and growth attracting talent. Growth and better execution may reinforce one another. This does not establish that youth or leaving college caused success, or that one company's account proves a general rule.
He says not every small decision receives a rigorous experiment, but expectations are explicit: what should happen during the next week, and what if it does not? Founders examine what works and what does not. “Being right does not matter” comes with conditions: avoid major mistakes, recognize errors, and adjust. It cannot justify irreversible decisions with large consequences.
Execution has a clearer definition: commitments made for the week are largely delivered by Friday. Other groups provide similar confidence, enabling customer promises. The conversation mentions long hours, but the transferable mechanism concerns predictable commitments, coordinated dependencies, and feedback. Growth does not validate a working regime, and leaving after midnight is not a success formula.
Editorial inference: Translate speed into a cycle of decision, commitment, delivery, observation, and adjustment. Without the final two steps, speed can simply accumulate unknown problems faster.
5. Engineers choosing more problems need support for collaboration across roles
Listen: 35:28–49:59. Yu assesses agency through how much explanation a person needs, how long they can advance independently, and when they seek help. He does not exclude people who prefer execution: teams need combinations rather than a fixed hierarchy based on one word.
A parking problem tests movement from simulating cases to identifying failure conditions. A multiplication problem reveals another behavior: forgetting the rule is acceptable, but spending half an hour pretending to progress instead of asking is costly. The useful observation concerns abstraction and communication, not a claim that one IQ question evaluates all talent. His preference about installed development tools is also personal rather than a universal hiring rule.
He learns concepts through comparisons with familiar ones. Comparing MCP with APIs may provide an entry point, but analogies do not replace formal definitions and practical testing. Building an initial framework quickly and understanding implementation accurately remain separate tasks.
The closing discussion concerns coding agents. AI can draft a beginning that may be wrong, while engineers spend more time choosing problems, speaking to customers, and checking direction. Yu recalls an early Google project: senior colleagues did not necessarily know the answer either. His job was to investigate, solve it, then teach others. If customer contact remains another role's exclusive territory, initiative can become a territorial dispute. Management needs incentives and clear responsibility that recognize actual contributions.
Exercise: complete six stages of an expert service
Map a real order, recording how qualifications are checked, jobs matched, quality accepted, hours recorded, money delivered, and disputes resolved. Add a failure case for each rather than writing “the platform handles it.”
Choose a reversible small change and record the expected result a week later, minimum quality, and stopping condition. Distinguish shipping, customer adoption, and acceptable delivery in the review. Referral rewards should consider effective supply and later performance rather than registrations alone.
Finally, examine one cross-team promise. Whose guarantee allows you to promise a completion date to a customer? This reveals whether execution rests on dependable coordination or recurring rescue by a few people.
Source boundary
This reading uses the official introduction and complete transcript. Revenue run rate, growth, market size, prices, and organizational conditions are accounts from the 2025 conversation. Competitor assessments and transaction motives are not independent findings. “First Chinese employee” is limited to birth in China because Yu explicitly mentions other colleagues of Chinese ancestry. Interview scores, analogies, and puzzles are not validated measures of fairness or ability. Editorial inferences and the exercise are identified separately.
Listening navigation
- 01:57–06:39: Expert demand as an entry point.
- 06:44–08:47: Fulfillment after matching.
- 09:01–15:28: Interviews, authenticity, acquisition, and prices.
- 18:48–24:20: Evaluation goals, private boundaries, and the longer vision.
- 30:54–35:13: Decisions and delivery across teams.
- 35:28–49:59: Agency, learning, and engineering roles.
Related themes: expert evaluation, marketplaces, organizational execution. Further listening: Zhou Jian on enterprise AI delivery and Wang Hua on capability and opportunity stages.