How Google DeepMind Interviews in 2026: Process, Questions & What They Score
The complete process, reported questions, and what interviewers score.
Google DeepMind / Interview snapshot
6
stages from
application to offer
33
reported questions
4-10
weeks, typically
20
public sources
Independent: SupaCV is not affiliated with or endorsed by Google DeepMind. This is one well-documented shape of Google DeepMind's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.
On this page
01 / For every Google DeepMind candidate
The process, start to finish.
Google DeepMind (formed in 2023 when DeepMind and Google Brain merged) hires on several tracks: Research Scientist, Research Engineer, Software Engineer, plus product, program and operations roles. This playbook covers the research tracks (Research Scientist and Research Engineer), which the company is best known for. Software Engineer material sits in its own question category: the system design prompts from one guide, the code review and Gemini API prompts, and the Educative infrastructure examples come from Software Engineer guides.
DeepMind's official guide lists four stages: Initial interviews, Skills interviews, Final interviews, and Decision and offer. It says the process takes 4-10 weeks depending on the role, and longer if interviewers are hard to schedule. Most interviews are virtual. You may use AI to prepare, but AI tools are not allowed in live interviews or interview tasks unless you are told otherwise. Initial interviews start with a 30-minute recruiter call, sometimes followed by a hiring manager conversation.
Skills interviews are two or three calls in which you meet potential peers; the official pages do not say what they cover, but third-party accounts and a 2022 forum reply from a DeepMind researcher describe, for research roles, a theoretical quiz on math/stats and ML/AI (one aggregator adds CS fundamentals) plus coding. Final interviews are with team leads and leadership and cover core skills, team goals and culture, mission and values; third-party guides add paper discussion for research roles.
DeepMind says many interviews are competency-based, recommends the STAR method, and says candidates are "assessed on clearly defined criteria". It does not publish those criteria or any named competency or values list, so no evaluation framework is included here. The question bank comes mostly from third-party prep guides and aggregators. These questions are not cross-checked against Glassdoor, igotanoffer, Dataford, 1point3acres or Medium, so treat them as indicative, not verified.
Stage 1: Before the interview stages: application review and referral
varies
Not one of the four official stages. You apply on the careers site and the Talent Acquisition team reviews the application. Referrals must come from someone who can vouch for your work and your alignment with DeepMind's mission and values; employees do not refer people who only contacted them online. If you are invited, a Scheduling Coordinator gets in touch and you sign a standard NDA electronically through a third-party tool. No source gives a duration for this step; it varies by role and team.
Pre-stage from the official guide's How to apply section, not one of the four named stages.
Stage 2: Initial interviews: recruiter call, possibly a hiring manager conversation
About 30 min for the recruiter call; third-party guides put the hiring manager screen at 30-45 min
The official careers page describes a 30-minute introductory recruiter call about your background, the role and why you applied, with a possible hiring manager conversation. Third-party guides say the recruiter also confirms which track you are on and your target level. One applicant in a 2022 thread on DeepMind's alignment-team hiring post reported being asked to schedule two 30-minute introductory interviews.
Stage 3: Skills interviews: technical quiz and coding
2-3 interviews; third-party guides report about 45-60 min each
Officially, two or three further calls assess you against the competencies and skills the role needs, and you meet potential peers; the official pages give no per-call durations and do not describe quiz, math or coding content. In a 2022 thread on DeepMind's alignment-team hiring post, an applicant listed a technical quiz plus a coding interview as phase two. DeepMind researcher Rohin Shah, replying in that thread about the Research Engineer stage, said the math/stats and ML/AI parts are more like factual or theoretical questions, that you might have to derive some results in the interview, and that the stage is standardized across DeepMind. In a 2023 Blind thread, one commenter said math/stats questions are still asked but seem different from earlier years, when they were a 2-hour exam-like format (hearsay from an anonymous commenter); another said the first interview covers that. Third-party guides describe coding at LeetCode medium to hard level and say the research tracks add ML fundamentals. One aggregator lists two quizzes of about 60 min each plus a 60-min coding round.
Official FAQ: unless told otherwise, do not use any AI tools during live interviews or interview tasks.
Stage 4: Final interviews: research, team lead and leadership rounds
varies
Officially, you meet team leads and leadership, including your potential manager, and discuss core skills in the context of team goals, future plans, and culture, mission and values. DeepMind frames it as a mutual assessment. The length of the loop varies by level and track. For research tracks, third-party guides describe paper discussion or a research talk (often 60 min; one guide says research candidates often do 2-3 such rounds), research problem framing, ML coding, and math and theory rounds. One aggregator lists two 60-minute team lead rounds covering resume deep-dives, open-ended ML problems and behavioral questions. Round counts differ: two guides say 5-7 rounds (one gives 4-6 for Software Engineer) and a third says 4-5 onsite rounds. Those guides use their own structure (recruiter, hiring manager, technical phone screen, virtual onsite, committee) and none maps it to DeepMind's four stages, so some rounds listed here may be what DeepMind calls skills interviews.
Stage 5: Culture interview (reported by third parties, not a separate official stage)
45-60 min (two third-party sources, for specific tracks)
The 2022 thread on DeepMind's alignment-team hiring post lists a culture interview as phase four after the research interviews; Rohin Shah said he thought phases three and four happen at the same time. One aggregator lists a 45-60 minute People and Culture round, and one guide lists a 45-minute behavioral and culture round in its Research Scientist loop. The official page folds culture into the final interviews.
Not one of the four official stages; the official pages place culture, mission and values inside the final interviews.
Stage 6: Decision and offer
varies; third-party guides report 2-4 weeks of committee review after the final rounds
Officially, the hiring team reviews your application against its criteria, and if you are the top candidate a recruiter shares the news, discusses compensation and benefits, and formally invites you to join. The official FAQ says silence for a few days is not bad news and suggests checking with your recruiter after more than a week without feedback. Third-party guides describe a slow hiring committee: 3-4 weeks in one guide, and 2-4 weeks in another that also says 3-4 weeks elsewhere on the page. Officially, the whole process takes 4-10 weeks depending on the role; three third-party guides say 6-10 weeks.
02 / What Google DeepMind scores
No publicly documented framework
03 / Coach's notes
Coach's tips.
01
Confirm your track (Research Scientist, Research Engineer or Software Engineer) and level with the recruiter before you prepare. The loops differ: third-party guides list math/theory and paper rounds for the research tracks that they do not list for the Software Engineer loop.
02
Practice coding and derivations without any assistant. DeepMind's official FAQ says you are free to use AI to prepare but not to use AI tools during live interviews or interview tasks unless you are told otherwise.
03
For research roles, expect a theoretical screen on math/stats and ML/AI where you may need to derive results live; a DeepMind researcher said in 2022 that this stage is standardized across DeepMind. One guide lists gradients, KL divergence, sampling and convergence proofs, and several guides say to be ready to implement attention, losses and training loops from scratch.
04
Use STAR and include data. DeepMind says many interviews are competency-based and assessed on clearly defined criteria, and tells candidates to use data to show their impact. Its guide also says it values curiosity and intellectual honesty: if you do not have the answer, say you are not sure, ask questions and explain your reasoning out loud.
05
Do the homework DeepMind asks for. Read its blog and research, think about how the mission resonates with you, and try Gemini and Google AI Studio. One aggregator also lists questions asking you to name a specific recent DeepMind paper or system and to explain why DeepMind rather than another lab, so prepare both.
06
Pick a paper you can defend for an hour, since the guides describe a 60-minute round that probes methodology, weaknesses and extensions. One guide also suggests preparing two DeepMind papers in depth because interviewers may include their authors. Plan for a 4-10 week process, and check with your recruiter if you have no feedback after more than a week.
04 / The research
Where this page comes from.
Compiled from public sources across 15 sites.
- sites
- 15
- coaching and prep guides
- 18
- candidate reports and forums
- 2
Source composition
Where the research comes from
Grouped by the kind of site that published each source: Google DeepMind's own domain, candidate forums, and everything else.
- Coaching and prep guides18
- Candidate reports and forums2
05 / The questions
Reported questions, by category.
Showing questions for
Roles are grouped by the category each question fits, not by the source.
Coding and ML coding
4 questions
Implement merge intervals. Then a variant: given streaming intervals, maintain the merged set efficiently.
Tests interval sorting and merging, then incremental updates to a merged set using an ordered structure.
Implement gradient descent for logistic regression from scratch (numpy, no scikit). Discuss convergence, learning rate, and batch vs SGD.
Tests implementing logistic regression gradient descent in numpy, with learning rate, convergence and batch versus SGD tradeoffs.
Implement a piece of an ML pipeline by hand with no libraries and no AI tools, for example attention, a loss function, a sampling routine, a data pipeline or a training loop.
Tests from-scratch ML implementation of attention, losses, sampling or training loops with no libraries or AI help.
Write a module to process multimodal data, with attention to scalability and performance testing.
Tests designing a data-processing module with scalability in mind and a plan for performance testing.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
ML systems and design
5 questions
How could user feedback be leveraged for model optimization in recommendation systems?
Tests using feedback signals to improve a recommender: training objectives, ranking, bias and feedback loops.
How do you handle test set contamination?
Tests evaluation integrity: detecting and preventing benchmark data leaking into training sets.
How do you ensure reproducibility?
Tests experiment reproducibility: seeds, versioned code and data, config tracking and deterministic pipelines.
We need to train a 100 billion parameter model, but it will not fit in memory. How would you design data and model parallelism?
Tests distributed training design: data, model and pipeline parallelism and memory tradeoffs for a 100B model.
Design a scalable recommender system handling billions of items, covering candidate generation, ranking, retrieval and A/B testing.
Tests recommender architecture: candidate generation, ranking, retrieval stages and A/B testing at billions of items.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Software Engineer loop
7 questions
Review this broken or suboptimal code as you would a pull request, covering correctness, performance and clarity of feedback.
Tests code review skill: finding bugs, spotting performance problems and giving clear, respectful feedback.
Design a global API for Gemini.
Tests global API design: multi-region serving, latency, scaling and reliability for a model endpoint.
Design a serving system for a 100B-parameter model at scale.
Tests large-model inference design: model sharding, batching, latency, throughput and cost at scale.
Build an evaluation pipeline that runs thousands of benchmarks nightly.
Tests batch pipeline design: scheduling, scale-out, result storage and reliability for nightly benchmark runs.
Design a feature store for an ML experimentation platform.
Tests ML platform design: online and offline feature serving, consistency and versioning.
A distributed training workload runs across hundreds of machines and one worker fails several hours into the job. How do you handle it?
Tests fault tolerance in distributed training: checkpointing, retries and recovery after a worker fails.
Design a platform that lets internal teams submit computationally expensive AI experiments and monitor their execution, recovering gracefully from infrastructure failures.
Tests job-platform design: experiment submission, scheduling, execution monitoring and failure recovery.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
ML and math fundamentals
8 questions
What's the difference between L1 and L2 regularization? When would you use one vs the other? Walk through the geometry.
Tests regularization theory: L1 sparsity versus L2 shrinkage, explained through constraint-region geometry.
Walk through reinforcement learning fundamentals: MDPs, value functions, policy gradient, and the pitfalls of reward shaping.
Tests RL theory: MDP formalism, value functions, policy gradients and how reward shaping can distort the learned policy.
Explain quaternions vs Euler angles for 3D rotation. What is gimbal lock? When does it occur?
Tests 3D rotation math: quaternion versus Euler-angle representations and why gimbal lock occurs.
Math and theory round: expect questions on gradient computation, KL divergence properties, sampling algorithms and convergence proofs.
Tests probability and optimization theory: gradient derivation, KL properties, sampling methods and convergence arguments.
Explain the difference between supervised and unsupervised learning.
Tests ML basics: labeled versus unlabeled data, learning objectives and typical algorithms for each.
What are the key differences between gradient descent and stochastic gradient descent?
Tests optimization basics: full-batch versus stochastic updates, gradient noise, per-step cost and convergence.
Explain the concept of overfitting and how to mitigate it in machine learning models.
Tests generalization: spotting overfitting and fixing it with regularization, more data, early stopping or simpler models.
What is the importance of Markov Decision Processes (MDPs) in reinforcement learning?
Tests RL foundations: states, actions, transitions and rewards, and why the Markov property makes the problem tractable.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Research and paper discussion
3 questions
Present and defend a recent paper you choose: methodology, weaknesses, alternative approaches and how you would extend it.
Tests depth on one paper: methodology, weaknesses, alternative approaches and extensions under probing.
Frame an open-ended research problem the interviewer poses: propose how you would investigate it.
Tests turning an open-ended problem into a research plan with hypotheses, experiments and evaluation.
Discuss your most impactful research project. What was the methodology? What are the limitations? What would you change?
Tests depth and ownership of your own research: methodology choices, limitations and what you would change.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Every role
Motivation and behavioral
6 questions
Why DeepMind specifically (vs OpenAI, Anthropic, Google Research)?
Why do you want to work at Google DeepMind?
What recent DeepMind paper or system have you engaged with substantively?
How do you handle disagreements in a team setting?
Describe a project where your AI solution failed and how you addressed it.
Share an experience where you solved a complex problem collaboratively.
Your next step
Interviewing at Google DeepMind?
Make sure your resume gets you to the first round.
Practicing for Google DeepMind against your resume is in Interview Prep on Career.
Common questions
Quick answers.
How many stages are in Google DeepMind's interview process?
Google DeepMind has 6 stages, set out in The process.
Does Google DeepMind have an official interview framework?
Google DeepMind has no publicly documented framework, as set out in What Google DeepMind scores.
What kinds of questions does Google DeepMind ask?
Google DeepMind's questions fall into 6 categories, grouped in The questions.
How reliable is this Google DeepMind interview playbook?
It is compiled from public sources, and the evidence is in The research.
Sources (20)
Every public source this page was compiled from. Links open in a new tab.
15 sites, by sources
- deepmind.google3
- greaterwrong.com2
- teamblind.com2
- educative.io2
- storage.googleapis.com1
- techinterview.org1
- designgurus.io1
- jobsbyculture.com1
- applr.ai1
- extrabrain.app1
- techprep.app1
- aced.io1
- 4dayweek.io1
- finalroundai.com1
- jobmentis.com1
- 01deepmind.google/about/careers
- 02deepmind.google/careers
- 03deepmind.google/about
- 04storage.googleapis.com/deepmind-media/DeepMind.com/Assets/Docs/interviewing-a…
- 05greaterwrong.com/posts/nzmCvRvPm4xJuqztv/deepmind-is-hiring-for-the-sca…
- 06greaterwrong.com/posts/nzmCvRvPm4xJuqztv/deepmind-is-hiring-for-the-sca…
- 07teamblind.com/post/interviews-for-research-engineer-at-deepmind-kd1t…
- 08teamblind.com/post/research-engineerscientist-interview-wfj6gfh2
- 09techinterview.org/post/3233474918/deepmind-interview-process-2026
- 10designgurus.io/answers/detail/what-is-the-google-deepmind-interview-p…
- 11jobsbyculture.com/blog/deepmind-interview-prep-2026
- 12applr.ai/en/ai-mock-interview/deepmind/research-engineer
- 13extrabrain.app/interview-questions/how-i-became-deepmind-research-eng…
- 14educative.io/blog/google-deepmind-software-engineer-interview
- 15educative.io/blog/google-deepmind-interview-questions
- 16techprep.app/blog/deepmind-interview-process
- 17aced.io/guides/google-deepmind-product-manager-interview
- 184dayweek.io/interview-process/deepmind-interviews
- 19finalroundai.com/blog/ai-researcher-interview-questions
- 20jobmentis.com/en/interviews/deepmind/swe
Related reading
- Jake's Resume: Why One LaTeX Template Took Over Tech HiringThe history behind the internet's most-copied resume template, why its formatting choices actually work, and how to get the same layout without touching LaTeX.
- Where the "75% of Resumes Are Rejected by ATS" Stat Came FromThe paper trail behind the most-repeated statistic in job search advice, what applicant tracking software actually does, and what really causes instant rejection.
How similar companies interview
Compare Google DeepMind's process with other High-Growth Tech & AI companies in this playbook: