Google DeepMind operates a hiring process distinct from the rest of Google. The reason is structural: DeepMind hires across research, engineering, and applied tracks, with very different rubrics for each. The interview format for a research scientist working on Gemini training has almost nothing in common with the interview format for a software engineer working on the Gemini API. A candidate preparing without knowing which track they are applying to will misallocate effort.
This piece covers how DeepMind interviews in 2026, the four engineering tracks, and what makes the process different from both Google product teams and other AI labs.
The four tracks
- Research Scientist. PhD-track researchers working on novel ML research. Heaviest emphasis on publication record, paper discussion, and research-problem framing.
- Research Engineer. Engineers embedded in research teams. Significant ML domain expertise required, but more focus on building scalable training and evaluation systems than on novel research.
- Software Engineer. Engineers working on infrastructure, the Gemini API, internal tooling, and product surfaces. Closer to a standard FAANG senior+ loop.
- Applied AI Engineer / ML Engineer. Engineers applying ML in product or for specific customer problems. Mix of ML domain depth and standard software engineering.
Confirm with your recruiter which track you are applying to. The process and prep diverge substantially.
Standard loop structure
- Recruiter screen.
- Hiring manager screen.
- Technical phone screen (1-2 rounds).
- Onsite or virtual loop (5-7 rounds depending on level and track).
- Hiring committee review.
- Final review and offer.
Typical timeline is 6-10 weeks. Research roles take longer; the hiring committee for research scientists is rigorous and slow.
Research Scientist track
The signature track for DeepMind. Loop emphasizes:
- Paper discussion (60 min). The candidate selects a recent paper of theirs (or a paper they have read deeply if they have not published). The interviewer probes the methodology, motivation, weaknesses, and how the candidate would extend the work. The depth expected is rigorous — interviewers will push hard on assumptions.
- Research problem framing (60 min). An open-ended problem is presented. The candidate must propose how they would investigate it: what experiments, what metrics, what theoretical analysis, what would falsify the approach. Tests scoping ability under ambiguity.
- ML coding (60 min). Implement a piece of ML pipeline by hand — typically a custom loss, an attention mechanism, a sampling routine, or a small training loop. Almost always unaided. The interviewer is checking that the candidate can code ML primitives, not just consume them.
- Math and theory (60 min). Probability, linear algebra, optimization. Probes foundational depth. Common topics: gradient flow, Bayesian inference, convergence proofs, information theory.
- Behavioral and culture (45 min). Mission alignment, collaboration in research environments, history of past disagreements with collaborators.
Research candidates often go through 2-3 rounds of paper discussion with different interviewers, to test depth across multiple subdomains.
Research Engineer track
Less paper-heavy, more systems-heavy. Loop emphasizes:
- ML coding (60 min). Same as Research Scientist track but typically more involved — implementing larger pieces of pipeline.
- Distributed training systems design (60 min). How would you design a training system for a model that does not fit on a single accelerator? Pipeline parallelism, tensor parallelism, ZeRO, DeepSpeed-style optimizations.
- Evaluation infrastructure (60 min). Design an evaluation harness for a frontier model across many benchmarks. How do you handle test set contamination? How do you ensure reproducibility?
- Standard coding (60 min). A general algorithmic problem, often unaided.
- Behavioral.
Software Engineer track
Closer to a standard senior FAANG loop:
- 2 coding rounds (medium-to-hard, generally unaided).
- 1 system design round.
- 1 domain depth round (relevant to the team — could be ML serving, API design, infrastructure).
- 1 behavioral round.
The bar is comparable to senior+ Google product teams. The hiring committee process is similar.
AI tool policy
DeepMind’s policy in 2026 is generally AI-prohibited or heavily limited in technical rounds. The reasoning: research roles need to filter on unaided foundational reasoning; engineering roles work on infrastructure where the AI tools have less leverage anyway. This is more conservative than Anthropic’s policy and more uniform than OpenAI’s.
For specific applied roles where the work involves heavy AI tool use, individual interviewers may permit AI tools. This is the exception, not the default.
How DeepMind differs from Google product teams
Despite being part of Alphabet, DeepMind’s interview process differs from Google product team interviews in several ways:
- Stronger emphasis on research depth across all tracks.
- More rigorous paper discussion for research and research-engineer roles.
- Math and theory rounds that Google product teams generally do not have.
- Hiring committee process is research-heavy, even for engineering roles.
- Process is generally slower than Google product teams.
How DeepMind differs from OpenAI and Anthropic
- vs OpenAI: DeepMind’s research-track loop is more academic — paper discussion is deeper, math depth is expected. OpenAI’s loop is faster and more product-integrated.
- vs Anthropic: DeepMind’s interview is more conservative on AI tool use, more weighted toward unaided foundational reasoning. Anthropic explicitly grades AI-collaboration; DeepMind does not.
- vs FAIR (Meta AI Research): Comparable in research depth. FAIR has more publication culture; DeepMind has more product-integration than FAIR currently does.
Compensation
DeepMind compensation in 2026 is at the top end of the AI lab market for senior+ roles. London-based comp is a step below US comp but with London tax structure can be net-comparable. RSU grants in Alphabet (GOOG) and PhD-level base salaries make total comp competitive with OpenAI and Anthropic, especially at staff and principal levels.
How to prepare
- For Research Scientist: read 5-10 recent papers in your area deeply, practice articulating their methodology and weaknesses, drill ML math fundamentals.
- For Research Engineer: distributed training systems (Megatron, DeepSpeed, FSDP), evaluation harnesses, ML coding without AI tools.
- For Software Engineer: standard FAANG senior+ prep (LeetCode + system design + behavioral). Add awareness of ML serving stack.
- For Applied AI Engineer: mix of standard engineering + ML deployment context.
- Across all tracks: practice without AI tools. The DeepMind format does not generally permit them.
Frequently Asked Questions
Do I need a PhD for Research Scientist?
Effectively yes for the research scientist track at DeepMind. Research engineer roles are more flexible and accept strong engineers with ML experience even without a PhD.
Is the London office different from the US offices?
Yes — London is the original DeepMind office and has a research-heavy culture. US offices (Mountain View, NYC) are more product-integrated. The interview process is similar across offices but the default team mix differs.
How does DeepMind compare to Google Brain?
Google Brain merged into DeepMind in 2023. The combined organization is what hires now. Some legacy team distinctions remain internally but the external interview process is unified.
Is the hiring committee process slow?
Yes. Senior+ research scientist hires can take 8-12 weeks from offer to start. Engineering hires move faster but slower than typical FAANG.
Do they use Gemini in the interview?
Generally no. The interview is AI-prohibited or heavily limited. Some applied teams allow tool use; verify with your recruiter.