Overfit a single batch first
Before trusting a training run on the full dataset, check that the model can drive its loss to near zero on a tiny handful of examples. If it cannot even memorize ten examples, the bug is in the code, not the data.
AI Researcher · Designs and tests the algorithms behind machine intelligence, in a field now racing to automate a growing share of its own research process.
Darker cells mean a higher score for this topic on that metric.
LessMore
Last reviewed Sources & creditsMedia creditsMethodology
Most days split between reading recent papers, writing and debugging training code, waiting on and analyzing results from long-running experiments, and discussing findings with collaborators. Contrary to the popular image, a large share of the job is diagnosing why a model is underperforming or a result won't replicate, not brainstorming new architectures from scratch.
For an independent research role at a university or a top industry lab, effectively yes — a PhD remains the field's real credential, since there is no licensing exam. Strong engineers without one increasingly enter through industry residency programs or a public record of open-source work and cited preprints, but titles like 'research scientist' still skew heavily toward doctorate holders.
Parts of it clearly are: literature summarizing, boilerplate experiment code and first-draft related-work sections are already routinely AI-assisted, and labs are openly experimenting with systems that propose and run their own experiments. Framing what a result actually means, and taking responsibility for a published claim, have proven much harder to hand over.
It varies enormously by employer and seniority. The US median for the broader 'computer and information research scientist' category was $140,910 in 2024, but new PhDs joining a large technology company's research lab often start well above that, and a small number of senior researchers at frontier AI labs have reportedly been offered total packages worth seven or eight figures during the 2024–2025 hiring competition.
The lines blur constantly, but a rough distinction holds: a researcher's output is usually a paper, a new method or an insight about why something works, judged by peer review; an engineer's output is usually a working system in production, judged by whether it ships and holds up under real use. Many people do both across a career.
Python dominates, paired with a deep-learning framework — PyTorch is now the most common in research, with JAX popular for large-scale and Google-affiliated work. Beyond code, researchers depend on shared GPU or TPU compute clusters, experiment-tracking tools like Weights & Biases, and arXiv, where most new results circulate as preprints months before formal peer review.
The image of a researcher inventing a clever new algorithm in a flash of insight is mostly wrong. Most days are spent running experiments that fail in uninformative ways, reading what a hundred other labs published this month, and trying to tell whether a promising result is real or an artifact of a lucky random seed.
The craft passed down inside the field is less about which architecture to memorize and more about experimental discipline: how to isolate what actually caused an improvement, when to trust a benchmark and when not to, and how to keep a negative result from being quietly thrown away.
Linear algebra, probability, calculus and optimization are the language nearly every model and paper is written in; without them, new methods are unreadable rather than just unfamiliar.
Writing efficient code in Python and a deep-learning framework, and understanding enough distributed-systems engineering to run training jobs across dozens or thousands of processors.
Designing controlled comparisons, running enough random seeds to trust a result, and isolating which specific change actually caused an improvement rather than assuming the obvious explanation.
Keeping up with a field publishing tens of thousands of new preprints a year, and telling which handful actually matter, is now a skill in its own right.
Choosing which of many plausible directions is worth months of compute and attention — the hardest skill to teach directly, usually absorbed by working alongside an experienced advisor.
A result that cannot be written up clearly enough to survive peer review, or explained to a non-specialist funder, struggles to have any impact regardless of how real it is.
Reviewing overnight experiment results and skimming new arXiv preprints and lab chat discussion before the day's focused work begins.
The best-protected block of the day, spent writing training code, debugging a model, or designing the next experiment in a series.
Often eaten with labmates, and frequently the setting for the kind of informal idea-swapping that a scheduled meeting rarely produces.
Lab meetings, one-on-ones with an advisor or manager, and a rotating reading group where someone presents a paper the group needs to understand.
Digging into why an experiment did or did not work, updating a shared results document, and drafting sections of a paper ahead of a deadline.
Personal time — except in the weeks before a major conference deadline, when evenings and weekends routinely disappear into finishing experiments.
Craft knowledge practitioners actually pass on — not motivation.
Before trusting a training run on the full dataset, check that the model can drive its loss to near zero on a tiny handful of examples. If it cannot even memorize ten examples, the bug is in the code, not the data.
A surprising share of published 'improvements' shrink or disappear once the comparison baseline gets the same hyperparameter search budget as the new method — a pattern documented across GANs and language models alike.
When a new method with five changes bundled together beats an old one, remove each change independently and re-test before crediting any single idea — otherwise the paper's story and the actual cause of the gain can quietly diverge.
A leaderboard number stops measuring general ability once researchers repeatedly tune directly against it — a dynamic long known as Goodhart's law, and cited directly in critiques of benchmark saturation across NLP and vision.
Drafting a paper's core claims early forces a concrete, falsifiable target for the remaining experiments, instead of running experiments first and assembling a narrative around whatever happened to work.
Failed configurations, seeds and hyperparameters are usually thrown away once a run fails, but recording them prevents a lab from quietly re-running the same dead end six months later under a different name.
The two dominant deep-learning frameworks; PyTorch leads in most academic and industry research, while JAX is popular for large-scale and Google-affiliated work.
Shared clusters, scheduled with tools like Slurm, that turn a model design into an actual trained network — often the single biggest constraint on what experiments are possible.
The field's de facto publication venue in practice: new results circulate here as preprints, often months before or entirely without formal peer review.
Experiment-tracking dashboards that log loss curves, hyperparameters and outputs across hundreds of runs, without which comparing experiments would be unmanageable.
Interactive environments for quick data exploration, debugging a model's behavior on specific examples, and prototyping before code moves into a full training pipeline.
Squeezing out a fractional accuracy improvement through extra hyperparameter search or scale, without a hypothesis for why it works, produces results that are hard for anyone else to build on even when the number itself is real.
Running many seeds and publishing only the best one, instead of a mean and a spread, makes ordinary noise look like a genuine effect — a problem flagged repeatedly in reinforcement-learning and NLP reproducibility studies.
Test data that leaked into a pretraining corpus, or a compute budget quietly larger than a paper reports, can make a result impossible to reproduce — and once discovered, damages a researcher's credibility more than a modest, honest result would have.
Closest neighbours on the six-score profile — not the same field only.
Designs and fabricates the transistors inside every computer, phone and weapon, using machines precise enough that only a few factories on Earth can run them.
AI-resistant 60 📦Builds the systems that train, deploy, monitor and govern machine-learning models in production.
AI-resistant 54 🩺Diagnoses illness and manages health for years afterward through examination and evidence, not a single operation — medicine's generalist and long-term guide.
AI-resistant 67 🧠Diagnoses and treats mental illness through medication and therapy, one of medicine's only specialties with legal authority to detain a patient in crisis.
AI-resistant 73 👔Advises clients, drafts the documents that bind them, and argues their case when it reaches court — carrying personal legal liability if the advice is wrong.
AI-resistant 58 🔐Protects systems, data and people by finding, preventing and responding to digital attacks.
AI-resistant 63Writes, tests and maintains the code that runs modern life — and is one of the first professions watching AI automate its own daily work.
AI-resistant 35 🛰️Designs, analyzes and certifies the aircraft, rockets and spacecraft that leave the ground, working to safety margins that leave no room for guessing.
AI-resistant 74 🌉The profession that turns rivers, rock and gravity into bridges, roads and clean water — civilization's quiet load-bearing trade since Imhotep.
AI-resistant 72 🔌Designs and fabricates the transistors inside every computer, phone and weapon, using machines precise enough that only a few factories on Earth can run them.
AI-resistant 60 🦾Designs the machines that sense, decide and act in the physical world, where the hard problem was never intelligence but the world itself.
AI-resistant 65 🔐Protects systems, data and people by finding, preventing and responding to digital attacks.
AI-resistant 63 📦Builds the systems that train, deploy, monitor and govern machine-learning models in production.
AI-resistant 54 🌬️Designs, builds and improves wind, solar, storage and grid systems that turn renewable resources into dependable electricity.
AI-resistant 72