Lila Ibrahim

Chief AI Readiness Officer — Google DeepMind Chief Operating Officer (former) — Google DeepMind Chief Operating Officer — Coursera

Listen — profile

0:00 / 2:23

Profile

Lila Ibrahim is the Chief AI Readiness Officer at Google DeepMind, and was its first-ever COO — the operator who spent eight years building the organizational machinery behind one of the world’s top AI labs. If Demis Hassabis is the scientist-CEO who sets the research agenda, Ibrahim is the person who figured out how to scale a 200-person research outfit into the thousands-strong lab that ships Gemini, AlphaFold, and most of Google’s frontier AI work.

Her path is unusual for a big-AI executive. She earned an electrical engineering degree from Purdue in 1993 and spent the next 18 years at Intel — starting as a design engineer on the Pentium, eventually serving as Chief of Staff to CEO Craig Barrett. She moved to Kleiner Perkins as Chief of Staff, then became founding president and COO of Coursera from 2013 to 2018, helping turn Andrew Ng and Daphne Koller’s Stanford experiment into a publicly-traded education platform. She also co-founded Team4Tech, a non-profit that deploys tech talent to under-resourced schools.

She joined DeepMind in 2018 and famously took 50 hours of interviews before accepting — she wanted to understand what she was signing up for. Her answer: “I felt there was no better place to build AI responsibly than DeepMind.” She owns the unglamorous but load-bearing functions — operations, governance, policy, people, communications — and in 2023 signed the Center for AI Safety statement putting extinction risk alongside pandemics and nuclear war. In 2026 she transitioned to Chief AI Readiness Officer, leading the Frontier AI Global Affairs team and DeepMind’s work on preparing the world for more capable systems.

For developers, Ibrahim is a reminder that frontier AI isn’t just a research problem. The reason Gemini ships on a predictable cadence, the reason DeepMind can absorb Google Brain without imploding, the reason policy teams actually get listened to internally — that’s COO work. The boring parts determine whether the interesting parts reach you.