Google DeepMind logo

Google DeepMind Research Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 34 interview experiences · FREE TO READ

3.3 Rounds average
Difficult Typical difficulty
64.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Google DeepMind.

Showing 3 of 34
Google DeepMind logo
Google DeepMind

Research Engineer

Research · more than a year ago

Entry Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

I applied in Dec 2021 and heard back in March 2022. They gave me some study stuff for CS, Maths, Stats, and ML. Then I had a technical interview where they asked me some practical questions about integrals and statistical theorems.

Confirmed questions5 questions
  • Questions about basic Machine Learning concepts.
  • Questions about statistical theories.
  • Questions on mathematical problems, specifically including integrals.
Google DeepMind logo
Google DeepMind

Research Engineer/Scientist

Research · more than a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Technical Coding Behavioral

I had an initial chat with a hiring manager and a recruiter. From those conversations, it sounded like it would be a great fit and that they would value me for all my experience. They described work that sounded like it would capitalize on my background while still allowing me room for growth. The recruiter acknowledged that I should be hired into a higher level role. I had one interview with a Research Scientist in London and two interviews with Software Engineers in Mountain View. The interview with the Research Scientist was interesting. They asked good questions that gauged problem solving and creativity. We had a good conversation. I felt like he was respectful, collaborative, and appreciated my background. Both of the interviews with the Software Engineers were disappointing. They asked questions appropriate for someone with less experience and were focused more on implementation rather than research. That would have been fine if they asked language-agnostic, algorithmic questions. But, the questions were obviously designed for python and were mostly testing off-hand knowledge of specific built-in text parsing functions. It was the sort of thing that anyone could have done easily in 5 minutes at their desk with the ability to look things up, but python is not my primary language and I don't do much text parsing. Both of them were very unwelcoming. Their comments made it clear that they had very rigid ideas about career paths and had a very different idea about the position for which I was being interviewed than the hiring manager. It very much felt like they were gatekeeping.

Confirmed questions2 questions
  • The first interview was a fun exercise that required problem-solving, creativity, and data analysis skills, and we talked through many possibilities for approaching the problem.
  • Two interviews measured familiarity with python, specifically text parsing functions.
Google DeepMind logo
Google DeepMind

Research Engineer

Research

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Coding Technical

The interview process had three stages. First, a recruiter call. Second, two coding interviews and one ML fundamentals interview. Third, ML design and an interview with the Lead Researcher. I didn't do well in one of the coding interviews at the second stage. The coding interviews were Leetcode mediums, and the ML fundamentals interview covered optimization, regularization, loss functions, transformers, and practical training/inference questions.

Confirmed questions1 question
  • Could you describe a string parsing question where you had to evaluate a mathematical expression?

Google DeepMind Research Engineer Interview Questions

Quoted word for word from Google DeepMind interview reports.

What are the limitations of neural networks when they are used as universal approximators?

Read reports

What's the formula for the Taylor series, why does it make sense, and what's the reason for the 1/n! term?

Read reports

Explain Newton's method, where it comes from, and how to use it for finding a function's minimum.

Read reports

When you multiply two orthogonal vectors, what is the outcome?

Read report

Solve a Python problem similar to Hackerrank in a Jupyter notebook.

Read report

Can you explain how to compute L matrix multiplication?

Read report

Formats, difficulty and experience

Across all 34 Google DeepMind interview reports.

Interview formats

Technical 42%
Coding 30.7%
Behavioral 22.7%
System Design 2.3%
Other 1.1%

Interview difficulty

Easy 2.9%
Average 41.2%
Difficult 55.9%

Candidate experience

Positive 64.7%
Neutral 20.6%
Negative 14.7%