The ML research scientist is the person pushing the boundary of what AI systems can do — designing new model architectures, training methods, optimisation algorithms, and theoretical frameworks that expand the field's capabilities. The primary pull is Discovery: the work exists because nobody yet knows the best way to build systems that learn, reason, and generalise, and the researcher's job is to find out. The satisfaction lives in the moment when an experiment reveals something genuinely new — a training technique that produces unexpected capabilities, a mathematical insight that explains why a particular architecture works, a result that changes how the community thinks about a problem.
The daily texture is a cycle of reading, thinking, coding, and experimenting. A research scientist might spend a morning reading recent papers to understand the state of a problem, an afternoon designing and coding an experiment, and an evening analysing results and iterating. The work requires comfort with failure — most experiments do not produce the hoped-for result, most papers take multiple rounds of revision, and the path from an initial idea to a published contribution is rarely linear. The people who thrive are those who find the process of inquiry intrinsically rewarding, independent of whether any particular experiment succeeds.
The field is moving extraordinarily fast. A result that is state-of-the-art in January may be surpassed by March. The competitive pressure — multiple labs working on similar problems, racing to publish first — is real and shapes the culture. The best research environments manage this pressure without letting it corrupt the science; others do not.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
The gap between the public image of AI research — building superintelligent systems, solving grand challenges — and the daily reality is significant. Most research work is incremental. A typical contribution is a modest improvement on a benchmark, a new way to reduce training compute by fifteen percent, or a theoretical result that clarifies a narrow aspect of how neural networks learn. The breakthroughs that reshape the field are rare, and the researchers who produce them have usually spent years on the incremental work that made the breakthrough possible.
The publication system dominates the incentive structure in ways that are not always healthy. Researchers are evaluated primarily by their publication record, which creates pressure to optimise for publishable results rather than for the most important questions. The "publish or perish" dynamic from academia carries directly into industry research labs, where headcount and project funding depend on demonstrated output.
The compute inequality is stark. Frontier research increasingly requires access to enormous computational resources — thousands of GPUs for weeks or months — that only the largest organisations can afford. A researcher at DeepMind or OpenAI has access to compute that a university researcher cannot match, and this shapes what questions each can realistically pursue.
A PhD in computer science, machine learning, mathematics, statistics, or a related quantitative field is effectively required for research scientist positions at top labs. The PhD provides both the technical depth and the publication track record that hiring committees evaluate. Strong undergraduate programmes in mathematics, computer science, or physics provide the foundation, and research experience during undergraduate study (summer internships at research labs, undergraduate theses) is increasingly important for competitive PhD admissions. Post-doctoral positions are common stepping stones. Industry research labs (Google DeepMind, Meta FAIR, Microsoft Research, Amazon Science) and university departments are the primary employers. Some entrants arrive through exceptional demonstrated ability without a PhD, but this path is rare and requires an extraordinary portfolio of published work or open-source contributions.
Directs the tools automating research itself, and is best-placed to judge whether autonomous findings are real. Experiment-execution layer increasingly agent-assisted; research direction and interpretation protected. Compute inequality binds what can be pursued.
Gaining value in research-direction and interpretation; 'agent-directing scientist' configuration emerging at well-resourced labs.
People drawn to ML Research Scientistare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.