Skip to content
Home » Lex Fridman Podcast: #494 w/ NVIDIA’s CEO Jensen Huang (Transcript)

Lex Fridman Podcast: #494 w/ NVIDIA’s CEO Jensen Huang (Transcript)

Editor’s Notes: In this episode of the Lex Fridman Podcast, Lex sits down with Jensen Huang, the visionary CEO of NVIDIA, to discuss the company’s pivotal role in the ongoing AI revolution. The conversation explores NVIDIA’s evolution from designing individual chips to engineering massive rack-scale systems and the “extreme co-design” required to power modern artificial intelligence. Jensen shares personal insights into his leadership philosophy, the importance of “manifesting” the future through engineering, and his optimistic outlook on how AI will solve humanity’s greatest challenges, from curing diseases to space exploration. (Mar 23, 2026) 

TRANSCRIPT:

Extreme Co-Design: Building the AI Factory

LEX FRIDMAN: The following is a conversation with Jensen Huang, CEO of Nvidia, one of the most important and influential companies in the history of human civilization. Nvidia is the engine powering the AI revolution. And a lot of its success can be directly attributed to Jensen’s sheer force of will and his many brilliant bets and decisions as a leader, engineer and innovator. This is the Lex Fridman podcast. And now, dear friends, here’s Jensen Huang.

You’ve propelled Nvidia into a new era in AI moving beyond its focus on chip scale design to now rack scale design. And I think it’s fair to say that winning for Nvidia for a long time used to be about building the best GPU possible. And you still do, but now you’ve expanded that to extreme co-design of GPU, CPU, memory, networking, storage, power, cooling, software, the rack itself, the POD that you’ve announced, and even the data center.

So let’s talk about extreme co-design. What is the hardest part of co-designing a system with that many complex components and design variables?

The Challenge of Distributed Computing at Scale

JENSEN HUANG: Yeah, thanks for that question. So first of all, the reason why extreme co-design is necessary is because the problem no longer fits inside one computer to be accelerated by one GPU. The problem that you’re trying to solve is you would like to go faster than the number of computers that you add. So you added 10,000 computers, but you would like it to go a million times faster.

Then all of a sudden you have to take the algorithm, you have to break up the algorithm, you have to refactor it, you have to shard the pipeline, you have to shard the data, you have to shard the model. Now all of a sudden, when you distribute the problem this way, not just scaling up the problem, but you’re distributing the problem, then everything gets in the way.

This is the Amdahl’s law problem, where the amount of speedup you have for something depends on how much of the total workload it is. And so if computation represents 50% of the problem, and I sped up computation infinitely like a million times, I only sped up the total workload by a factor of two.

Now all of a sudden, not only do you have to distribute the computation, you have to shard the pipeline somehow, you also have to solve the networking problem because you’ve got all of these computers connected together. And so distributed computing at the scale that we do, the CPU is a problem, the GPU is a problem, the networking is a problem, the switching is a problem, and distributing the workload across all these computers are a problem. It’s just a massively complex computer science problem. And so we just got to bring every technology to bear. Otherwise we scale up linearly or we scale up based on the capabilities of Moore’s Law, which has largely slowed because Dennard’s scaling has slowed.

Bringing Specialists Together: The Architecture of Nvidia

LEX FRIDMAN: I’m sure there’s trade-offs there. Plus you have completely disparate disciplines here. I’m sure you have specialists in each one of these — high bandwidth memory, the networking, the NVLink, the NICs, the optics and the copper that you’re doing, the power delivery, the cooling, all that. I mean, there’s world experts in each of those. How do you get them in a room together to figure out —

JENSEN HUANG: That’s why my staff is so large.

LEX FRIDMAN: Can you take me through the process of the specialists and the generalists? How do you put together the rack when you know the set of things you have to shove into a rack together? What does that process look like of designing it all together?

JENSEN HUANG: There’s the first question, which is what is extreme co-design — you were optimizing across the entire stack of software from architectures to chips to systems to system software, to the algorithms to the applications. That’s one layer. The second thing that you and I just talked about goes beyond CPUs and GPUs and networking chips and scale-up switches and scale-out switches. And then of course you got to include power and cooling and all of that because all these computers are extremely power hungry. They do a lot of work and they’re very energy efficient, but they in aggregate still consume a lot of power.

So that’s one. The first question is what is it? The second question is why is it? And we just spoke about the reason. You want to distribute the workload so that you can exceed the benefit of just increasing the number of computers. And then the third question is, how is it? How do you do it? And that’s kind of the miracle of this company.

When you’re designing a computer, you have to have an operating system of computers. When you’re designing a company, you should first think about what is it that you want the company to produce. I see a lot of companies’ organization charts and they all look the same. Hamburger organization charts, software organization charts and car company organization charts, they all look the same. And it doesn’t make any sense to me. The goal of a company is to be the machinery, the mechanism, the system that produces the output.