Google DeepMind Research Engineer Interview Guide

Dan Lee's profile image
Dan LeeData & AI Lead
Last update
Google DeepMind Research Engineer Interview Guide

The short answer: Google DeepMind publishes four interview stages: initial interviews with a 30-minute recruiter call, two or three skills interviews with potential peers, final interviews with team leads and leadership, then a decision. It says the process takes 4 to 10 weeks, most interviews are virtual, and you may use AI to prepare but not during live interviews or interview tasks unless told otherwise. Candidate reports say research engineer skills interviews include coding rounds where the code must run and ML rounds on fundamentals, maths, probability and ML design. Older reports describe a factual maths, ML and computer science quiz, and reports disagree on whether it is still used. Last reviewed October 2026.

Google DeepMind Research Engineer at a Glance

Base Salary (US postings)

$147k - $364k/yr

Levels

Research Engineer - Senior Staff

Python C++Gemini pretraining and post-trainingGenerative mediaRoboticsAI safety and securityEvaluations (Polaris)

Google DeepMind research engineer interview: quick answers

QuestionShort answer
How many interview rounds?Google DeepMind lists a recruiter call (sometimes with a hiring manager interview), two or three skills interviews with potential peers, and final interviews with team leads and leadership.
What do the rounds test?DeepMind says skills interviews test the competencies for the role. Candidate reports describe medium to hard algorithm problems where the code must run, and ML rounds on fundamentals, maths and probability, and ML design.
Can I use AI tools?Only to prepare. DeepMind says you are free to use AI to help you prepare, but unless told otherwise you should not use any AI tools during live interviews or interview tasks.
How much does a Google DeepMind research engineer make?US postings list base salary from $147K to $252K for most Research Engineer titles, $207K to $300K for Staff and $262K to $364K for Senior Staff, plus a bonus target and equity.
How long does it take?DeepMind says 4 to 10 weeks depending on the role, possibly longer. Feedback after the finals usually comes within days.
Is it the same as a Google interview?No. DeepMind says its process is run by a different team from Google's, and asks you to tell your DeepMind recruiter if you are also interviewing at Google or another Alphabet company.

The Google DeepMind research engineer role

What Google DeepMind research engineers work on, the skills its job postings ask for, and what a week can look like. Google DeepMind posts the role as Research Engineer, <team>, DeepMind (for example Gemini Large Scale Pretraining, Robotics, Polaris), with Senior, Staff and Senior Staff titles and some combined Research Scientist/Engineer roles.

Primary Focus

Gemini pretraining and post-trainingGenerative mediaRoboticsAI safety and securityEvaluations (Polaris)

What You Need

  • 2 years of software engineering with Python ML libraries such as JAX (Gemini pretraining)
  • 1 year of ML experience (Gemini pretraining)
  • 5 years with TensorFlow, JAX or PyTorch (Gen Media)
  • 2 years in applied research (Gen Media)
  • Building and debugging software for simulated and physical robots (Robotics)
  • Implementing and optimizing frontier models

Nice to Have

  • Large-scale, distributed systems or performance engineering (Gemini pretraining)
  • Diffusion model training (Gen Media)
  • Physics simulators such as MuJoCo or Isaac Sim (Robotics)
  • Competitive programming or maths olympiad experience (Polaris)

Languages

PythonC++

Tools & Technologies

JAXPyTorchTensorFlowMuJoCoIsaac Sim

Want to ace the interview?

Practice with real questions.

Start Mock Interview

A Week in the Life of a Google DeepMind Research Engineer

Illustrative week · Google DeepMind

An illustrative week for a research engineer, built from what Google DeepMind says about the role in its own job postings and publications. Real weeks vary by team.

Culture notes

  • DeepMind describes research engineers as experimentalists who bridge theory and implementation, and their work often leads to paper co-authorship.
  • Most staff are in the office Tuesday to Thursday and work from home on Monday and Friday.
  • The Polaris team favors fewer hand-built, realistic eval tasks over synthetic pipelines.

Key takeaway: Expect to build and scale the systems that test research ideas, working closely with research scientists.

Google DeepMind research engineer levels and pay

Your level sets the bar you are interviewed against and the pay band of the offer.

Google DeepMind Research Engineer Levels

Each level has different expectations, compensation, and interview focus.

What This Level Looks Like

Builds and scales the systems that test research ideas on one team, such as Gemini pretraining or robotics.

Interview Focus at This Level

Candidate reports describe coding rounds where code must run, plus ML fundamentals, maths and ML design.

Find your level

Practice with questions tailored to your target level.

Start Practicing

Google Careers shows title prefixes (Research Engineer, Senior, Staff, Senior Staff) but no level codes on these postings. Ranges overlap across titles, so the table lists postings.

Pay in Google DeepMind's US job postings

Google DeepMind's US research engineer roles are posted on Google Careers. Each lists a base salary range plus a bonus target and equity.

Bonus targets seen were 15% for Research Engineer and Senior Research Engineer, 20% for Staff and some Research Engineer titles such as Responsibility and the Tech Lead Manager role, and 25% for Senior Staff. The Polaris posting also lists total compensation of $550K to $1.1M. No London or other non-US ranges are published. Ranges seen October 29, 2026.

Google DeepMind research engineer interview process

Google DeepMind publishes its interview stages on its careers page and in its interviewing guide, and says exact steps differ by role. The content of the research engineer rounds comes from candidate reports.

~4 to 10 weeks end to end

Screen

2 rounds
1

Initial interviews

30mVideo call with a recruiter, sometimes a hiring manager

DeepMind says the recruiter asks about your background, experience and why you applied, and the hiring manager asks about specific capabilities for the role.

generalbehavioral

Tips for this round

  • Have a clear answer to why DeepMind and why this team.
  • Tell the recruiter if you are also interviewing at Google, as DeepMind asks.

Onsite

1 round
3

Final interviews

Meetings with team leads and leadership

DeepMind says these look at your core skills in the context of the team's goals, plans, culture, mission and values. Candidate reports describe conversations with tech leads about your background and ML experimentation, plus a people and culture interview.

research_discussionbehavioral

Tips for this round

  • Prepare to discuss how you design and run ML experiments, which candidate reports say tech leads ask about.
  • Use the STAR method, since DeepMind scores competencies on defined criteria.
  • Read about the team's goals and recent work so you can connect your skills to them.

Tips to Stand Out

  • Read the Google DeepMind blog, try Gemini models in Google AI Studio and listen to the DeepMind podcast, as DeepMind suggests.
  • Map your experience to the job description before each stage.
  • Think out loud, say when you are unsure and explain your reasoning, which DeepMind asks for.
  • Use data to show the impact of your work, and answer competency questions with the STAR method.
  • Practice with Google's own interview practice tool and coding prep video, which DeepMind points candidates to.

Common Reasons Candidates Don't Pass

  • ✗Candidate reports describe passing the hiring committee but stalling in team matching, with feedback about too little ML experimentation and modeling experience.

Based on Google DeepMind's own pages and candidate reports.

DeepMind says the whole process takes 4 to 10 weeks depending on the role, possibly longer, and that candidates sign a standard NDA electronically before interviewing. Invited candidates get prep information for each stage of their role. Last reviewed October 2026.

What is different at Google DeepMind

  • DeepMind defines the role. It describes research engineers as experimentalists who bridge theory and implementation, designing and scaling systems to test new ideas, which often leads to co-authoring papers. Research Scientists normally hold a PhD and form new hypotheses and algorithms, and Software Engineers build and maintain software for research.
  • The quiz is a known feature. Candidate reports from 2021 and 2022 describe a factual quiz on maths and statistics, ML and computer science, mostly theory with some derivations. Reports disagree on whether it still runs, and 2026 candidate guides describe ML depth rounds instead.
  • Interviews are competency-based. DeepMind recommends the STAR method and says every candidate is scored on clearly defined criteria.
  • AI is for prep only. DeepMind says you may use AI to prepare, but not during live interviews or interview tasks unless told otherwise.
  • US roles are posted on Google Careers with Google-style pay: a base range, a bonus target and equity. DeepMind runs its own interview process, separate from Google's.
  • Polaris is open to people without degrees. The Research Engineer, Polaris posting has no education or prior work requirement and prefers competitive programming or maths olympiad experience. Its engineers hand-build long-horizon software engineering eval tasks for Gemini, each taking about a week.

Google DeepMind research engineer interview questions

Questions from our bank, then practice prompts we wrote for this guide around Google DeepMind's work.

Questions from our bank

From the DataInterview question bank: questions tagged to Google DeepMind first, then questions that fit research engineer interviews. Open one to answer it.

ML coding practice

Prompts we wrote for this guide around Google DeepMind's work. They are not reported interview questions. Each answer is an outline or a worked solution.

Write a numerically stable softmax cross-entropy loss and its gradient with respect to the logits, in NumPy.

MediumML Coding

Sample Answer

Subtract the max logit from each row before applying exp, so large logits do not overflow. Compute the log-sum-exp as max + log(sum(exp(z - max))), and the loss as log-sum-exp minus the logit of the true class, averaged over the batch. The gradient is softmax(z) minus the one-hot target, divided by the batch size. Check it with a finite-difference gradient on a small random input.

Practice more questions

Research discussion practice

Prompts we wrote for this guide around Google DeepMind's work. They are not reported interview questions. Each answer is an outline or a worked solution.

Polaris hand-builds a small number of realistic eval tasks instead of generating many synthetic ones. What are the trade-offs?

MediumResearch

Sample Answer

Hand-built tasks are closer to real long-horizon work and are harder to game, so a gain on them is more likely to mean a real capability gain. They are expensive, about a week each, so the set is small and each score has a wide confidence interval. Synthetic pipelines give many tasks cheaply but can share artifacts the model learns to exploit. A strong answer suggests using both and checking whether they rank models the same way.

Practice more questions

Fundamentals practice

Prompts we wrote for this guide around Google DeepMind's work. They are not reported interview questions. Each answer is an outline or a worked solution.

A test for a rare condition has 99% sensitivity and 95% specificity, and 1% of people have the condition. If someone tests positive, what is the chance they have it?

MediumFundamentals

Sample Answer

Out of 10,000 people, 100 have the condition and 99 of them test positive. Of the 9,900 without it, 5%, or 495, test positive. So P(condition | positive) = 99 / (99 + 495) = 99 / 594, about 16.7%. The low base rate drives the answer.

Practice more questions

Behavioral practice

Prompts we wrote for this guide around Google DeepMind's work. They are not reported interview questions. Each answer is an outline or a worked solution.

Tell me about an ML experiment you designed that changed what your team did next.

MediumBehavioral

Sample Answer

DeepMind calls research engineers experimentalists. Use STAR: the question, how you designed the experiment, the result with numbers and the decision it led to.

Practice more questions

Practice problem: score a coding eval with pass@k

python

An eval team samples n solutions per task and records whether each one passed. The unbiased estimate of pass@k for a task with n samples and c passes is 1 - C(n - c, k) / C(n, k), where C is the binomial coefficient. Write pass_at_k(results, k), where results maps each task id to a list of booleans. Return the mean pass@k over tasks, rounded to 4 decimals, or 0.0 if there are no tasks. Raise ValueError if k < 1 or any task has fewer than k samples. Example: {"a": [True, False, False, False], "b": [False, False]} with k = 2 gives task a 1 - 3/6 = 0.5 and task b 0.0, so the result is 0.25.

Python
1from typing import Dict, List
2
3def pass_at_k(results: Dict[str, List[bool]], k: int) -> float:
4    """Mean unbiased pass@k over tasks, rounded to 4 decimals."""
5    pass

700+ coding problems with a live code executor.

Practice in the Engine

How to prepare

A plan for the Google DeepMind loop, most important first:

  1. Practice medium to hard algorithm problems in Python until you can write code that runs on the first try, since candidate reports say it must run.
  2. Review maths and statistics, ML theory and CS fundamentals for factual questions and short derivations, in case your loop has a quiz-style round.
  3. Practice ML design and ML coding: losses and gradients, training loops, RL estimators and how you would test a research idea at scale.
  4. Prepare STAR stories with numbers on impact, mapped to the job description, since DeepMind scores competencies on defined criteria.
  5. Read the DeepMind blog and recent papers from your target team, and try Gemini in Google AI Studio.
  6. Practice without AI tools, since DeepMind allows AI only for preparation unless you are told otherwise.

Practice path

Courses that cover the rounds above:

Are you ready for the Google DeepMind research engineer interview?

1 / 6
Machine Learning

Can you implement attention, a training loop or a tokenizer from scratch in PyTorch or NumPy, and debug it?

Frequently Asked Questions

How many rounds is the Google DeepMind research engineer interview?

DeepMind publishes four stages: initial interviews (a 30-minute recruiter call and possibly a hiring manager interview), two or three skills interviews with potential peers, final interviews with team leads and leadership, then a decision. Candidate reports describe the skills interviews as coding and ML rounds.

Can I use AI tools in a Google DeepMind interview?

DeepMind says: "You're free to use AI to help you prepare for interviews. But – unless told otherwise – please don't use any AI tools during live interviews, or during interview tasks."

How much do Google DeepMind research engineers make?

In US postings seen in October 2026, most Research Engineer titles list $147K to $252K base, Staff and some Research Engineer titles such as Responsibility list $207K to $300K, and Senior Staff lists $262K to $364K. Bonus targets were 15%, 20% and 25%. The Polaris posting lists total compensation of $550K to $1.1M.

Does Google DeepMind still use the research engineer quiz?

Reports disagree. Candidate reports from 2021 and 2022 describe a factual quiz on maths and statistics, ML and computer science; one 2021 candidate said it had been replaced by two coding and two ML screens, and another said a two-hour quiz remained for some applicants. 2026 candidate guides describe ML depth rounds. Ask your recruiter.

How is a research engineer different from a research scientist at DeepMind?

DeepMind says Research Scientists normally hold a PhD and formulate new hypotheses and algorithms, while research engineers are experimentalists who build and scale the systems that test ideas. Some senior postings use a combined Research Scientist/Engineer title.

Where do Google DeepMind research engineers work?

US postings list Mountain View, San Francisco, New York, Cambridge (MA) and Kirkland, and some list London. DeepMind says most staff are in the office Tuesday to Thursday and work from home on Monday and Friday.

Can students or people without a degree join DeepMind?

The Student Researcher Program offers paid 12 to 24 week internships for enrolled BS, MS or PhD students, in person at a Google office. DeepMind says internships are run by Google Recruiting and applied for through Google careers. The Research Engineer, Polaris posting says no education or prior work experience is required.

Dan Lee's profile image

Written by

Dan Lee

Data & AI Lead

Dan is a seasoned data scientist and ML coach with 10+ years of experience at Google, PayPal, and startups. He has helped candidates land top-paying roles and offers personalized guidance to accelerate your data career.

Connect on LinkedIn