Google Reshuffles DeepMind; Gemini 3.5 Pro Misses July
Key takeaways:
- Hassabis moves to Chairman of GDM + Chief Scientist of Alphabet; his focus shifts to AGI strategy and Isomorphic Labs (AI drug discovery)
- Kavukcuoglu now owns Gemini model delivery, Frontier AI research, and the Gemini app — 13 years at DeepMind, led WaveNet and DQN
- Jeff Dean (27-year Google veteran), Sanjay Ghemawat, Oriol Vinyals, and Quoc Le are co-founding Discovery Loop; Alphabet is a founding investor and Cloud partner
- Gemini 3.5 Pro missed June, then July — no revised launch date has been announced
- Gemini Flash is in high demand; Google has not announced product or service changes to current Flash workloads; Gemini 4 is in active development as of August 5, 2026
Google shuffled its most senior AI leadership on August 5, 2026. In a note to Google DeepMind staff, Sundar Pichai announced that Demis Hassabis — who co-founded DeepMind and built it into Google’s AI engine room — is stepping back from CEO to become Chairman of GDM and Chief Scientist of Alphabet. Koray Kavukcuoglu, GDM’s CTO for 13 years, steps up as SVP and will run day-to-day model delivery. Separately, Jeff Dean, Google’s Chief Scientist and a 27-year veteran, is departing to co-found Discovery Loop alongside Sanjay Ghemawat, Oriol Vinyals, and Quoc Le. Alphabet shares fell approximately 4–5% following the announcement. The backdrop: Gemini 3.5 Pro remains unshipped, months past its original June target.
What Happened at Google DeepMind on August 5?
Per Pichai’s post, the changes are framed as separating two priorities: AGI/science strategy (Hassabis) and accelerating model delivery (Kavukcuoglu).
Hassabis wrote to staff that he believes “AGI is close at hand” and that he needs “time and space to focus on the big picture.” He will continue as Chairman of GDM and will spend more time at Isomorphic Labs, Alphabet’s AI drug-discovery subsidiary. The leadership of Isomorphic is one of his stated priorities.
Kavukcuoglu becomes SVP of Google DeepMind, reporting directly to Pichai. He started GDM’s deep learning team, led work on WaveNet and DQN, and is currently overseeing development of Gemini 4. In Pichai’s note, Kavukcuoglu is framed as the operational owner of Gemini going forward — the person accountable for delivery.
Dean and Ghemawat are co-founding Discovery Loop — a public benefit corporation focused on automating machine learning and science research — with Vinyals and Le. Alphabet is a founding investor and will supply Cloud compute. Dean announced Discovery Loop on X and told the New York Times (via SiliconAngle) that operating outside a public company allows decisions unconstrained by immediate financial interests.
Does This Change the Enterprise Calculus for Google AI?
We wrote in June that if Gemini 3.5 Pro missed July, “that’s a materially different signal.” It did miss July. The model remains unshipped, with no revised date from Google.
The positive case for Google AI customers is real: Kavukcuoglu is an internal promotion with deep institutional knowledge, not an outside hire parachuted in. Pichai’s note cited 950 million monthly Gemini app users and 900 million Gemma model downloads, with strong Flash demand. Vertex AI enterprise agent infrastructure remains intact. As of August 5, 2026, Gemini 4 is in active development under Kavukcuoglu. None of that goes away because Hassabis moved upstairs.
The risk side: this is the latest wave of senior departures from the group that built the current Gemini generation. Noam Shazeer (returned via the Character.AI acqui-hire to work on Gemini) moved to OpenAI. Nobel laureate John Jumper moved to Anthropic. Now four more senior researchers are forming their own lab. The question for procurement teams is not “is Google’s AI capability finished?” — it is not — but “how confident am I that Gemini 3.5 Pro will ship on a schedule I can plan around?”
What to do now:
- If your roadmap depends on Gemini 3.5 Pro capabilities: do not plan around an assumed delivery window — Google has announced no revised date. Ask your Google account team for a written commitment in your contract. Kavukcuoglu is Google’s announced operational owner of Gemini delivery, but an org-structure change is not a contractual guarantee.
- If you’re running Vertex AI or Google Workspace AI workloads on Flash: no action required. Google has not announced any product or service change to current Flash workloads.
- If you’re in active contract negotiation or renewal for Google Cloud AI: use this moment to ask for roadmap commitments in writing — specifically Gemini 3.5 Pro delivery date and Gemini 4 preview access terms.
- Watch Gemini 4 framing: if Google positions 4 as the successor to 3.5 Pro rather than an incremental step, the 3.5 Pro delay becomes a moot architectural decision rather than a delivery failure. Watch for an official Gemini 4 preview, release date, model card, or SKU/roadmap clarification — those are the actionable signals.
FAQ
Why did Demis Hassabis step back from running Google DeepMind?
Per his August 5 note to GDM staff, Hassabis decided this is the right moment to focus on AGI strategy rather than day-to-day operations. He wrote that he believes AGI “is close at hand” and that getting the next steps right “is critical for humanity.” He becomes Chairman of GDM and Chief Scientist of Alphabet, and plans to lean into Isomorphic Labs, Alphabet’s AI drug-discovery unit.
Who now owns Gemini model development?
Koray Kavukcuoglu, the new SVP of Google DeepMind, reporting directly to Sundar Pichai. He has been at DeepMind since its early days — 13 years — started its deep learning team, and led work on WaveNet and DQN. He is currently overseeing Gemini 4 development. In Pichai’s announcement, he is explicitly named as the owner of Gemini model delivery, Frontier AI research, and the Gemini app going forward.
Should enterprise teams reconsider their Google Vertex AI or Gemini commitments?
Not based on leadership changes alone — Kavukcuoglu has 13 years of institutional continuity and Google has not announced product or service changes to current Flash workloads. The more concrete reason for scrutiny is the Gemini 3.5 Pro delay: missed June, missed July, no revised date. If your H2 roadmap has dependencies on 3.5 Pro-specific capabilities, re-baseline timelines and request written delivery commitments from your Google account team rather than relying on general product announcements.