Software Engineer applying ML/GenAI research at Google DeepMind, 2 years of applied experience required

An entry-to-mid Software Engineer role at Google DeepMind requiring 2 years of experience developing ML models (TensorFlow, PyTorch, or JAX) and applying ML/statistics/diffusion model theory in applied research, alongside general software development in Java, C, C++, Python, or Go. The role spans prototyping GenAI features, building ML pipelines for generative media and multimodal understanding, and owning code quality, testing, and deployment lifecycle.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google's standard loop typically includes coding rounds, a googleyness/behavioral round, and for research-adjacent roles may include an ML/system design discussion

What this interview tests

Applied ML model development (TensorFlow/PyTorch/JAX)
GenAI pipeline building for generative media and multimodal tasks
Software engineering rigor: testing, code review, security
Root-cause debugging of complex system issues
Technical documentation and technical debt management

Common question themes

Describe an ML pipeline you built for a generative or multimodal task, from data to evaluation

Where has applied ML/statistics or diffusion model theory actually changed a technical decision you made

Tell me about a bug or system issue you debugged that required root-causing across hardware, network, or service layers

How do you approach code review and testing (integration, performance, security) on a project you own

How do you decide when to pay down technical debt versus ship the next feature

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Google Software Engineer interviews

All Google interviews