Mercor Sr. Machine Learning Engineer at Mercor building ML systems for scoring, validating, and improving complex work products with ambiguous correctness. Focus on applied ML product engineering under real production constraints.
Responsibilities
Frontier AI companies are increasingly bottlenecked on expert judgment — capturing it reliably, validating it at scale, and turning it into durable model behavior. This role sits at the center of that problem.
You'll build the ML systems that power Mercor's Frontier Data Products: the infrastructure that scores, validates, and improves complex work products where correctness is rarely binary and labels are often noisy, delayed, or disputed. A single job can stay live for days, interleaving model inference, automated checks, expert review, disagreement resolution, and feedback loops. Your work determines how models reason over ambiguous inputs, when they should defer to humans, how quality is measured, and how feedback compounds into better systems over time.
This is applied ML product engineering under real production constraints — incomplete ground truth, shifting requirements, latency and cost tradeoffs, and workflows where a silent model failure corrupts the final output. It is not an offline benchmarks role.
Build ML systems that score, validate, and improve complex work products where correctness is nuanced and labels are imperfect.
Design evaluation frameworks for ambiguous tasks where ground truth is partial, delayed, or disputed.
Build feedback loops that turn review, disagreement, correction, and adjudication into measurable model and system improvements.
Own production ML behavior end-to-end: precision/recall tradeoffs, regression detection, drift, latency, cost, and explainability.
Improve model quality using the right tool for the job — prompting, fine-tuning, retrieval, active learning, heuristics, and error analysis.
Partner with backend engineers to integrate inference into durable, long-running workflows without sacrificing debuggability or human oversight.
What Makes This Role Different
The architecture is not set — early engineers will define how quality is measured, how models and humans interact, where automation is trusted, and how the system compounds over time.
The feedback loop is short: shipping a model behavior change directly and visibly affects what customers receive.
Qualification
Strong instincts for model qualityFamiliarity with LLM applicationsYou're likely someone whoHas 4+ years of experienceDefaults to simple
Required
Track record of shipping ML systems that improved a real product, workflow, or business metric.
Strong instincts for model quality, evaluation design, error analysis, and production failure modes.
Comfort operating in ambiguous problem spaces where labels are imperfect and correctness evolves.
Sound judgment about when to reach for prompting, fine-tuning, heuristics, retrieval, human review, or a simpler product constraint.
Solid engineering fundamentals across the full ML stack — not just modeling.
Familiarity with LLM applications, model-assisted workflows, evaluation frameworks, or human-in-the-loop ML is a strong plus.
You're likely someone who:
Has 4+ years of experience
Defaults to simple, inspectable ML systems that improve quickly and fail in understandable ways — not the most impressive architecture.
Gets uncomfortable when a model ships without a clear evaluation story.
Can hold ambiguity without paralysis and make reasonable bets with incomplete information.
Cares about the real-world output of the system, not just the benchmark.