By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
The Pragmatic EngineerSoftware engineering after code becomes cheap with Satya Nadella
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
Great conversations run long. Their best ideas don't have to.
uListen is free on iPhone, iPad, Android, Chrome, and Claude.
See howTranscript
65 min read · 12,876 wordsIntro
Satya Nadella 0:00 In a world where code generation has become cheap, what has become hard is verification. In fact, I kind of feel like I gotta learn because I've not worked in a team that is mostly now code as output. But the code as output has a particular order of operations. It's not like code as output means everybody's just generating all sorts of random code.
Gergely Orosz 0:18 Out of nowhere, 2025 Claude Code. For the first time, I felt that you didn't have an immediate response.
Satya Nadella 0:24 When model jumps happen non-linearly, the form factor has to change. AI first product building in that sense is unforgiving. In six months or so, IDEs kind of faded away.
Gergely Orosz 0:35 I'm asking myself, are there parallels to the open source movement and now the open model?
Satya Nadella 0:40 If you just get past this thing called there's gonna be one frontier model to have all of the world's knowledge, right? If you don't buy that, then you have to assume that there should be, in some sense, as many frontier models as firms in the world, right? Because after all...
Gergely Orosz 0:59 What does software engineering mean after code generation becomes very cheap? Today's guest is Satya Nadella, Microsoft’s CEO, one of the few Big Tech CEOs who started his career as a software engineer. Today, we cover what the term software factory means for Satya and how it looks like today inside of Microsoft. Open width models, local models, and the idea of unmetered intelligence. The very real anxiety for us devs around AI, Microsoft voluntary exit offers, and why the junior hiring slowdown might only be temporary, and many more. If you want to understand what Satya thinks it will take to become a standout software dev in this age of AI and want to understand his thoughtful mental models on how to make sense of all this change, this episode is for you. This episode is presented by Turbopuffer, a ridiculously scalable, fast, and cheap hybrid search engine built on top of object storage used by cutting-edge companies like Anthropic, Linear Ramp, and many others. Many companies who switch to Turbopuffer are cutting their search bills by 50% or more and getting much faster results. Check it out at turbopuffer.com/pragmatic. Satya, welcome to the podcast.
Satya Nadella 1:59 Thank you so much for having me, Gergely.
Gergely Orosz 2:01 Well, it's great to be here because I'm not sure if you know, but I was a Microsofty.
Satya Nadella 2:05 Were you here or where were you?
Gergely Orosz 2:06 I, I was in London, and this is the first time I'm here in headquarter, so you know, like-
Satya Nadella 2:11 Welcome. [laughs]
Microsoft’s open-source shift
Gergely Orosz 2:12 12, 12 years back. But I want to re- re- rewind back there. I was actually at Microsoft when you became CEO in 2014, and I remember, distinctly remember how Microsoft was still very much embracing closed source, and when you came on, you started to embrace open source. There was Visual Studio Code that was released. Microsoft acquired GitHub and went all on Git before we used TFS. TypeScript was released as open source, and I just wanted to rewind back. Why did you... People were surprised. My, my friends outside of Microsoft were surprised. Even I was surprised. Why did Microsoft go all in on open source?
Satya Nadella 2:47 Yeah, I mean, at some level, sometimes these narratives and perceptions get shaped, and it takes a lot to change and what have you. Because i- if you looked at even, I would say, commits even into Linux, even pre me becoming CEO, I think Microsoft had significant, uh, contributions and were committed to it. But the thing that I think we really made sure the... we understood internally and the world understood is Microsoft is committed to o- open source, right? Whether it is, uh, bringing some of our workloads to Linux, like SQL Server, uh, or contributing to Linux or, or open sourcing projects like TypeScript and others.
Gergely Orosz 3:27 Yeah.
Satya Nadella 3:27 I think we're all part... And, you know, obviously our, uh, uh, you know, us as stewards of GitHub, uh, put us at the center of it, and we just wanted to make sure that we were able to earn the trust, uh, of the open source community by doing right by the community. In fact, it's fascinating. I've always thought about this, which is when you look at companies that have used open source and people who have contributed to open source, if there was a true accounting of it at some point, I think Microsoft would be at the top or if not in, you know, amongst the top, right? In fact, if you look at some, quote-unquote, "a lot of these other companies" that have benefited the most from open source have hardly contributed, and it's never... And that is, I think, how, you know... And like, hey, you can't complain, but that's how the world rolls, which is it's on narratives versus facts all
Building VS Code in the open
Satya Nadella 4:15 the time.
Gergely Orosz 4:15 Well, it's, it's narratives versus facts, that's true, and, and again, I think there's that Windows legacy from the '90s that shifts people's, uh, you know, like how they think about it. But what I remember made the biggest impact across the developer community was not really open source. It was Visual Studio Code.
Satya Nadella 4:31 Yeah.
Gergely Orosz 4:32 It was open source, sure, but it was also free, and I was a developer before I used Visual Studio, and it was so good. Visual Studio is still amazing piece of software. And somehow you decided Microsoft to bring Visual Studio for free in an open source version to the broader dev community, and boom, 10 or five years later, it's everywhere. Everyone was using it. Was that intentional?
Satya Nadella 4:56 Yeah. In fact, uh, you know that, you know, Eric Gama and others who were at that time in that place really was a- absolutely, it was an intentional, even building with community. In fact, uh, you know, when I look at even product making, uh, it was the first time I also got exposed to what I think now people talk about, you know, building in the open. That was-
Gergely Orosz 5:14 Yeah
Satya Nadella 5:14 ... really the first time we all learned what building in the open means, having the community around it, and just that feedback cycle. I remember even spending time at that time with Amanda Silver and others, learning how that team, even the product manager, what does it mean to be a PM, uh, on that team? How they every day looked at the community feedback as a way to build versus, you know, top... You know, like it's not like a, you know, I listen to my vi- vice president. I listen to my community. So there were many, many cultural aspects of building in the open, uh, beyond open source that I think were fundamentally transformative. In fact, I would say sometimes I sort of feel like we learnt a lot of great lessons there. We should have learnt it even more deeply and more broadly.
Copilot, Cursor, and Claude Code
Gergely Orosz 5:55 Speaking of, of learning more, more deeply or more broadly Visual Studio Code was everywhere. GitHub was doing great. And then with Copilot, I, I mean, I was so surprised, even looking back, how Microsoft was so early to realizing that AI before ChatGPT 3.5, this was, I think, the 3.0 version or, or, or so Copilot was working like magic and there was no real competition for at least a year until 2023 when Cursor came out. And then Cursor came out and I still felt that you guys were super smart about VS Code because Cursor was based on VS Code, familiar interface and, you know, GitHub Copilot and Cursor were going... Has side by side competing with one another, keeping up with one another and then out of nowhere, 2025 Claude Code. And for myself, for people working at startups, even big tech companies, in six months everyone just forgot about the IDE. And I am still so surprised that Microsoft, you guys live and breathe developer DNA is in your, your, your DNA and it's always been. How do you think you missed that this sudden shift would, would come and it-- for the first time I felt that you didn't have an immediate response?
Satya Nadella 7:03 Yeah. No, it's a g- it's a great, uh, thing to unpack, right? I think you-- to your point, being early to it, uh, when we... You know, this was pre-GPT 4, right?
Gergely Orosz 7:12 It was.
Satya Nadella 7:13 So when we even started there, um, and even just the code completions were magical. That was sort of really what-
Gergely Orosz 7:20 It was magical
Satya Nadella 7:21 ... GitHub Copilot... Uh, you know, if you remember, we worked on IntelliSense forever and we made good progress and then we said, "Wow, this thing is working." And quite frankly, there was a lot of skepticism that it would ever work. But it started and that was my... Even my own belief in scaling laws, quite frankly, was, uh, fundamentally, uh, reaffirmed, let's say, when I started seeing that. And I thought we did a good job of trying to build that product. One of the keys of building with, uh, models is when model jumps happen non-linearly, the form factor has to change quickly, right? That's the... You know, what is... AI first product building in that sense is unforgiving because when you-- you have to be-- basically build everything around a given model and then be ready for the next model to have some emergent capabilities and rewire yourself for that, right? Don't be in love with what you built. So that's why even when agentic coding or task handling started becoming something that one could do, right? It's not just code completions, but you could assign, uh, small tasks. That's where Cursor really... You know, they took the IDE, they forked, but they did a good job on really, uh, the agent mode.
Gergely Orosz 8:27 Yeah.
Satya Nadella 8:27 And so we then caught up on the agent mode, uh, because that was sort of something that we could do on top of even the OpenAI models. But then the thing that hit us was obviously a great work that Anthropic did, uh, with their model, uh, which then truly made the CLI as a form factor. Uh, and then you could even just say just complete full, uh, handling of, you know, code be- went from input to output effectively, right? I mean, that I think was the transformation in six months or so.
Gergely Orosz 8:56 Yeah.
Satya Nadella 8:57 Uh, we went primarily that to your point about, uh, IDEs, uh, IDEs kind of faded away and then you really had this new way of thinking about code as input. And that's why if I look at, uh, the new IDE, it's more about how do I really input the specs and the markdowns and everything else around the software factory. And so that transformation changes. Interestingly enough, it, it's funny that we're talking about it. Like one of the things, thoughts I have is with these decision engine models. Finally, I'm back again to IDEs because in an interesting way it's kind of like functions, right? It's intelligent functions that are embedded inside software. So I think that there could be a rebirth even of an IDE, um, as we think about even embedding intelligence in a more token efficient way. So I don't say, uh, it's a permanent shift all in one way. It's about having multiple form factors now that actually help you with model capability.
Decision engines
Gergely Orosz 9:52 I do want to ask you here, you mentioned decision models and how you're excited about them. Both of us recently talked with Diogo in, in-
Satya Nadella 10:00 Yeah
Gergely Orosz 10:00 ... different, different forums. How has your thinking changed on both decision models, but also on the limits of LLM specifically for, for programmatic tasks, for, for coding, for, for building software in a reliable way?
Satya Nadella 10:11 Yeah, I think that that's kind of it, right? Which is look, I, I think the LLMs are fantastic and we can talk about like even how, you know-
Gergely Orosz 10:19 We're, we're, we're engineers. Let's cut to the point where they're not fantastic, right?
Satya Nadella 10:22 Yes. Right. Uh, in the sense of how do you even think about, uh, the software factory and there's an entire thing that we can go into. But the-- uh, what I love about decision engines is it's kind of a new primitive, right? And how Diego talks about it and how our own decision engine and Achint and others are talking about it. And I like that because, you know, it's kind of like, you know, Excel macros. Uh, you know, what happened to spreadsheets with macros can happen with code with intelligence embedded as a primitive, right? And so, I don't know, you build any system like I think I was looking at an Xbox system that they'd built for managing all of the com- community feedback, right? It's a classic community feedback comes, I make a set of decisions based on it. I don't want to really generate LLM code on it. I just want to be able to make decisions. So it's better to embed this primitive, right? It has a distribution. You can make a call. It's sort of a, uh, it doesn't need to be generated again and again. It's token efficient.
Gergely Orosz 11:21 Yeah.
Satya Nadella 11:21 Uh, and so I think that this is one of those places where software engineering remains very much alive. It's changing. One of the things I like about Diego's thing is he wants to make it as boring as databases. In fact, to me, a relational database... I grew up with my, my, my-- like the most favorite product, uh, in the developer chain other than the compilers and the lex and yak and what have you, was the database. Because the relational database is a reliable way to be able to store, query, uh, your information. Just made all kinds of applications possible. And I think decision engines in the era of intelligence will also do the same.
Gergely Orosz 11:59 Well, in fact, the databases are the hardest. So we, we talk about what is the essence of a software company? It's the business logic, right? But when you go deeper, it's often in the database. In fact, so much of the business logic used to be coded in stored transactions, some of these things. So I wonder if-
Satya Nadella 12:15 Yeah, it's a good one. It's like it's a... Like this is the stored procedure of the intelligence era.
Gergely Orosz 12:20 Yeah. So, so I wonder if there's an analogy or a hope, because I do see that we haven't found the right primitive. Like, we know that LLMs can generate code. We can use LLMs to do unreliable stuff, but we still, we're missing these kind of primitives,
Verifying AI-generated code
Gergely Orosz 12:32 right?
Satya Nadella 12:32 Yeah, yeah. So I'm very excited about it, and this is, I think, the beginning of how... You know, because one of the other challenges, you know... So let's go to the software factory for a second, right? If you look at even how Cowork is built or even the GitHub Copilot runtime is built today, and, you know, I think people have blogged about it, and it's fascinating, right? You know, in a world where code generation has become cheap, what has become hard is verification, right? Uh, and in fact, one of the things that I feel like, oh my God, I wish, you know, I want to join one of these Mark Russinovich, Scott Hanselman, you know, perceptorships or whatever they call. Because I kind of feel like I got to learn, because I've not worked in a team that is mostly now code as output, right? But the code as output has a particular order of operations. It's not like code as output means everybody's just generating all sorts of random code. Like, the way you got to build the verification stuff, how do you take every failure and then build back the test case and make sure you truly verify the test, right? I mean, there's just so much, I would say, new type of tribal knowledge people are building up in managing complex software projects. In fact, it's a nightmare. I think even in that Rust migration they were having, they had to revert back. Um, and so that is sort of all the code, the great advantages and some massive disadvantages. So that's why, to your point, having additional primitives like this, uh, decision engine, I think are good.
Gergely Orosz 13:55 And you mentioned that as a, as a CEO of, of like this amazing company, you see all of the things happening, right? You oversee, you get information. You would want to go and work on a team if you could.
Satya Nadella 14:06 Oh, uh, absolutely. In fact, you know, my dream next job would be that, right? If I could go back and just be part... In fact, in fact, one of the things that's interesting, you know, I was gonna send mail to Scott and Mark and say, "Hey, they're doing an unbelievable job of creating this new program inside of Microsoft, uh, called perceptorship." I think they even have a relationship with Carnegie Mellon or something. And that idea that you can have people who can come in even early in career, because I care a lot about, hey, can you have an early in career person come in, join one of these teams, go up the learning curve? Because I think the learning curve, I remember people used to come to Microsoft for an internship. They would go see, hey, how is, you know, Cutler's code? Uh, how do I go look at the malloc implementation? [laughs] So what's the new form of that is what I think we have to really discover. And so yes, if we... You know, my hope would be one day I get to do that again.
Gergely Orosz 14:59 I'm now understanding why so many CTOs, uh, VP of engineering, SVPs do take step downs to work on small teams to learn how to build with, with these new tools right now.
Satya Nadella 15:11 Yeah.
Gergely Orosz 15:11 It seems all of it's changing.
Satya Nadella 15:12 I absolutely. I think, yeah, it's the organizational sort of context of it all, uh, is changing that I think, yeah, if I, um, if I think about it, I think it's very important. In fact, you know, being a lot more hands-on at a time of great change on many fronts, right? By the way, being close to customers, building in the open. There's so much to learn on all aspects of what makes successful products or successful technology, uh, that, yeah, there's plenty of opportunity.
The software factory
Gergely Orosz 15:39 We've now been throwing around the, the term software factory for a little bit, so, so let's, let's actually talk about it. I feel this term is a bit vague-
Satya Nadella 15:46 Yeah
Gergely Orosz 15:46 ... but it's coming around. What does it mean for you?
Satya Nadella 15:48 Yeah. So I'm also still kind of coming to grips with it. So I'm pattern matching, um, in what is teams of people in a software team today do, right? So, you know, I think I'd point your viewers to, uh, the, the blog that Bas wrote. I mean, in fact, there are two nice blogs, right? The Cowork team and the GitHub Copilot, uh, team, both of them have these blogs out. One is what one what... uh, one individual developer-
Gergely Orosz 16:15 Yep
Satya Nadella 16:15 ... was able to do. That was on the GitHub side, which was maintain an entire runtime, um, and re- you know, I think they also mi-migrated, I forget whether it's from Python, I guess, to Rust. Um-
Gergely Orosz 16:26 It's always to Rust. [laughs]
Satya Nadella 16:27 To Rust. [laughs] Uh, but nevertheless, they kind of... That's a beautiful case study of what the productivity of a single developer and what does it mean to do that maintenance and so on. Then there is the team, I think it's nine or 12 or whatever number of engineers. It's kind of crazy that that's the total size of that team, um, and the software factory, and they've also done a nice blog. But there's so many things there I love. I mean, I... This is where, you know, uh, if, if I could just go join that team and really learn it firsthand versus just reading blogs or talking to Bas and team. But for example, the fundamental ch- transformation as I understand it is, right, one is code is gone from being input to output. Great. Then you kind of have to say, okay, that means specification and intent, right? Which was always important. Design docs were important, and so-
Gergely Orosz 17:15 Alignment, yeah
Satya Nadella 17:16 ... but align. And so that, that's kind of, yeah, very important now.
Gergely Orosz 17:20 Yeah.
Satya Nadella 17:20 The other fascinating thing I'm also finding is, and I talked to one y- uh, sort of early in career, uh, person who went in, getting into a code base now is actually much easier because the reason when you're managing a software factory, everything is documented.
Gergely Orosz 17:37 Yeah.
Satya Nadella 17:37 Um, and so to... And then you can, you can ask it questions. So you-
Gergely Orosz 17:40 You have this patient mentor onboarding buddy.
Satya Nadella 17:42 Exactly. And so you can have... Y- your, your onboarding onto a code base is so much more easier than you scrounging around for tribal knowledge that's in people's heads, if you will, right? So the other thing is I'm learning a lot about this verification stuff, right? Which is m- Yeah. The way you want to do agentic coding is, like, these little tasks that you give it, make sure that it's truly done. How do you have the critique, right? There's so much to be said about having a separate model family. In fact, that's the other thing that I, I w- I've always worried about is, like, hey, if there's one model family and this model families are all gonna have all these alignment issues, how do you use a critique to ensure that one model family's challenge doesn't become, uh, your challenge? And so anyway, I, I kinda look at, say, there's an entire new way to build, uh, that is emerging, and it's new software engineering, and it requires software engineers. It's just a level of indirection. Maybe that's why I like the even the analogy of, you know, when, you know, uh, you went from writing your own assembly to saying, "Oh, wow, I have a compiler." Um, and suddenly you felt like, "Oh, wow, I can now go from intent to code, and I don't need to know assembly." There's a little bit of that. It's a level of abstraction. But even how you work in a team has changed and how you construct a product has changed. The other one that I'm really excited about is, um, the, the traces from production coming back.
Gergely Orosz 19:05 Yes.
Satya Nadella 19:05 I love that, too, right? Which is, you know-
Gergely Orosz 19:08 We're talking the observability, but now-
Satya Nadella 19:09 Yeah, it's kind of observable
Gergely Orosz 19:09 ... you have more, more opportunities or more capabilities.
Satya Nadella 19:11 Yeah, I mean, when people say, like, you know, RSI, that's kind of my RSI, right? [laughs] Which is it's sort of the ability to take my production logs and then to be able to verify the fix. In fact, that verifiability loop is great that you can then deploy the fix and deploy it all the way through that it actually passed all the tests. Uh, that actually is very helpful. And so I think there's a lot of learning, uh, that these co- teams are having, and it's spreading across Microsoft. I mean, uh, it's just good to see how this is now becoming the way teams are structuring. The other one that I love, um, is our networking, Azure networking team, right? It's... In fact, my... Th- uh, this used to be my favorite story where this team said, "Hey, we are... You know, our, our Microsoft manages something like 500 fiber operators all over the world for our global network." And, you know, always it's a physical asset, something or the other goes wrong. You know, the fancy word for managing all that is DevOps. But the-
Gergely Orosz 20:09 Yeah
Satya Nadella 20:09 ... reality is it's emails and, you know, all sorts of ad hoc processes. And so they went and built this entire agentic system that actually does the ops, and that ops is connected even, uh, to their repos. And so now it's not just the repo on its own or the code base, but it's even the operations that are around it. And so you can start seeing how the nature of what technical teams do is build these factories of ops plus, uh, software that do the job versus doing the job. But still, they're doing a job which is slightly different.
Bringing AI to existing products
Gergely Orosz 20:45 I, I do wonder because, uh, in AI labs, uh, it's, it's pretty common and, and they're very open about sharing how software engineers there, their job is becoming to allow the agent and the loop to do a better job, so, so what you just said. But just sticking to practical level, like at a place like Microsoft, you're... you will have teams that can experiment, and they're building new factories, or, or there are platform teams and maybe they have extra cycles and they're doing all these things. But you also have product teams who actually have a product. You have real customers, and this is where I see a lot of companies struggle with who do have a real business, and they're seeing these aspirational things from AI labs or maybe even they're listening to you right now, and they're thinking, "Hang on, like, I can't just drop everything and build a factory, 'cause what am I gonna do with, with the thing?" How, how are you thinking about both this balance and especially inside of Microsoft? What, what do you tell engineers? Like, how is your job changing, especially when you're working a product that is a good product, it's a profitable product, customers depend on it?
Satya Nadella 21:39 Yeah. It's a great point. I mean, like, first of all, you know, we don't get permission to do things that are not adding value to customers. Like, let's start there. To your point about a little bit of... And, and we made our share of mistakes of, you know, going and doing random AI things just because they were, you know, you know, cool to do. You kind of ultimately are going to-
Gergely Orosz 21:58 I, I think everyone's done that.
Satya Nadella 21:59 [laughs] Everyone's done that, and I've done my fair share of it and learned from it, hopefully, and will get better. But that said, if you sort of say, well, let's take even... Let's face it, right? Which is today, when I look at the CVEs in Windows, right? Um, because you now have AI models that are finding vulnerabilities.
Gergely Orosz 22:15 Yeah, the critical vulnerabilities.
Satya Nadella 22:16 Yep, and so we now need to go fix them all.
Gergely Orosz 22:19 Yes.
Satya Nadella 22:19 And so therefore, there's a new pipeline. So in fact, if I look at even the Windows from crash traces all the way to fixes, they are building out, uh, essentially a new type of software factory, except this is a brownfield, right? Which is the build system of Windows st- is still the build system of Windows. In fact, if you think about in all these brownfield projects, the most difficult part is builds and CI/CD.
Gergely Orosz 22:44 Oh, yeah. Oh, yeah.
Satya Nadella 22:45 Um, and then of course, you gotta really, you know, even, you know, if I look at the amount of change that underneath even GitHub, right? Which is if you think about it, right?
Gergely Orosz 22:52 Yeah.
Satya Nadella 22:52 Like, you know, we've had... I mean, suddenly all these coding agents showed up at work at GitHub, and the scale has gone through the roof.
Gergely Orosz 22:58 Yeah, it's a superhuman level.
Satya Nadella 22:59 Yeah. And so therefore, we have to fundamentally change the entire, the Git protocol, the storage system. So we are working on every part of this to make sure that we are living in the brownfield as opposed to... I mean, the greenfield stuff we'll always do, but the real world is all about brownfield, and the brownfield requires stepwise, you know, hardening of systems, rethinking of the, the core primitives, right? All the way from source code control to build to CI/CD that works in a brownfield project, and that takes time. That takes investment. That takes, uh, thought, and the sequence of operations or the order of operations is very, very critical. So one of the things that I want our teams is it's not about... One nice thing I like about the transformation is this is not about, oh, here is some new shiny object, and here is the team that's doing that.
Gergely Orosz 23:47 Mm-hmm.
Satya Nadella 23:47 And everybody else lives in the, uh, old world. Like, everybody across the company gets to use the new tool chain and the new ways of working and tackle the challenge in front of them on any product, whether it's Windows or SQL Server or a cloud native service, what have you, and that I think is
Why adopting AI is different to adopting React
Satya Nadella 24:06 what we are seeing.
Gergely Orosz 24:06 To be fair, like, this doesn't sound all that different to what we did in the past because when there was a new technology, let's say React, which was a new front-end technology Everyone wanted to use it, and what we did is no one got permission to just stop and migrate to React. But when you built a new product or you added a new feature, you start to add it in, you start to mix it. So maybe it's not all that different to how we're adopting AI. But, but-
Satya Nadella 24:28 Yeah
Gergely Orosz 24:28 ... what, what is different about this? Is it the pace?
Satya Nadella 24:29 Yeah, it's a good one. Like, you know, sometimes I, I, you know, I kind of say, "Yeah, I've seen this before," and what have you. But I think the one thing that I do feel that's different this time around is that the, the physics of how we do things, right? That order of operations-
Gergely Orosz 24:47 Mm
Satya Nadella 24:47 ... the level of abstraction. Maybe, in fact, one of the fascinating things I think about is it is like when people moved, right? I, I, I joined the workforce at the cusp of when we went from... You know, in s- in fact, in college, I was mostly working on a VAX, right? You know, with a VT- VT-
Gergely Orosz 25:04 Okay
Satya Nadella 25:04 ... you know, terminal, uh, VT-
Gergely Orosz 25:06 Oh, this, this is a mainframe
Satya Nadella 25:07 ... uh, yeah, or a mini, um-
Gergely Orosz 25:08 Or a mini
Satya Nadella 25:08 ... right? Uh, VMS systems, right? So and then, and then I joined actually for a couple of years at Sun on a workstation, and then I came to Microsoft. And so and then, you know, the world kind of was stable, right? You mostly wrote code-
Gergely Orosz 25:21 Yeah
Satya Nadella 25:21 ... in an IDE. Throughout my professional career, it sort of didn't really change. I mean, new technologies came, but all those new technologies were new frameworks and new runtimes. It was not like con- the concept count radically changed. Even the mobile thing was sort of a miniaturized PC with new sort of, uh, user, you know, user interface, right? The new frameworks. This is a place where everything, what is the runtime, what is the framework, what is the IDE-
Gergely Orosz 25:47 Mm
Satya Nadella 25:47 ... what's the stack? Um-
Gergely Orosz 25:48 You write all, all, every single part of-
Satya Nadella 25:50 Yeah, so it's a little more, uh, of a change in how you think about, I think. Then let's not forget, a, a new model could drop, right? [laughs] Whether it is a new, uh, frontier model or a new thing like decision engine, and it could change again, right? This is where I think we also have to be ready for the regime to completely be transformed, uh, at any moment, if you will. And so therefore, I think these are two things at least I think about, that, uh, thinking of it, learning from the past, when were we at our best, individually or as companies or as teams in managing change, I think is always important, but also being open-minded that this time is different is also
The changing role of software engineers
Satya Nadella 26:29 good.
Gergely Orosz 26:29 Yeah, and, and also specifically for, for the biggest change for us software engineers and, you know, Microsoft has probably majority of the workforce is software engineers or people close to the code is we used to spend most of our time writing code, and most of our effort was learning at college, at previous jobs to be good at this. And this part suddenly disappeared, which I know for a lot of people, in- including me for, for earlier, it, it was hard to reconcile, 'cause we've never seen it with any technology change. It always added a new, a new tool. How do you see people inside of Microsoft or, or outside who you talk with reconcile this who, who are, are really good engineers and they've spent decades getting very good at coding? Which is hard to do, right?
Satya Nadella 27:10 Yeah. No, I think that that's right. I think... So this is where what at least I am observing, and as I talk to even people, uh, who are, you know, both been great software engineers, uh, previously and now are prolific even in the new mode of production, is the same skills are still required. It's just again that the what you think about, the order of operations, the tool chain, um, has changed. And so that's one of the other reasons where I don't think it's about devaluing the expertise. It's about really taking the expertise and making sure that you can exercise that with new leverage, right? That is where the nature of w- how you work has to change, as opposed to thinking that this is about, uh, software engineering no longer being important. And I think that we're in that phase, right?
Gergely Orosz 28:06 Yeah
Satya Nadella 28:07 ... uh, where we are trying to figure out how to value the new thing, and in valuing the new thing, you are suddenly going to even start valuing the old thing, if it makes sense, right? Which is when I look at the people, there's obviously somebody who's AI native who comes out of... Like, in fact, it was funny. Last, last GitHub Universe, uh, I went down and I met a bunch of, uh, college kids, and they've-- that was the first batch of college graduates who grew up in the AI era, right? Because they went to college when-
Gergely Orosz 28:37 When Cha-
Satya Nadella 28:37 ... GitHub Copilot-
Gergely Orosz 28:38 Oh, Copilot, yeah
Satya Nadella 28:39 ... right? They d- so they didn't know an IDE world pre-GitHub Copilot. It was, like, stunning to me [laughs] that that was sort of what's happening. So there is going to be people who are gonna come at this who are quote unquote, "going to be native to this tool chain." But I also think that people, when I see at Microsoft, anyone who has great depth and expertise in any part, has curiosity, and is sort of learning the new ways to work are absolutely flourishing in it. And so one of the things I, I'm hoping to ensure is we create that opportunity for folks because, at the end of the day, right, it, you know, it's about economic return on your professional careers that matters, and so therefore, we want to make sure at Microsoft you can both value the skill set you have and build the new skill set that the marketplace will value.
Microsoft’s voluntary exit offers
Gergely Orosz 29:25 I'm really liking how you're looking at this and also how you talked about how junior, new, new grads, early career people are contributing. They can get up, up to speed. But one thing that's been going around in, in dev circles, and I'll, I'll just lay it out for you, is people are speculating why is it that, that Microsoft is making the voluntary retirement offers? Like, what does this mean? There is this fear that could this be a prelude to potentially a layoff because of AI making, uh, teams more efficient, and I just wanted to ask you dead on the head. There's never been anything like this at Microsoft, which is what I actually paid most attention to, and also the fact that it is voluntary. How did your, your thinking and the company's thinking come together on this one?
Satya Nadella 30:07 Yeah, it's a great, it's a, it's a very important question. And, you know, one of the things that we discussed a lot and we felt was let's acknowledge two things, right? One is that, or maybe three things. One is that let's acknowledge that there is going to be plenty of opportunity going forward. The shape of that opportunity may be different than what is the opportunity, right?
Gergely Orosz 30:28 Yeah.
Satya Nadella 30:28 If you... let's even narrowly think about just software engineering, as we were discussing.
Gergely Orosz 30:32 Yeah.
Satya Nadella 30:32 So let's start there.
Gergely Orosz 30:34 Yeah.
Satya Nadella 30:34 Then the next thing we should say is, okay, great, let's create more of that new opportunity inside, uh, the company, right? That's where everything that we're talking about, whether you're working on Windows or whether you're working on AI training, quite frankly, you get to really e- equip yourself with new skills that are gonna be valuable inside of Microsoft and in the marketplace, right?
Gergely Orosz 30:56 Yes.
Satya Nadella 30:56 But the shape of what this new thing looks like is gonna be different than what-
Gergely Orosz 31:01 It's very different
Satya Nadella 31:01 ... the shape of what it was before, right?
Gergely Orosz 31:03 Yeah.
Satya Nadella 31:03 Team, team sizes, team workflows. So we need to take... It's not that we don't want the 200,000 people at Microsoft flourishing, all of them, and growing even. But the, the 200,000 people at Microsoft and growing will have to be configured in different ways, right? When I look at even at i- inside of Microsoft, some of even, let's say even the economic return, right? If you look at the wages for a systems engineer, right, or an infrastructure person, it's through the roof. Same thing if you are a researcher in training, right? So some of the expertise is highly competitive, highly valued, right? And so we wanna give more agency, quite frankly. In fact, this voluntary thing was mostly about, let's give everybody more agency to get themselves slotted into places, uh, that make sense for their economic opportunity long term. That's, I think, the key thing. You know, I've been CEO for a long time. I was a senior exec before that and what have you. But at the end of the day, though, I did grow up as from an IC to this, right? So I think about lot of the times when I was an IC or a lead, right, and maybe a, a manager of, uh, leads, that's sort of the lens through which I think about how should we create opportunity inside the company. I don't wanna be stuck in a team that's not transforming. Even inside of Microsoft, let's face it, right? It's not like I can sit here and say every part of Microsoft is sort of really got the memo, and they're all transforming at the capa- I wanna give them... You know, if you're, you're... if you're in a team where you feel stuck professionally, uh, you can vote with your feet. I don't want you to because, quite frankly, there are many places you can go inside of Microsoft itself. So that is another opportunity we wanna create. So in that context, we are trying to give more agency to people, uh, realizing that this is a time of tumult, right? I, I wish I could just sit here and say it'll all be the same. I cannot, right? And, you know, and, and, you know, this is one of those places where I, I wanna be as transparent about the change. I wanna make sure we do, I, I do the hard work of creating all the opportunity at the company, and then make sure that our workforce is able to really make their professional growth come true here.
Gergely Orosz 33:23 I mean, I think you're, you're saying this very nicely and thoughtfully, but how I would translate it is, you know, the world has changed big time, and we saw, for example, with Claude Code has been such a fast change, and the teams who fall asleep at the wheel, if you will, we c- you cannot afford it. Uh, so you need to either go with it, realize that the, the world has changed, my work as a software engineer will change, my tools will change, and either I'm on board with this, I figure out how to be enthusiastic about this and see all the opportunities, all the engineering challenges with building the factories, with the new workflows, or I decide, well, I'm not going to do that. And for most places, you're kind of stuck, but you're actually giving an option for people to decide if you would like to check out from there, you can right now, and there's no hard feelings.
AI anxiety and changing roles
Satya Nadella 34:05 I think so. And I also feel like... look, I think let's sort of, if you come down to it, and I care a lot about this, right, which is we have created enormous anxiety, enormous anxiety in people sort of feeling that they don't have control of their own destiny.
Gergely Orosz 34:22 Mm-hmm.
Satya Nadella 34:23 Because the way we have talked about this AI revolution is, yeah, you know, we have been-- people say, "Hey, this maybe, you know, the singularity is here, and therefore maybe we are building, there'll be one company," or, you know, "No, there'll be no jobs." All that sort of leads to anyone who even wants to change be sort of anxious.
Gergely Orosz 34:45 Yes. Stress.
Satya Nadella 34:46 And so I kind of feel that this is where... Look, we're a company of 200,000 people. You know, I know that there's gonna be a lot of change in what each of us do. Like, think about it, right? One of the fastest growing jobs in Microsoft is FDE.
Gergely Orosz 35:01 Microsoft as well.
Satya Nadella 35:02 Yeah, right?
Gergely Orosz 35:03 Yeah, across the industry right now.
Satya Nadella 35:03 Across the industry because in some sense, if you think about it, right, you have an account, uh, um, uh, rep-
Gergely Orosz 35:09 Yeah
Satya Nadella 35:09 ... very important. Then right next to the account rep is sort of our, uh, customers, uh, you know, uh, the technical support folks, right?
Gergely Orosz 35:17 Yeah.
Satya Nadella 35:17 And the customer, um, it's, I think, CSU is what we call a customer success.
Gergely Orosz 35:22 Yep.
Satya Nadella 35:22 Uh, and then we have even the technical support people, and then you have, uh, the FDE team.
Gergely Orosz 35:27 The Forward Deployed Engineers.
Satya Nadella 35:28 All of for- all of these things require a complete... Like, they all should be going to the same preceptorship that any software engineer is going, if you will, right? Because you can all... Like, I know even LinkedIn, I think they made this change inside where they call them full stack builders, right? Which they, they combined roles. So all that change, I think there's opportunity, but you have to sort of walk the hard walk of really making the structural changes, getting people slotted, giving them opportunity, giving them, uh, the wage support, newing- knowing how to evaluate people with their productivity and their, uh, excellence in their new jobs, in their new slots. This is the hard work. Any incumbent, you know. So that's why, you know, the celebration of the new, which always should be there, right? That's how competitive marketplaces work. Uh, look, you know, we are a 51-year-old company. We're going to sort of be comfortable in our skin. We wanna serve our customers well. We wanna create fantastic economic opportunity for the employees at this company doing great work, given our mission to empower people and organizations.
Junior hiring
Gergely Orosz 36:35 On the other side of this, but I, I just wanna get this on the record. So when we talked about Uh, hiring new grads. So you, you are still hiring new grads, junior people, you're investing in them. You're, you're seeing that... Because one of the worries in a lot of other companies at startups is, um, they've slowed down or even stopped hiring 'cause they're thinking, "Well, with AI, the most-- the people who can use it the most efficiently," as, as we previously mentioned, the ones who have expertise, and they can leverage that, and they're very hesitant to hire any new career people.
Satya Nadella 37:01 That's a great point. So, so one of the things that we're trying to do is in this change, this is why I think a little bit of the trends have to be watched carefully over sort of slightly longitudinally versus just, you know, one year because-
Gergely Orosz 37:14 Yeah
Satya Nadella 37:14 ... um, we're in the process of a lot of change, right? So first job is to make sure internally all of the folks are getting reorg-ed to places that make sense, right? That, that-
Gergely Orosz 37:25 Yeah, that is step one
Satya Nadella 37:26 ... right, just step one. I mean, like e-even inside of a team, right?
Gergely Orosz 37:29 Yes.
Satya Nadella 37:29 You just want to get the configuration right. Then it makes sense to, oh, what is the industry hire or a new college hire? You add to this, right? And, and-
Gergely Orosz 37:38 Yes
Satya Nadella 37:38 ... so a little bit of what's happening, I think, is the slowdown may be a slowdown to get those, quote-unquote, "new factories" of software engineering built such that new inputs, not just tokens, humans, can come in and then in this new configuration give you high leverage, right? I mean, let's face it, when-- what is an AI native company? They start with a token budget and a human, right?
Gergely Orosz 38:04 Yeah.
Satya Nadella 38:04 Then they add the, that person maxes their token budget and, and then says, "Let's add the next human," and then that human gets a token budget, and then their factory gets the budget.
Gergely Orosz 38:14 Yes.
Satya Nadella 38:14 That is the constructionist way, and it's not like, okay, those companies, if they succeed, they will also be big one day.
Gergely Orosz 38:21 Yeah.
Satya Nadella 38:21 And they will-
Gergely Orosz 38:22 Some already are
Satya Nadella 38:22 ... and some already are, are, and you-- uh, every company is gonna start looking like that, and every project team or product team will look like that. And so that process of reconfiguring new discovery, uh, and configuration, it'll take time, and that's where I think, uh, you know, trying to draw too many lines as long-term trends, uh, I think is too early.
Gergely Orosz 38:45 Before we get back to the conversation, I'd like to talk about Linear, our season sponsor. Until recently, I was thinking of Linear as a tool that helps plan and organize the work, but it's much more than that. A lot of teams use Linear to ship changes from idea to merge in GitHub, all without leaving the tool. I sat down with Dima, an engineer on the Linear team, to see how devs inside of Linear use Linear to build all of Linear. So here's a real issue. When you submit a review with unsent draft comments, Linear warns you about these comments, but it didn't tell you where those comments were. A customer complained, and Dima decided to fix it. But for the fix, Dima did not open his ID. Instead, he opened up Linear and described the issue to the agent. The agent built a fix, created a PR, and attached Storybook screenshots for easy verification. You can see the fix with the draft comments linked on this screenshot. In the PR, you can then open the preview with one click from Linear to play around with the change and see that it worked. And here's my favorite part, guided reviews, which is work in progress. Guided reviews is a new code review experience where the important stuff just pops out. The top of the review has a summary and a diagram of the change, and the pull request is divided into chapters that walk you through what has changed. These blocks highlight the important changes in a way that's easier to understand and review. Oh, and when Dima is finished with all of this, he just self-approves the code, and it's merged into GitHub, all without leaving Linear. If you take away one thing from this, Linear is no longer just a place for planning tickets and organizing the work. It's where all the work happens, creating the issue, kicking off the agent, checking out the preview, and doing the review, and merging to production. Linear is the product development system for teams and AI agents, and I'm loving this evolution. Linear is the product development system for teams and for AI agents, and I'm loving this evolution. Check it out and get a six-month trial at linear.app/pragmatic. If you've ever worked on B2B software, you know how this goes. A customer likes the product, then their security team sends a list, SSO, SCIM provisioning, role-based access. None of it is what you set out to build, but the deal waits on it. WorkOS is the alt infrastructure that covers all of that, so nobody on your team has to debug a customer's SAML setup. The newer version of the problem is agents. Once an agent is acting inside of a customer's systems, the enterprise wants to know what it's allowed to do. That's what WorkOS Airlock is for. It's intent-based access control. Most access control only asks who you are. Airlock also asks what the agent is trying to do at the moment it tries to do it. Clear-cut rules like no agent deletes cloud resources run as plain code. For the fuzzier calls, an AI judge evaluates the policy at runtime. You write these policies in plain English, and Claude can pull the ones you already had out of Notion and Jira and import them for you. Your agents, whether that's Claude or Devin, connect through a single access point, and your MCP servers sit behind it. Airlock is a new layer on top of your existing permissions, so an agent can never get more access than the person who invoked it has. When something risky comes up, Airlock can escalate to human for approval, say, over Slack. The idea is to write the rules once and spend human attention only on the calls that need it, and every request and decision is logged. Visit workos.com/airlock to learn more. Now w-we know when everyone is building their, their software factories are changing how they work. A big trend now that we go down to a little bit of the how this is done, big trend across the industry that I'm seeing and I'm sure you're seeing as well, a lot of tech companies are moving to open models as well. The, a lot of them are, are spinning up their inference or companies like Revolut are buying their inference, they're buying their B200s and just launching the models on it. They all have their own reasons, but from your vantage point, you know, Microsoft is also in the open model serving business with, with Foundry, for example. How big is this trend, and is this in-inevitable? I'm asking myself, are there parallels to the open source movement and now the open model movement?
Satya Nadella 42:35 Yeah, I
Open models
Satya Nadella 42:36 think that, that there are for sure the parallel, which is, you know, you know, there's sort of going to be closed models, and there'll be competition amongst them, and there will be sort of an alternative to obviously closed will be open. Uh, open gives you flexibility. In fact, I th-- you know, one of the ways I come at it is with just this. What does a frontier ecosystem look like, right? It's can't be... If you just get past this thing called, uh, there's gonna be one frontier, uh, model to sort of have all of the world's knowledge, right? If you don't b-buy that, right, uh, then you have to assume that there should be, in some sense, as many frontier models as firms in the world, right? Because after all, if you go back to actually Hayek, uh, the, uh, his description of what an economy is, it's all about knowledge being distributed, right?
Gergely Orosz 43:25 Mm-hmm.
Satya Nadella 43:26 In fact, uh, his, you know, his entire thing about pricing, uh, is a beautiful sort of explanation of, hey, it happens because of knowledge being tacit and distributed throughout the economy, and every firm needs to be in control of it. And if so, then I would even say every firm is essentially got both human capital and token capital. So if every firm is gonna have both token capital and human capital, the token capital can be an open weight model into which, uh, you know, you've embedded your knowledge. That's one. It can also be in the context layer. You could even be using multiple closed models. In fact, collecting even the traces, uh, of your usage of those closed models, and then using those traces to maybe train an, a small model on an open weight model-
Gergely Orosz 44:12 For yourself, for example
Satya Nadella 44:12 ... for yourself, and keeping, you know, combination. When I look at even Copilot, in fact, whether it's GitHub Copilot or Copilot, they're all designed as these multi-model system, right? In fact, I would say maybe even by the next time you and I talk, everybody would say, "It's not about even open or closed. Everyone has a model system." In fact, it starts with even a decision engine which says which model to use for what task, and then I have my context and memory and my action space separate from any one model because otherwise you have a complete lock-in. In fact, one of the things I, I, I think about is like, wow, if you've really got your harness, your model, your memory and all coupled, how would you ever get out, right? In fact, what are you doing and what are, what do you own [chuckles] versus what is owned by the model? Uh, because no... The model will basically collapse into it everything it sees. Um, and so I think that this dynamic is getting well, better understood. It's, you know, most people again think, "Oh, this is just some competition amongst tech people." Remember, there's no limit to intelligence. Every bank, every healthcare company, every insurance company, every analyst out-- Everybody needs to sort of have a real thing, architectural approach to figuring out how do they manage to control their own learning and knowledge and have firm differentiation. And in that context, open weight models is one strategy that I think
Owning your AI infrastructure
Satya Nadella 45:39 has legs.
Gergely Orosz 45:39 You know, this is very interesting because I, I talk with a lot of mid-size tech companies, startups, and almost all of them are building the things that you just draw. Their own harness, their own context layer, their own, own context graph, their own inference. And I thought initially I'm like, well, this kinda makes sense because engineers love to build, and if you wanna get AI engineering experience, the, the least risky thing is to build something internal. However, I never thought of, of this part where it's actually these engineers building for the right reasons, which is the strategic reason or not, they're probably doing their company a service. And you're saying that most companies should probably consider owning the system, having replaceable parts primitives because-
Satya Nadella 46:18 That's correct. So in fact, what you're observing is correct, which is it's fascinating, right? In fact, I would say if you're a bank, you should check how software companies that are trying to manage in this ecosystem to become frontier, uh, are doing it. They're not l-- c-ceding control. So in some sense, that's what the bank should be doing. So what is the ba-- In, in that they will have leverage. So for example, what we have done, you know, what we describe as this IQ layer, is we have taken, for example, the harness that we have underneath Copilot and GitHub Copilot-
Gergely Orosz 46:50 Yep
Satya Nadella 46:50 ... made it a first-class thing that you can now go to Foundry as a managed service and you have the harness.
Gergely Orosz 46:55 Yeah.
Satya Nadella 46:55 So in there, let's say you're building a supply chain system, you can start with our harness just as essentially an open, or you can bring Py or any other open source harness-
Gergely Orosz 47:04 Yeah
Satya Nadella 47:04 ... as well in there.
Gergely Orosz 47:05 Oh, we love Py.
Satya Nadella 47:06 Uh, but you can just have it, like, as a managed service, right? It... So battle-tested, uh, harness from Microsoft, which we ourselves are using, is just available there. And then you can have all the Foundry models, right? So you have a harness, you can use multiple models as endpoints, you can have your context layer that is completely separate, right? Your memory and context, uh, is yours then. So I think now we have a model system. Uh, and, oh, by the way, the action space, so with all the plug-ins and skills and connectors, right? All separate from any given model being, only having the visibility to it. So I think a good sort of classic middle-tier platform is emerging even for model-first development, where you're not just captured. And then you can e-eval everything, right? You can say, "Hey, I have an eval and my private evals will matter more," right, all these public benchmarks, which by the way is great, but you need to have your own private eval for what is the outcome that matters to you. And then look at in your RLE, the real performance for across all these models and continuously optimize. In fact, when I look at even, you know, even with our customers, they start with a frontier model, then they say, "Well, great, I've got all those traces. Now I'm gonna flip to... Hey, this is a deterministic workflow. I mean, it's not like I don't need the next big model drop. I wanna now cost optimize. I'll drop, you know, an MAI Flash model, drop it in there, use the traces to fine-tune it," and there you have it. So therefore, that's all stuff you can do in Foundry. So that type of work, I think, is what's gonna increasingly be true.
Gergely Orosz 48:38 We're, we're saying that's... You're, you're already seeing that a lot of companies have their reinforcement learning environment as well on top of the evals, so that they can, they can stay in control ... control pricing, and also, I guess, not leak their business data to some of the AI companies that might want to train their models on it.
Satya Nadella 48:56 That's right.
Gergely Orosz 48:57 Right?
Satya Nadella 48:57 So if you think about it, right? So the way, the simple analogy I have, at least in my head is, you know, people, you know, in the past, whether, you know, in an insurance company, in a bank, in a healthcare company, said, "Hey, I'm gonna get a relational database."
Gergely Orosz 49:10 Yeah.
Satya Nadella 49:10 "Great. I'm gonna deploy a relational database. On top of it, I may even buy some software that runs on that relational database that is sort of comes with its own business logic. But then I'm gonna extend it with my own business logic that I write, right? And then I control it, and never at any point is my data in the database going to somebody else." It's not like when the database vendor says, "Hey, I'm no longer gonna give you a database update." You still can migrate out.
Gergely Orosz 49:38 Yeah.
Satya Nadella 49:38 That's the question you have to... How are you gonna migrate your memory out if your memory is in the embeddings of a given model when that model company says, "You know what? Tough luck. I can't do a next update to you"?
Gergely Orosz 49:52 Plus, I guess what we talked about, when we have new primitives come, how are you going to integrate them?
Satya Nadella 49:56 That's a great point too.
Gergely Orosz 49:57 Because, because if you're too reliant on a, on a vendor or a series of vendors, you'll have to wait for them to maybe do it. And I, I guess it's also easier to build right now, like, right? If you have competent engineers, we're good at this.
Satya Nadella 50:09 Yeah. So I think that there are two enterprise architectural decisions that I think, interestingly enough, are... I, I'm hoping that people are gonna start talking, right? Because, and in fact, to your point, all you have to do is look at a software team today in a software in- industry. They're all figuring this out to stay independent.
Gergely Orosz 50:28 Oh, yeah.
Satya Nadella 50:28 I think this has to become more of the reality in the commercial space.
Gergely Orosz 50:32 Yeah.
Satya Nadella 50:32 Uh, and there are two... Are how do we avoid this reverse information paradox, which is don't leak your value. You as a firm need to be in charge and control of your own learning loop. What's the architectural approach? How are you making sure your context is separate from the models, and you're using multiple models? Uh, that's, and your harness is separate from the context and the models because that, I think, is the only way you can assure yourself that you can replace any model. In fact, my acid test for that is you should be able to replace any model and still hill climb on an eval that's your private eval.
Gergely Orosz 51:06 Yeah.
Satya Nadella 51:06 If you can't do that, then you have to ask yourself, how are you a sovereign firm, right? Like-
Gergely Orosz 51:14 Yeah
Satya Nadella 51:14 ... that means you do not have control of your own output.
Gergely Orosz 51:18 Yeah.
Satya Nadella 51:18 Uh, so that's kind of the first-
Gergely Orosz 51:19 You're just sitting on a ticking time bomb.
Building trust in AI agents
Satya Nadella 51:21 Yeah, I mean, you're done. I mean, like-
Gergely Orosz 51:22 Yeah
Satya Nadella 51:22 ... is my, my, my point. And so the, then the next thing is you now need a trust architecture, right? Which is you kind of have to rank in a world where you now know scaling laws work, except w- with scaling comes new capability, but not alignment. In fact, no mechanistic understanding, that hopefully someday there's a science breakthrough, but right now we're getting more and more capable and less and less reliable, like, which is the most dangerous place to be in. And so that means you have to separate out architecturally authority from intelligence. If your intelligence has authority and it's unreliable, again, you're taken, right? You have a massive insider risk problem. And so you've got to treat these agents as insider risk. That means you've got to have a trust system, and then a lot of things, like even this chain of thought, man, like this, uh, the amount of... Like, this chain of thought has to be not in new release.
Gergely Orosz 52:14 Yeah.
Satya Nadella 52:14 It has to be in, in, in human language. It needs to be auditable. It needs to be logged such that it's not tampered. It's not just in, you know, pre-training or in, uh, uh, you know, RL that things happen, right? Which is in test time compute things could happen because they could reward hack. And so we have some serious amount of safeguards you have to build, um, at, at runtime, as I describe it, which is the trust architecture that al- ensures that you can treat models and, and agents as insider risk and monitor them and have observability and what have you. And then ensure that you have control over your learning loop.
Gergely Orosz 52:53 As, as, as an engineer, all, all I'm hearing and all I'm seeing is there's so much new type of work that needs to be done, so many novel systems need to be built, which we don't have a blueprint for. I mean... And probably the best way to do is, well, build it, also talk with peers who are building it at the same time, and I'm sure we'll have blueprints and certifications in, I don't know, five to 10 years or something. But right now, this, this is a job. It's-
Satya Nadella 53:14 Correct. And in fact, in fact, um, one of the things we have our conference, Ignite, coming up next week, and I'm excited about it because that's kind of what I want to make sure we do a good job is communicating that, hey, this is all doable. Like, there are blueprints. There is a lot of i- innovation happening in how companies. And so I think that we are reaching that stage where it's not just about the shiny object and the novelty effect, and I think people have to sit back and say, "Hey, how am I creating enterprise value in my firm?" And once people sit and talk about that in a little more depth, then I think these patterns of success become much clearer.
Local models and hybrid intelligence
Gergely Orosz 53:48 Now, as, as an engineer, one thing that I, I feel very lacking is all of these AI models, they run in the cloud on someone else's server or a super expensive B200 that I cannot afford, or my company will not buy it for me, or if, if you, if you are, I mean, you're lucky. But would it not be nice if it just ran on my laptop?
Satya Nadella 54:04 That's a great point.
Gergely Orosz 54:05 And local AI, until now, it's been difficult, uh, very hacky. Actually, funny, Microsoft is, is the one that's innovating. There's a new Surface Ultra laptop that Scott Hanselman gave me a demo-
Satya Nadella 54:16 Nice
Gergely Orosz 54:16 ... and I now wanna get my hands on 'cause it, it has a chip. It has a local coding model running on it. Where do you think local models fit into the, the AI loop? And as a developer, I feel it's desperately missing, but am I kind of alone? You talk with way more people.
Satya Nadella 54:31 No, I think it, it, it's, it's a great point, right? So one of the, the things is we're very excited about making sure that the, the PC as the form factor, um, you know, we innovate in, uh, in the age of AI. And so to me, the way I've been thinking about it and how we've been executing on it is- Oh, I've always felt like distributed computing will always remain distributed, so why not use all the power and all the tokens that are out there versus just the stuff in the cloud? So that's sort of the inspiration even for Ultra. But, but there is lots of innovation, in fact from, you know, whether it's Nvidia or AMD or Qualcomm, so it's fantastic. Intel, there's good silicon work happening and systems work, and this is... In fact, it's already true. What is it? Like, last year's Frontier can run on your laptop and last quarter's-
Gergely Orosz 55:21 It's wild
Satya Nadella 55:21 ... uh, Frontier can run on your desktop. I mean, right? That's kind of like the capability. So you-
Gergely Orosz 55:26 It's, it's like how PCs used to evolve, right?
Satya Nadella 55:27 Exactly. So it's great. So now that you have that, then one of the things that I think about, again, goes back to my decision engine and routers, right? So when I think about HydraFusion, um, I think that's the term we use, I forget now [laughs] , which in GitHub we have a f- you know, a way to route, right?
Gergely Orosz 55:43 Yeah.
Satya Nadella 55:43 I love the GitHub, uh, because all nowadays... In fact, in Copilot, the last time I chose a model was-
Gergely Orosz 55:48 It's Copilot Fusion.
Satya Nadella 55:48 Yeah, Copilot Fusion. So basically we want to be able to have this router pick the models, right, for the task, and so that means... In fact, I see it in Ultra sometimes. I mean, it p- you know, my suddenly I see the fan go, right?
Gergely Orosz 56:02 [laughs]
Satya Nadella 56:02 Because my local model is being used. Because especially-
Gergely Orosz 56:04 Yeah
Satya Nadella 56:04 ... in an agent swarm, uh, where you have multiple sub-agents, then you can invoke for some sub-agents a bunch of local models while you're using even the cloud models together. Uh, and so yeah, this makes sense. Architecturally, it makes sense. Economically, it makes sense. And so we are in the beginning of what I'll call this hybrid intelligence era. Cloud will continue to grow. There's going to be infinite amount of sort of demand for these tokens, but that means you can also start thinking about the, you know, the form factors at the edge as also token factories. In fact, I kind of think of it as the unmetered intelligence.
Microsoft’s model strategy
Gergely Orosz 56:39 Yeah, because you, you don't need to worry about how much you're using it.
Satya Nadella 56:42 That's right.
Gergely Orosz 56:42 I guess this is where it's now starting to come together for me because the, uh, MAI Code, uh, w- the, the Flash 1.4 model, I'll be honest, I wasn't too impressed. I don't think anyone's was too impressed. But the one detail I was impressed with, when it comes to local models running on any laptop, I always assumed it must be open models. However, the MAI Code can be downloaded on a Windows machine even though it's a closed model, and it can be run there. There's the infrastructure there and I'm like, "Huh, could there be a future where, like, other closed models... So I, I could choose on my laptop, like pick and choose, like either I download them and maybe it's free or I pay very little?"
Satya Nadella 57:17 You know, to your point about the, the Code Flash models, getting them even all the way, uh, to a laptop is core priority for us and we are excited and that's kind... When I look at the code tab inside a Copilot, right? Which is, uh, even, you know, independent of GitHub Copilot. Now code co- writing a document or writing an application, you can easily use these models on your PC and that's exciting. But just to kind of step back and say what are we doing with even MAI models, right? First of all, through the partnership with OpenAI, we have the OpenAI models and, and we are gonna continue to use those OpenAI models, right? Uh, on, on top of that, what we are saying is, okay, let's sort of innovate in a new model family ground up that truly-
Gergely Orosz 57:58 Gr- ground up meaning you build it from zero
Satya Nadella 58:00 Yeah. First of all, we have a... You know, I think we disclosed even the new MAI 2 base, which is the pre-training and in fa- in fact, it's one of the best disclosures of a pre-training recipe and regime. Uh, so for those who are, uh, you know, your listeners should go look at it, right? It's probably-
Gergely Orosz 58:14 Yeah, we'll have a link at the-
Satya Nadella 58:14 And people tell me from the outside that it's the most detailed descriptions of pre-training, right? Because there are very few places where you can go to and get it, and it's completely, you know, clean room so to speak-
Gergely Orosz 58:26 Mm-hmm
Satya Nadella 58:26 ... uh, implementation of a, a pre-training run. So therefore we're continuing to do that. But then the place where we are able to sort of innovate is put, I'll call it new points on the frontier curve, where using our products, right, whether it's cyber, whether it is knowledge work, whether it's coding, how do you put new points on the frontier where you're both flop sufficient on training and you are efficient on tokens in deployment? And once you are in a world where you're handing high level intents to many sub-agents, the sub-agents can be using multiple model families, right? That's, I think, the way. Like this idea that, oh, I'm like wedded to one model family may not be true if there are choices. Agents will be smart in picking all of the models that allow them to get the task done in the most efficient way, and that, I think, is our goal. Our goal is to give more choice as opposed to just one
Advice for engineers
Satya Nadella 59:26 model family.
Gergely Orosz 59:27 I, I really like how, like you're, you're setting out choice because a- as a developer, I love choice. It also helps lease the competition, better prices and so on. And as closing, this change is very fast. Everyone I talk to who've been in the industry, they said they've seen, you know, like change maybe similar to this, maybe not as big, but not, not as quickly. You've been through multiple change cycles. Wh- when you started, it was at a very different time. How would you approach this change as a software professional when your goal is, "I would like to be a amazing software engineer in this new age of AI in a year or two"?
Satya Nadella 59:58 [laughs] You know, it's sort of the stuff we talked about. Quite frankly, even for me, I think just making sure that one gets grounded in what is this change about, right? Uh, it's not just about the headlines and it's not just about-
Gergely Orosz 1:00:13 It's definitely not the headlines
Satya Nadella 1:00:14 ... you know, I love X and, you know, it's great, but it's just not [laughs] about, uh, the hype cycle-
Gergely Orosz 1:00:21 Yeah
Satya Nadella 1:00:21 ... and that constant need, um, uh, to talk. [laughs] Uh, but it's ironic in a podcast to say that.
Gergely Orosz 1:00:29 [laughs] Everyone who's listening.
Satya Nadella 1:00:30 But it's do, do more, uh, learn more-
Gergely Orosz 1:00:34 Yeah
Satya Nadella 1:00:34 ... and, and hands-on, like-
Gergely Orosz 1:00:36 Experience, see it, right
Satya Nadella 1:00:37 ... experience it firsthand. That's, you know, quite frankly, that's kind of what I would even say for me. If I could change the ratio of my, you know, talk to do, I would do it. This is the time. If one piece of advice, whether you're mid-career or even a CEO like me or, uh, or a fresh, uh, college grad- The more you can take the time to sort of learn, to do, be in teams that are doing, [laughs] uh, the better it is, versus, um, I think anything else. Because at times, like, we can... At some li- at some level, I sometimes think about it, and when am I at my best, it's when I'm in the school mode. Uh, so let's get back to school.
Gergely Orosz 1:01:18 Satya, thank you so much.
Satya Nadella 1:01:19 Thank you so much. It's such a pleasure.
Closing takeaways
Gergely Orosz 1:01:21 Well, this was an awesome experience, and we really covered a ton of ground with Satya. A recurring theme that kept coming back: What kind of software engineering work becomes more important when coding becomes cheap with AI? We talked about how the things both before and after coding, that is planning and validation, both become more important, and this will be activities as us engineers will spend more time on. I also observed a lot of tech companies building their own coding harness, context layer, and AI infra, and I assumed that it's because engineers just like to build with novel technology. But Satya pointed out that it's actually suicidal strategy for a company to not own their AI infra and their AI intellectual property. In fact, he thinks that every successful company will build out this own AI infrastructure, and those relying on a single vendor or AI lab are making a massive strategic mistake. Talk about us devs enjoying building new stuff, [laughs] and it's paying off. I can see us having a lot of opportunities to build this new type of AI infra and these internal software factories. Finally, software engineering roles and expectations are also changing. Satya shared that the one of the fastest-growing jobs inside of Microsoft is Forward Deployed Engineer. This is a position that has not existed a few years ago. Satya expects to see a lot of reorg inside of Microsoft, where teams become smaller and roles change, and the voluntary exit program is an opportunity for people who leave who don't want to go through what will probably be a really intensive period of change, much more than before. I would assume that this kind of change with reorgs and role changes, all of these being more intense than before, is probably not just true for Microsoft, but it will be true for a lot of other tech companies. In the end, I walked away being more energized from this conversation. Yes, the industry is changing, but what I understood is how Satya sees that a lot of software engineer work is waiting to happen with these new AI-related primitives, like decision models, and some of the primitives that have but not been invented. And us engineers will need to build these new systems with these new primitives, deciding what goes where, how to change it, what makes sense, how to deploy it, and just keep learning from it. Do check out the show notes below for related deep dives on AI engineering concept like evals, inference engineering, loop engineering, and more. If you enjoy this podcast, please do subscribe on our favorite podcast platform and on YouTube. A special thank you if you also leave a rating on the show or share with colleagues or friends. Thanks, and see you in the next one.
Episode duration: 1:03:38
In the uListen app, the transcript lights up word by word as you listen. Get uListen
Transcript of episode 0NE89Nzfk20