AI Pulse

Google's AI Founders Are Leaving to Automate Science Itself. DeepMind Has a New Boss. The August 7 Pulse.

By Felix Maru · August 7, 2026 · 7 min read

Two announcements landed on August 5 from inside the same company, and the combination is worth sitting with. The person who co-founded and led Google DeepMind for over a decade stepped back from running it. And four of the most consequential researchers in modern AI, people who spent between 13 and 27 years at Google building the foundations that nearly every AI system today depends on, announced they are leaving to start something new. The question worth asking is not who left, but what they are going to do next, and what that says about where AI development is actually heading.

The Hassabis Handover: What Changed at DeepMind

Demis Hassabis stepped down as CEO of Google DeepMind on August 5. He moves to Chairman of Google DeepMind and takes the title of Alphabet Chief Scientist, a role that gives him a mandate to focus on the long-horizon AGI question. He also continues running Isomorphic Labs, Google's pharmaceutical research spinoff, where AI-designed proteins and drug candidates are an active commercial program.

Koray Kavukcuoglu takes over day-to-day operations as SVP, reporting directly to Sundar Pichai. Thirteen years at DeepMind. He built the deep learning team there and drove the research behind WaveNet, the voice synthesis architecture that eventually powered Google Assistant, and DQN, the reinforcement learning agent that beat Atari games. His mandate now covers Gemini model development, frontier AI research, and the Gemini app and developer teams, all as a single reporting line.

That consolidation is worth noting. Previously the distance between DeepMind's research culture and Google's product organization was structural. Research reported one way, product reported another. Bloomberg reported that the reshuffle is explicitly designed to shorten the path from frontier research to shipping products. With Kavukcuoglu owning models, research, and the app in one mandate and reporting to Pichai, the organizational distance has collapsed. Google is signaling it wants AI product velocity, not just AI prestige.

Jeff Dean, Sanjay Ghemawat, and the People Who Built the Infrastructure of Modern AI

The same day, TechCrunch reported that four people are leaving Google to co-found Discovery Loop.

Jeff Dean spent 27 years at Google. He co-designed TensorFlow, helped create the TPU program, and was a co-founder of Google Brain. His collaboration with Sanjay Ghemawat produced MapReduce and BigTable, the papers that became the foundational layer of how distributed computing works across the entire industry. The data pipelines, the model training infrastructure, the serving systems: much of what makes large-scale AI possible traces back to work Dean and Ghemawat did at Google.

Oriol Vinyals was VP of Research at Google DeepMind and a technical lead on Gemini. Quoc Le co-founded Google Brain and created AutoML-Zero. These are not peripheral names. They are the people who built the scaffolding the AI industry runs on.

Google confirmed it will participate as a founding investor in Discovery Loop and serve as a Cloud partner. The company is backing the departure rather than treating it as a loss.

Discovery Loop: Automating the Scientific Method Itself

What is Discovery Loop actually trying to do? Their stated mission, as reported by Yahoo Finance and covered by GeekWire, is to automate the full experimental loop of the scientific method at a scale sequential human effort cannot match. Not "use AI to help scientists do research faster." Build systems that propose an experiment, implement it, run it, evaluate the results, and iterate, in thousands of parallel loops simultaneously.

The initial focus is ML research itself: using automated experimental loops to accelerate the development of AI systems. From there, the plan expands into chip design, biology, drug discovery, and materials science. Discovery Loop is structured as a public benefit corporation, backed by Radical Ventures and Khosla Ventures.

The reason this is worth paying close attention to: if it works, even partially, the pace at which AI capabilities improve will compound differently than any lab's current roadmap predicts. ML research that currently takes months of human-guided experimentation could become something that runs in parallel over days. The people doing this are not researchers with an interesting idea. They are the people who built the infrastructure that made large-scale ML possible in the first place.

What This Means for People Building on Google's AI Today

Two time horizons, and it is worth being clear about both.

In the near term: nothing changes for teams building on Gemini or Google's AI APIs. Kavukcuoglu is not an unknown quantity parachuted in from outside. He has been inside DeepMind for 13 years and drove real technical breakthroughs. The restructuring is designed to ship more, not less. If anything, the product-focused mandate means Gemini development may accelerate.

The longer-term read is more interesting. When the people who built Google's AI foundations leave to automate the scientific discovery process itself, they are making a bet that the next major capability jump will not come from incremental scaling of existing approaches. It will come from systems that can run the experimental loop autonomously, at volume. That is a different kind of progress than the current "train a bigger model, release it, repeat" cycle.

For anyone working in IT operations, support automation, or AI tooling: the practical implication is not "do something different right now." It is "do not plan your tool stack as if the current capability ceiling is permanent." The workflows being built today on models like Gemini, GPT-5, and Claude are being built on infrastructure that will look meaningfully different in two to three years, possibly faster if automated research loops start producing results.

The Practitioner Read: Build for Portability

There is a specific habit worth developing in light of this kind of structural shift at the top of AI.

Build your automation workflows with a clear separation between the logic and the model underneath it. If your ticket classification, intent detection, or response drafting is hardwired to one vendor's API syntax, model version, and response format, every shift like this one becomes a potential maintenance problem. The abstraction layer between your workflow and the specific AI call costs a little more to build upfront and saves real time every time the underlying model changes.

This is not an argument against using any specific vendor. Gemini, GPT-5, and Claude all do genuinely useful things, and the right tool still depends on the specific task and the data privacy requirements around it. But the teams I have seen handle model transitions well are the ones who treated the AI call as a swappable component from the start, not the ones who assumed a particular model's behavior was permanent.

The people who built the foundations of modern AI just left to automate the process of building the next set of foundations. That is worth understanding clearly, not as a reason for alarm, but as useful signal about the pace of what is coming.

Sources

Working through how shifts like this affect your AI tool choices? Reach out here.