Role hub · live · updated 20 Nov 2026

Research engineer: the role, pay and who is hiring

A research engineer builds the code, infrastructure and experiments behind AI research: training runs, evaluation pipelines, data systems and the tools researchers use, often running experiments themselves. It is among the best-paid engineering titles at AI labs, where Anthropic, OpenAI and Google DeepMind hire research engineers by the team.

Open roles
716
Companies hiring
320
Median posted pay
$190k to $300k
Remote
16%
Demand
up 1.5x in a year

This week · 20 Nov 202625 new Research engineer roles, most from Clera, Dragos and Maven Robotics.

01 · The role

What does a research engineer do

The engineering half of a research team. Read across lab postings, the work covers:

  1. INFRA

    Make training work at scale

    Distributed training, GPU efficiency, data loaders, checkpoints and the code that keeps big runs alive.

  2. EXPERIMENTS

    Run the experiments

    Implement ideas from papers or the team, run ablations, and turn noisy results into a clear answer.

  3. EVALS

    Measure the models

    Benchmarks, safety and capability evals, and the pipelines that run them on every checkpoint.

  4. TOOLS

    Speed up research

    Internal tools, data systems and environments that let researchers try more ideas per week.

02 · Pay

Research engineer salary

Median posted pay on landed, next to the bands the biggest employers publish.

Median posted range, USD base

$190k to $300k

From 330 live postings that publish a range, before equity and bonus.

Research engineer salary by city and company →

03 · The way in

How to become a research engineer

A PhD helps but is not required. Proof of engineering at research scale matters more.

  1. [x]
    Get very strong at Python and PyTorchWrite training loops yourself, not only with high-level libraries.
  2. [x]
    Reproduce a paperPick a recent paper, reproduce its main result and publish the code and what differed.
  3. [ ]
    Work at scaleMulti-GPU training, profiling and speedups. Open-source contributions to training libraries count.
  4. [ ]
    Show your judgementWrite up experiments clearly. Labs hire people whose results they can trust.
  5. [ ]
    Apply the day roles openEarly applicants get read first. Full Research engineer roadmap →

04 · The roadmap

How to become a Research Engineer: the roadmap

About 9–18 months, 7 stages, 9 core skills, aiming at $245k. The AI Research Engineer is described by Jobs By Culture as "the highest-leverage technical role at frontier labs in 2026." Google DeepMind frames the RE as "software engineers with a deep understanding of machine learning and deep learning." A PhD is not required; what is required is research taste plus engineering judgment. Acceptance rates sit below 1%, but total comp runs from $350K for new grads to $500K-$900K for seniors and $1M+ at Staff/Principal. The focused prep window is 6-10 weeks on top of a 12-24 month transition from senior software engineering.

  1. Stage 0 · 8-12 weeks

    Strong Python + numerical + GPU literacy

    CUDA basics, Triton kernels, PyTorch internals (dispatcher, autograd, inductor), and profilers (torch.profiler, nvprof, nsys). Completion signal: write a working Triton kernel for softmax.

  2. Stage 1 · 4-8 weeks

    Distributed training literacy

    FSDP/FSDP2, DeepSpeed ZeRO-3, Megatron-Core, Megatron-FSDP, and tensor/pipeline/context parallelism. Completion signal: reproduce a small multi-node training script with an explicit parallelism choice.

  3. Stage 2 · 2-5 days per paper

    Reproduce-paper muscle

    FlashAttention v3, RMSNorm, the Llama-family architecture, and nanoGPT. Completion signal: an open-source repo with a clean reimplementation. The benchmark is 2-5 days per paper.

  4. Stage 3 · 4-8 weeks

    Frontier model internals

    Attention variants, mixture-of-experts, RLHF/DPO/GRPO, and eval suites (lm-eval-harness, HELM, FrontierEval). Completion signal: submit a public eval result on a frontier open model.

  5. Stage 4 · 6 weeks

    Research discussion literacy

    Read 5+ papers per week and practice the "present the contribution, methodology, strengths/weaknesses, and extensions" framing. Completion signal: run mock paper-discussion rounds cold.

  6. Stage 5 · 4-6 weeks

    Lab specialization

    Pick OpenAI (reasoning, post-training), Anthropic (interpretability, safety), or DeepMind (JAX-native, Gemini). Completion signal: a tailored portfolio plus a lab-specific project.

  7. Stage 6 · 4-8 weeks

    Interview loop

    Coding, system design, paper discussion, and lab-flavored behaviorals ("AGI focus", safety convictions, "Googleyness"). Completion signal: pass the final loop.

The full roadmap: projects, skills and what to learn at each stage

The roadmap, stage by stage

There are two parallel entry bars. A Master's plus production ML plus demonstrated systems engineering makes you competitive at OpenAI, Anthropic, DeepMind, Cohere, Mistral, Cursor, Databricks, Scale AI, and Cresta. A PhD (or equivalent research output) is more typical for Research Scientist than Research Engineer, though PhD REs exist. The staged path front-loads systems literacy: Stage 0 pushes you into CUDA basics, PyTorch internals, and a first Triton softmax kernel, because at frontier labs an RE is expected to read and profile kernels, not just call them. Stage 1 builds distributed-training literacy across FSDP2, DeepSpeed ZeRO-3, and Megatron-Core, with the signal being a reproduced multi-node training script that makes an explicit parallelism choice. Stage 2 is the heart of the role: the reproduce-a-paper muscle, benchmarked at 2-5 days per paper, producing clean open-source reimplementations of FlashAttention v3, RMSNorm, or a Llama block. Stage 3 moves into frontier internals and standardized evals; Stage 4 builds research-discussion fluency by reading 5+ papers weekly and rehearsing the contribution/methodology/strengths/extensions frame; Stage 5 tailors everything to a chosen lab; Stage 6 is the loop itself. The honest master checklist, per Jobs By Culture, is "8-12 weeks PyTorch fluency + 2-5 days per paper reproduction + 6-8 weeks interview prep + 1 standout open-source artifact." The full transition from senior SWE runs 12-24 months, or 3-5 years if you must build the math and research taste from zero. See the honest path writeup.

The 2026 stack to learn deeply

The 2026 ranking is explicit: PyTorch > FSDP2/DeepSpeed/Megatron > Triton > CUDA > JAX > FlashAttention/vLLM/HF > eval harnesses > experiment trackers. Tier 1 is the non-negotiable frontier core. PyTorch, deeply: every frontier lab uses it as the primary DL framework, and you should be able to reason about the dispatcher, autograd, inductor, and compile. JAX is rising fast because DeepMind is JAX-native and Anthropic is increasingly JAX-friendly for safety work, so you must be able to write and review a JAX training loop. The distributed-training glue is FSDP/FSDP2 (torch.distributed.fsdp), DeepSpeed ZeRO-3, Megatron-Core, and NVIDIA Megatron-FSDP; the build target is a multi-node script that reproduces a paper with an explicit parallelism choice. Triton, the kernel language, is a "plus" signal at OpenAI and Anthropic: write kernels for fused softmax, FlashAttention, and custom activations. CUDA literacy means enough to read kernels, profile them with nsys and Nsight, and reason about memory bandwidth versus compute. Tier 2 is the auxiliary stack: FlashAttention v3 as the canonical kernel to reproduce, vLLM for inference and eval generation, Hugging Face Transformers/Accelerate/TRL for fine-tuning and reward-model training, lm-eval-harness for standardized evals, and W&B or Neptune for experiment tracking. Tier 3 is specialization: for Anthropic interpretability, TransformerLens and nnsight; for OpenAI post-training, TRL plus GRPO plus custom reward models and high-throughput RL infrastructure; for DeepMind, JAX-native scaling and Gemini-family evals.

Portfolio projects that get you hired

The RE portfolio is judged on reproducibility and low-level depth, not breadth. The recommended ladder runs from foundational to standout:\n\n- nanoGPT-style training of a small custom GPT (PyTorch fluency plus paper-to-code).\n- Re-implement "Attention Is All You Need" in a 2-5 day sprint (reproducibility and Transformer literacy).\n- Implement a Llama-family block with RMSNorm, SwiGLU, and RoPE (modern-architecture literacy).\n- Implement FlashAttention v3 as a Triton kernel: this is the standout signal, and most candidates in any role still lack it.\n- Build an RLHF/DPO pipeline on a 7-13B open model (post-training depth).\n- Submit a public lm-eval-harness result for a frontier open model (standardized eval maturity).\n- Write a paper or blog post on a failure mode of a frontier model such as sycophancy or jailbreak reproducibility (frontier-model critique and "scrappy energy").\n- A mechanistic interpretability study using TransformerLens on an open-weight model (the Anthropic interpretability track signal).\n- An open-source contribution to vLLM, FSDP, or the HF Hub (production-system literacy).\n\nThe full standout portfolio is a small open-weight model trained end-to-end on a custom curated dataset with a public eval. Writing Triton kernels for fused softmax, RMSNorm, or a layer-norm variation beats another LoRA project in the eyes of frontier-lab REs, and a Triton-kernel write-up in blog form is the RE equivalent of an accepted open-source patch.

How the role is evolving

Post-training is the new hotness. OpenAI's Post-Training team is responsible for "training the models to be deployed into ChatGPT, the API, and future products," and reasoning models (the o1/o3/o4 line and GPT-5-pro reasoning variants) have arguably made post-training more important than pre-training in 2026. RLHF is shifting toward DPO, GRPO, and RLAIF: less human labeling, more programmatic and verifier-based reward modeling. Interpretability is rising fast enough that "Research Engineer, Interpretability" is now a discrete listing at Anthropic, and the "Tracing the thoughts of a large language model" paper is standard prep reading. Pre-training data quality is back: frontier labs have increasingly woven human-generated data into pre-training and mid-training stages through 2025-2026. Federated and privacy-preserving training is emerging for healthcare, finance, and government labs. Because the RE title (unlike Research Scientist) does not strictly require a publication record, artifact contributions like Triton kernels and open evals are increasingly the currency. Rising directions: post-training specialization, agentic RL, mechanistic interpretability, and multimodal foundation models. Fading: pure PPO/RLHF research and classical RL without a foundation-model context. Two cultural notes matter. Anthropic reference-checks during the cycle, a unique signature, so treat every collaborator and ex-manager as a future reference. And the "AI Safety Needs Great Engineers" thesis from 2021 still defines who gets hired: "Anthropic is bottlenecked on aligned engineering talent."

How to actually get hired

The 6-10 week prep timeline maps onto three distinct lab processes. OpenAI runs a recruiter screen, a technical phone screen, then a 4-6 hour virtual onsite (coding, system design, ML debugging, research discussion, behavioral), end-to-end roughly 6-8 weeks. Anthropic filters with a 90-minute CodeSignal (a 520+/600 score is the bar) plus reference checks, averaging about 20 days. Google DeepMind opens with a rapid-fire quiz on undergraduate fundamentals, then a hiring committee, and is faster than typical FAANG. The question bank spans math and theory (linear algebra: eigenvalues, SVD, PCA; calculus: gradient derivation, autodiff; probability: MLE, Bayesian; information theory), coding (Multi-Head Attention, Transformer layers, CNN, K-means, AUC, KV caching, quantization, speculative decoding), and system design ("how would you train a 100B+ parameter model" with tensor/pipeline/context parallelism). The paper-discussion round is distinctive: you receive a paper 2-3 days prior and must discuss its contribution, methodology, results, strengths/weaknesses, and possible extensions. Behaviorals carry lab phenotypes: OpenAI wants "AGI focus" and scrappy velocity, Anthropic wants safety-first alignment convictions and Constitutional AI enthusiasm, DeepMind wants "Googleyness & Leadership." Common switch-ins: senior SWE to RE with a research portfolio, ML Engineering Lead to RE with eval publications, and Senior ML Platform Engineer to RE with a kernel/Triton stack. ARENA's 4-5 week in-person bootcamps are the single most-targeted career-building program for alignment REs, with non-trivial alumni density at Anthropic and DeepMind safety roles.

Resources to learn from

Books

  • Ian Goodfellow, Yoshua Bengio & Aaron Courville, Deep Learning — The foundational math and DL reference; best for refreshers on theory.
  • David MacKay, Information Theory, Inference, and Learning Algorithms — Depth on information theory; a frontier-lab math signal.
  • Sebastian Raschka, Build a Large Language Model (From Scratch) — From-scratch LLM build covering pretraining and finetuning internals.
  • Jay Alammar & Maarten Grootendorst, Hands-On Large Language Models — Visual plus code coverage of RAG and applied LLMs.

Courses

YouTube channels

  • Andrej Karpathy — Build neural networks from scratch; the canonical first course for internal mechanics.
  • Yannic Kilcher — Daily paper explainers at researcher pace; best for staying current and paper-discussion practice.
  • Sebastian Raschka — 306 videos; the "Build a Large Language Model From Scratch" companion channel.
  • StatQuest with Josh Starmer — 1.66M subscribers; clear math intuition to sharpen foundations.
  • Machine Learning Street Talk — Long-form interviews with frontier researchers; best for building research taste.

Blogs & newsletters

  • Ahead of AI (Sebastian Raschka) — Jan-May 2026 LLM papers list (Jun 6, 2026); the quarterly paper cadence.
  • Interconnects (Nathan Lambert) — Daily post-training commentary; best for RLHF/DPO/GRPO depth.
  • Lilian Weng's blog — Long-form technical posts on RLHF, agents, and diffusion (lilianweng.github.io).
  • Tri Dao's blog and Twitter — FlashAttention v3 author; the canonical low-level LLM-systems voice on memory-efficient attention, Triton, and kernels.
  • Anthropic Research (Interpretability team) — Interpretability posts; core Anthropic-specific prep.
  • AI Alignment Forum — Community blog for technical AI alignment research: interpretability, safety, evals.

Papers & docs

Communities worth joining

  • EleutherAI Discord — Grassroots open-source AI research; strongest LM-internals community for pretraining, evals, dataset curation.
  • AI Alignment Forum — Blog plus forum for alignment research discussions.
  • Latent Space Discord — Practitioner interviews plus a weekly Paper Club; frontier-engineering talk.
  • Hugging Face Discord — Largest HF-specific server; transformers/peft/TRL help.
  • r/MachineLearning — Premier AI subreddit; paper announcements and technical discussion.
  • r/LocalLLaMA — Local/open-model community; the open-weight frontier ecosystem.
  • ARENA alumni network — Direct alignment-RE cohort after a 4-5 week bootcamp.
  • AI Safety Fundamentals (BlueDot Impact) — Curriculum-based community on alignment and reproducibility.
  • Anthropic "Research Engineer, Interpretability" listing — A discrete, recurring RE role signaling a structured interpretability career path.
  • Events: COLM, NeurIPS, ICML, ICLR — Plus AI Engineer World's Fair, alignment workshops (AI Safety Camp), and Anthropic Fellows events.

Sources

05 · The difference

Research engineer vs research scientist vs ML engineer

Lines blur at the labs, where many people do both research and engineering.

Research scientistML engineerResearch engineer
Main questionWhat should we try?How do we serve this in a product?How do we make this experiment work at scale?
OutputIdeas, papers, resultsModels in productionTraining and eval infrastructure, results
Typical backgroundPhD commonSoftware or ML engineeringStrong engineering, research exposure
WhereLabs, universitiesProduct companiesAI labs and research-heavy startups

06 · The interview

The research engineer interview

Heavy on engineering, with real ML depth.

  1. Coding

    Strong Python, sometimes systems-level code; often practical rather than puzzle-style.

    Every loop
  2. ML implementation

    Implement a model component or training step from scratch and debug it.

    The core round
  3. Systems and scale

    Distributed training, memory, throughput and what breaks at scale.

    Labs
  4. Research discussion

    Talk through a paper or your own experiments: what you tried, what failed, what you concluded.

    Most loops

07 · Hiring

Who is hiring research engineers

716 open roles at 320 companies, refreshed daily. Each links to the company's own page.

08 · Where

Research engineer jobs by country

66% of Research engineer roles are in the US, led by San Francisco and New York. 16% are remote.

09 · Hiring now

Research engineer jobs

716 open today. The newest openings first, from the companies' own career pages.

  • Research Engineer67
  • AI Research Engineer19
  • Senior Operations Research Engineer14
  • Senior Security Research Engineer11
  • Senior Research Engineer9
  • Security Research Engineer6
  • ML Research Engineer5
  • Applied AI Research Engineer4
  • Machine Learning Research Engineer4
  • Member of Technical Staff, Research Engineer4

Lab roles fill fast. Apply the day they open.

landed watches research engineer roles at the labs and research startups and applies within the hour. 10 free applications, no card.

Start applying free →

FAQ

Research engineer, answered

What is a research engineer?

A research engineer builds the code, infrastructure and experiments behind AI research: training runs, evaluation pipelines, data systems and the tools researchers use, often running experiments themselves.

How much does a research engineer earn?

Across 330 live Research engineer postings on landed that publish pay, the median range is $190k to $300k in USD base, before equity and bonus. Senior roles at AI labs post well above that.

Who is hiring research engineers?

landed tracks 716 live Research engineer roles at 320 companies. Nanyang Technological University, Anthropic, Mistral AI, OpenAI, Miratech, Qualys, Harvey and NVIDIA have the most open right now.

Are Research engineer jobs remote?

16% of live Research engineer postings on landed are fully remote. Most of the rest are hybrid in the biggest tech cities.

Do I need a PhD to be a research engineer?

No. Many lab research engineers have no PhD. Strong engineering, hands-on model training and clear experiment write-ups matter more; a PhD is more common for research scientist roles.