Back to deep dives

Jeff Dean on building useful AI systems

  • Agents
  • AI For Science
  • AI Engineering, Software, And Developer Tooling
  • AI Infrastructure, Compute, Chips, And Energy
Thumbnail for Jeff Dean on building useful AI systems
Image: Jeff Dean: The 1% Rule for Building in AI

Audio deep dive

Listen to this deep dive

IntroductionSection 01

Jeff Dean is one of the GOATs of modern computing: he helped Google scale, co-founded Google Brain, and is now Google’s Chief Scientist. At Y Combinator’s Startup School 2026, YC Managing Partner Diana Hu interviews him about agents working for weeks, the chips, memory, context and evaluation they need, and which assumptions and unsolved problems founders should chase.

Agents are handling longer tasks and may automate scientific experimentationSource0:24

I think the ability to do more and more complex tasks has been growing faster than I thought.

Agents may soon automate experiments across technical fields.

  • Coding agents broadly match his qualified junior-engineer prediction.
  • Improvements now extend beyond coding.
  • Automated loops can split problems, test solutions, and combine results.

Jeff Dean says specialized inference hardware could cut latency and energy useSource2:40

Imagine what you could do with something where the latency is 50X better.

Specialized inference chips could make agents faster and cheaper.

  • Hu compares the opportunity to Google’s faster in-memory search.
  • Low-energy inference should broaden access.
  • Specialized chips can beat general hardware on defined workloads.
  • Fifty-fold lower latency could enable new products.

Agents can work for days or weeks on some complicated tasksSource4:38

You can tell agents to go off and implement completely new versions of software in different programming languages that might have better safety properties or better performance properties.

Some capable agents now work for days or weeks.

  • Results depend on the model and problem domain.
  • Software can be rebuilt in another language.
  • Replacements can target better performance or safety.

A capacity calculation led Google to build the TPUSource5:58

That system produced a chip a couple years later that was 30 to 80 times more energy-efficient than CPUs and GPUs of the day.

Speech-recognition demand made CPUs unaffordable, prompting the TPU.

  • Better speech models halved errors but required much more computation.
  • The first TPU cut energy 30–80 times and latency 20–30 times.
  • Flexible linear algebra supported changing algorithms.
  • Dean urges founders to rethink bottlenecks from first principles.

Data movement and memory bandwidth dominate AI hardware designSource10:25

I think the example you raised of a thousand X difference in moving data versus actually computing on it in terms of energy is a pretty significant one.

Data movement can cost far more energy than calculation.

  • Designers must track memory, chip-link, and network bandwidth.
  • Batching saves energy but increases response time.
  • Inference chips can reduce movement and precision.

Understanding data well should make it compressibleSource15:33

If you truly understand the data, you should be able to compress it really well.

Compression depends on understanding what can be restored.

  • Lossy compression removes details that may need reconstruction.
  • Deeper understanding should improve compression.
  • Transformers have worked well so far.

Useful AI products depend on the whole system around the modelSource16:12

I think the model is really only one piece of what you’re trying to do, which is build an overall system that can solve really interesting problems.

Useful systems combine models, context, memory, tools, and evaluation.

  • Direct context can be clearer than training knowledge.
  • Complex work requires tool choice, sequencing, and evaluation.
  • Failures reveal which instructions or skills are missing.
  • Dean encoded code optimization into a benchmark-driven skill.
  • Performance Hints also improved models’ reasoning about slow code.

Skills and multi-agent evaluation make long-running agents more reliableSource22:14

One is give the model skills and hints that tend to keep it in the more brightly lit path of things it does know how to do.

Skills and competing attempts help agents outside familiar territory.

  • Performance can collapse outside training.
  • Guidance keeps agents near reliable operations.
  • Evaluators can select promising attempts and discard failures.
  • Google supplies internal agents with proprietary-tool skills.

Startups can win through specific problems, proprietary context, and clear objectivesSource25:19

So look for something where the model succeeds 0% or 1% of the time, not 20%.

Startups can compete where general models fail.

  • Dean favors useful problems with 0% or 1% model success.
  • Private data or specialist training can create advantages.
  • Founders must judge how long those advantages will last.
  • Specifications and tests make agent objectives concrete.

Problem selection and assumption-testing become scarce skills as agents handle more executionSource33:51

That high-level wisdom of what to work on is incredibly important.

People must still choose worthwhile goals and question assumptions carefully.

  • Strong tools add little to an unimportant problem.
  • Written predictions help test judgment.
  • Contrarian experiments sometimes expose better designs.
  • Dean’s unreliable-chip example replaces perfect parts with redundancy.

TPUs and MapReduce came from discarding accepted design assumptionsSource39:56

Being able to specialize hardware for a very niche problem domain before that problem domain seemed as important as it is today is one thought experiment.

TPUs and MapReduce emerged from reconsidering familiar designs.

  • Google specialized hardware before machine learning looked important.
  • MapReduce separated computation from parallelization and failure handling.
  • Its abstraction kept large jobs reliable across computer failures.

AI can accelerate fields with fast, reliable experimental evaluationSource42:08

So this is now a validation device, but instead of it taking a night, they made something that was 300,000 times faster and nearly as accurate as running the full-scale simulator.

Fast evaluators multiply possible experiments.

  • Orchestration can divide goals and recombine experimental results.
  • A learned chemistry simulator ran 300,000 times faster with similar accuracy.
  • Faster validation could accelerate science, engineering, and AI.

A rejected distillation paper still proved strategically importantSource47:45

We put it on arXiv, people read it, people use it. It’s all good.

A rejected model-distillation paper still became useful across industry.

  • A reviewer predicted little impact.
  • Operating large AI services made its value clearer.
  • Google now uses distillation for efficient Gemini Flash models.

Jeff Dean says career choices should combine meaningful impact with enjoyable, complementary teammatesSource50:01

If I work on this problem and the best possible outcome happens, will the world be a lot better in some way?

Meaningful work and enjoyable teammates guide his advice.

  • Established organizations offer structure, expertise, and reach.
  • Startups offer autonomy and reward with greater risk.
  • Strong teams combine complementary skills, low egos, and learning.
  • Teammates expand each person’s technical tool belt.

Open problems remain in AI hardware, learning, and human interactionSource55:07

I think there are radically different kinds of algorithms for machine learning that might be much more data efficient than the approaches we’re using today.

Open opportunities span hardware, learning, and human interaction.

  • Efficient inference hardware remains an open opportunity.
  • Current models consume far more data than humans.
  • Continual learning and multi-agent interaction remain promising.
  • Better tools could support civil conversation and human connections.

Tags

  • Agent Orchestration
  • AI Chips
  • Agent Tooling
  • Inference Infrastructure