CEOInterviews.AI
Start App
Get an email when Misha Laskin gives a new interview
One email per new interview. Unsubscribe in one click.
Misha Laskin
Co-Founder and CEO, Reflection AI

Ex‑DeepMind Researcher Misha Laskin on Enterprise Super‑Intelligence | Reflection AI

📅 Jul 17, 2025 The MAD Podcast with Matt Turck 66 MIN 11374 VIEWS 170 SEGMENTS · 2 SPEAKERS
What if your company had a digital brain that never forgot, always knew the answer, and could instantly tap the knowledge of your best engineers, even after they left? Superintelligence can feel like a hand‑wavy pipe‑dream— yet, as Misha Laskin argues, it becomes a tractable engineering problem once you scope it to the enterprise level. Former DeepMind researcher Laskin is betting on an oracle‑like AI that grasps every repo, Jira ticket and hallway aside as deeply as your principal engineer—and he’s building it at Reflection AI. In this wide‑ranging conversation, Misha explains why coding is...

Questions asked in this interview

12
  1. 4:15Do people agree on what that means, or is that just more like something that directionally feels very impressive, but not everybody exactly knows what that means?
  2. 7:55Is that, was that the wrong analogy?
  3. 11:54How is that different or similar to basically doing a combination of coding and RAG and RAG to bring in the context of the enterprise?
  4. 19:26Was that a temporary solution or are those parallel capabilities?
  5. 26:32And is a sort of like snappy one-shot agent necessarily a bad thing if you direct them at small problems and then you try to put them together, or does the sort of individual little agent need to be smarter?
  6. 29:08... do those data sources need to have a special protocol to lend themselves to agents or like MCP-style kind of infra so that the super intelligent agents that go around and sort of grab information everywhere can interact with them?
  7. 34:50What was your journey to starting all of this?
  8. 36:48So where was nowhere America that you mentioned? What city?
  9. 42:07So you evolved from physics to AI, and then what was the next step?
  10. 47:28And when was the decision to leave and start a company, and what was the thinking?
  11. 53:07Where does it all land currently?
  12. 58:57How does one sort of recruit and keep talent in this environment when you are, you know, very impressive obviously, but still a small startup?
Misha Laskin 0:00 ↗
I do think there will be a general super intelligence, but I think that it won't be one lab that has built it, but it'll be kind of the plurality, like the collection of all intelligences will be a general super intelligence.
Matt 0:11 ↗
Welcome back to the Matt podcast. Today my guest is Misha. Misha is a former DeepMind researcher who left Google after shipping Gemini 1.5, convinced that LLM had crossed a critical threshold, and started Reflection AI, a startup that emerged recently out of stealth with $130 million in funding and a goal to build super intelligence autonomous systems. We talked about super intelligence a lot in this episode: what it means, how all building blocks to create it already exist today, and how coding and enterprise AI are the best paths to build it.
Misha Laskin 0:43 ↗
I think we have everything. The sort of series of breakthroughs that need to happen, I think many of them have happened. We're really focused on coding to start for a number of reasons. This is a super intelligence complete problem. Like if you really solve this Oracle organizations just for coding, you've basically built all the capabilities you need to have super intelligence.
Matt 1:02 ↗
We also chatted about their brand new product announced today as we publish this podcast.
Misha Laskin 1:06 ↗
We're launching our first product and the first milestone on the path to super intelligence: the best-in-class code research agent built for organizations. It has this new concept that I don't think has been introduced to date.
Matt 1:17 ↗
Finally, we covered what it's like building a super intelligent startup at a time when the big AI labs and Mag 7 companies are poaching top AI talent left and right.
Misha Laskin 1:26 ↗
I think the entire makeup of the research team was earning a lot of money at big labs. We tend to attract people who have that kind of internal drive in them of wanting to be part of that next story.
Matt 1:37 ↗
Please enjoy this deeply insightful conversation with Misha. Hey Misha, welcome to the Mad Podcast. Thanks for being here in person today.
Misha Laskin 1:47 ↗
Yeah, thanks Matt. Thanks so much for having me.
Matt 1:48 ↗
You are the co-founder and CEO of Reflection AI, which is a super exciting startup that up until recently was pretty much in stealth. You sort of came out of stealth a few weeks ago, and you have some exciting product announcements that we're actually going to discuss today. Before we do that, tell us about the company itself.
Misha Laskin 2:10 ↗
We're a research and product company in AI that was founded by myself and my co-founder, Giannis. We are both longtime researchers at DeepMind. And generally the makeup of the team is a lot of folks who did large language model training and reinforcement learning, building reinforcement learning systems within companies like DeepMind, OpenAI, and Anthropic. We came together to build this company that designs, co-designs research and product to build super intelligence. I think that super intelligence can sound like a very abstract thing, and I think what makes it special doing this at a startup or a smaller place is that you can be very concrete in what that means to you.
Because I think that generally when people think about super intelligence, they might think of something that becomes really good at math, you know, like olympiads or code olympiads or competitive coding, things like this. But these things to us don't really, I mean, they're impressive, but maybe not so, it's unclear how they're useful. Like what is this super intelligence doing that is useful for kind of an end user? But if you co-design kind of a product and the research alongside it, you can be much more opinionated about where it is that you want to go.
And after talking to a lot of organizations and enterprise customers after we started the company, we realized that probably the form factor of a kind of organizational super intelligence, like the thing that's really going to help organizations get a lot of stuff done, is probably going to be something like an oracle. Like an oracle that understands the entire organization extremely deeply, that can answer questions at, you know, the level of, let's say, the seniormost person on that team, right? It kind of has that, like a principal level engineer or like the senior most sales leader who has like full context on the company. And it'll probably be super intelligent also in the sense that it's doing all those things at once, right, as opposed to having like these distinct different functions. And so that is what we think an organizational super intelligence is going to look like, that it's going to be a system that really deeply comprehends the organization.
Matt 4:15 ↗
It's a great term, organizational super intelligence, as opposed to the super abstract concept of super intelligence. Just to say for a second on the concept itself, super intelligence, does the industry actually agree on what that means versus AGI? So, you know, we're recording this. Obviously, the big news is our friend Zuckerberg showering top researchers with extraordinary amounts of money and poaching them from various organizations to create a super intelligence lab, and then this, you know, Safe Superintelligence as a startup. Do people agree on what that means, or is that just more like something that directionally feels very impressive, but not everybody exactly knows what that means?
Misha Laskin 4:56 ↗
You know, I would actually say that super intelligence in these contexts of the large lab context is actually just being used synonymously with what AGI used to be used for. There's a scene in Indiana Jones and the Raiders of the Lost Ark, the first scene where he goes and tries to steal a sculpture, and he kind of takes a sculpture and replaces it with a sandbag and hopes that nothing changes. And I kind of think one of those...
Matt 5:18 ↗
That scene does not end well, if I remember correctly.
Misha Laskin 5:20 ↗
It doesn't end well, but you know, that's...
Matt 5:21 ↗
But the analogy stops here.
Misha Laskin 5:23 ↗
Yeah, the analogy stops here unless we really figure out safety. But I think that what happened is that by many accounts, you know, many people would argue that AGI hasn't been achieved, but now some people might argue that AGI has. And so it's kind of, it's unclear that this is a binary event that hasn't been achieved yet, even though that was the case before. And so I think the goalpost just moved like, oh, what I meant by AGI was actually super intelligence. So I think that that is to say that it's as vaguely defined as AGI was before, and I don't think anyone actually, that there was any agreement on what we actually meant by AGI.
Matt 5:58 ↗
Okay. I mean, it does sound cool though. 2025 super intelligence is a 2024 AGI. Okay. All right. Yeah. So coming back, I really like that term of organizational super intelligence. It does sound more tractable in your analogy of what a senior person would know, especially, I assume, a senior person that actually does the work, right? Because typically the most senior people in an organization are actually disconnected from the reality of what happens in the troops.
Misha Laskin 6:23 ↗
Yeah, I think it's more, yeah, the person who, there's on every team, there's a go-to seasoned, experienced person who's very much in the weeds and understands everything. Getting systems first that are like that, and then they can hold a lot more context in their heads and sort of be even better than those, you know, critical, you know, kind of members of the team. I think that's kind of like an oracle for an organization. That's what a super intelligence looks like, because once you deeply understand the problems that you need to solve in any discipline in an enterprise, acting upon them to actually go and solve it is the easy part.
And so we're really focused on coding to start for a number of reasons. We kind of think you solve this problem, it sort of solves the more general problem.
Matt 7:09 ↗
Yeah. What are those reasons?
Misha Laskin 7:11 ↗
There's one reason is that the way, you know, today we think of coding as just for software engineers. But when you build a coding model, you've just trained a language model that can interact with a piece of software through code. And so the way these language models are going to interact with any piece of software, not just software engineering software like Salesforce and other CRM and creative tools and so forth, the majority of those interactions are going to be through function calls, API, so through code. So today we think of coding model as something that is just for software engineers. But that's not true. If you build that system, it can actually interface with any piece of software. It's sort of what you've built is kind of the hands and legs of a digital AI, right? In the same way that a humanoid robotics robot can do anything with the same hands and legs that humans do.
Matt 7:55 ↗
So would coding be the brain and then everything else becomes the legs and the hands that are connected to the brain? Is that, was that the wrong analogy?
Misha Laskin 8:04 ↗
Yes. It's kind of like you can kind of think of the model as the brain and then what people call a scaffolding agent, scaffolding. That's sort of the affordances, right? The things that you can actually do. All these affordances for software, at least, you know, for digital intelligence, are going to be primarily through code. The other option is teaching a model how to drag a mouse around, and it's called computer control. Some of that will happen, but I just don't think that that's going to be the majority in which, you know, a language model interacts with software. So if you solve coding, you've just solved how does a language model, how should it interact with software.
Matt 8:35 ↗
And also it's a more tractable problem. Is that fair? Because code is more structured and code is closer to grammar, lends itself well to, you know, the type of work LLMs do? Or is that...
Misha Laskin 8:48 ↗
No, I think that's very much correct. It's more that code is almost, it's kind of intuitive to LLM because they were trained on the internet initially, and so they kind of have almost a muscle memory for code. It's kind of like humans have evolved to have spatial, you know, geospatial muscle memory, and so we learn very quickly how to use our hands and so forth as toddlers. Code is actually very unintuitive to us, right? That's why the GUI was invented, because the first way to interface with computers was through code, very unintuitive for humans. So you invent the GUI. For language models, it's the opposite. They've never seen any GUI data really on the internet. Like there's no mouse movement data out there. So the thing that is native to them is the exact opposite of what's native to us. So if you build things that are really good at coding, you're sort of just amplifying like the existing sort of base knowledge of the LLM, like you kind of, it's just intuitive to a language model.
Matt 9:45 ↗
Mm-hmm.
Misha Laskin 9:45 ↗
So that's why coding. But then, you know, within coding, you can kind of think about what it would take to create a super intelligent coding agent. You basically need a system that can generate code really well, and you need a system that comprehends large code bases and all the knowledge around them, like everything that's in all the docs and the stuff that's kind of tribal knowledge that's in engineers' heads. And where I'd say every coding tool today is focused on the code generation piece in an autonomous, semi-autonomous, in your IDE, in your terminal, but it's all around code generation.
And as a result, because companies today, I don't think, are really focused in earnest on the understanding piece. What we're building towards, I'd kind of call as almost, you know, today maybe we have AI engineers that are at the level of an L4 engineer, maybe next year L5, L6, going to L9. I think the path there is clear, and what we're going to get to if we don't solve the comprehension piece is basically L9 engineers with amnesia.
Matt 10:47 ↗
So an L9 engineer, if they came into your company but had amnesia, yeah.
Misha Laskin 10:50 ↗
They wouldn't be really...
Matt 10:51 ↗
Good news and bad news.
Misha Laskin 10:52 ↗
Right, right. It's kind of, if you tell me exactly what to do, I'll go do it really well, but otherwise, you know, like I know nothing about your code base, I know nothing about your organization, and I'm not going to gather any of that either. The thing to solve now, I think, is...
Building what we kind of think of as the context engine. Like what's the thing that's kind of brain that your coding agents can query in order to have all the context that they need to go do, you know, meaningful work, not just junior engineering work, but the stuff that engineers spend really most of their time on, like critical infrastructure bugs, dealing with legacy code, like things that, you know, if you actually hover over a shoulder of an engineer at any large organization or even a startup with a really sizable code base, and you look at what they do, you'll find that a minority of their time is actually spent coding. Like 70% of their time, they're digging basically through information, trying to understand stuff, asking other engineers questions.
Matt 11:54 ↗
And you kind of want to build a super intelligence that has the same DNA, that, you know, what it's spending most of its time on is collecting information, and then obviously once it has it, it knows how to act on it. How is that different or similar to basically doing a combination of coding and RAG and RAG to bring in the context of the enterprise?
Misha Laskin 12:18 ↗
Yeah.
Matt 12:18 ↗
Is that the general direction?
Misha Laskin 12:20 ↗
It's kind of, maybe it's almost like if RAG worked. So the purpose of RAG is to get all the information that your coding agent needs in order to do some work. But it's a very primitive form of doing this and by and large fails. It's kind of, I mean...
Matt 12:37 ↗
Why is it primitive?
Misha Laskin 12:38 ↗
Uh...
Matt 12:39 ↗
Because it's just search oriented. It's just a query or...
Misha Laskin 12:42 ↗
It's more, so there are a few things about it, but the first thing is that it's kind of what we call sparse because it's the stuff that it grabs from, you know, a large code base has a lot of false negatives and false positives. So it's kind of, and it typically only does it once, right? It'll grab it and then that's all you have. And most likely for any meaningful query, it will not have given you the information that you need to actually go do the task. So RAG agents are actually pretty weak.
What's happening now is that there's kind of a new kind of retrieval that I think people are calling agentic search, which is more what Claude Code does. And it's kind of an agent that uses the same kind of command line that a human does and goes and kind of looks for files and, you know, uses the same commands that an engineer does to go look for files and, you know, search for keywords and grab stuff, and it does this agentically. So as opposed to it just being a one-step process where it just pulls a bunch of embeddings in, it will use a file search tool and then it'll look at the stuff that it did and think about it and then use another tool and so forth.
Matt 13:46 ↗
And will remember it. Is there a concept of a memory built in?
Misha Laskin 13:49 ↗
It does store the stuff in a context. But the way I would think about it is that imagine you are dropped into a large dark jungle and all you have is like a tiny flashlight. That's basically what agentic search is today, where you're going and you're kind of exploring and you have this tiny flashlight and you have to then remember everything in your head. And obviously that's a first form of comprehension, but it's also a pretty weak form of comprehension. It doesn't really, it doesn't scale to large jungles.
Matt 14:20 ↗
Like if you have like a little tiny jungle in your backyard, then you might be able to navigate it.
Misha Laskin 14:24 ↗
A bonsai jungle.
Matt 14:25 ↗
A bonsai jungle. Yeah.
Misha Laskin 14:26 ↗
So that's kind of how I would liken the existing state-of-the-art agentic search. Whereas the kinds of systems that you need to build are ones that will basically expand the kind of lens, like the aperture of your beam, so you're seeing more, are smarter about where they go and look for stuff, how they remember it. These are basically, you know, fundamental kind of research problems, you know, like memory, long context reasoning is, you know, what people call it, but I would say it's just expanding the aperture of your beam, figuring out how to actually store it, and also what sources of information should you be pulling on other than just your code, because information for organizations lives in their chats and their project management tools, and a lot of it is in their team's just brains, right? So oftentimes when that senior engineer leaves who understands some legacy piece of code, all of a sudden that becomes known as a haunted graveyard because no one else understands it.
And so how do you build products that capture that knowledge that's in people's heads? That's why I kind of think that, you know, you can't, it's so hard to think about super intelligence in the abstract because half of it is a product problem. The comprehension problem is sort of, I would say, deep. And what people used to say, like when a problem was AGI complete, it just meant that the problem has so much depth to it that if you solve it, you get AGI. I would say this is a super intelligence complete problem. Like if you really solve this Oracle for organizations just for coding, you've basically built all the capabilities you need to have super intelligence.
Matt 16:02 ↗
Because you can generalize from there. It's an idea that certainly made the rounds, by the way, that coding is a path to super intelligence. I think a variation of that idea has been that, you know, it's intelligence building intelligence, doing it automatically, which I think feels like a different avenue. But what you're saying here, or maybe not, but I think, but what you're saying here is more that it's such a complex problem that if you solve that problem, then you're there. I mean, just to play back what you just said.
Misha Laskin 16:37 ↗
Yeah. I think that the notion of, in the sense in which coding is ASI complete, is that you can use an intelligent coding system to build another intelligent coding system. If people like to do research in the abstract, that sounds awesome because it's kind of like, it's like, I don't have to think about the actual problem that's being solved. If I just build an intelligence that builds an intelligence, it will figure it out somehow. I don't think that's how it works.
So I think what I think coding intelligence that builds better coding intelligence will make algorithms more efficient, basically, you know, and maybe it's so intelligent that it can even start making all the product decisions for you in terms of like what questions you should be asking users and what features you should be building. And to me, it actually seems like a much larger, more practical problem that it's, there's almost no, I think, research without co-designing product with it is sort of, it's sort of a meaningless pursuit now, but that was only meaningful when the ingredients for how to build artificial general intelligence or ASI were not known. I think now they're known, and so...
Matt 17:39 ↗
So you think that we have everything, and maybe list what everything is in terms of components.
Misha Laskin 17:45 ↗
Yeah, I think we have everything, even though the capabilities will continue being tightened, but the sort of series of breakthroughs that need to happen, many of them have happened. There are still some, but I would say that the ones that come to mind, and I'd say there are four of them. The first ones were just making deep neural networks work. So that was just the ImageNet moment in 2012 when you can have a deep neural network that's classifying images at human and then superhuman level. I think that was the first breakthrough.
Second breakthrough was reinforcement learning, even though I think it was not clear maybe then, but now it's clear again. So reinforcement learning basically told us how do we take a system and if we have a reward, make it super intelligent. And we actually, super intelligence has been built a few times now. AlphaGo was super intelligent. AlphaStar was, if you put more compute into it, it would have gotten super intelligent. So we've known how to build narrow super intelligence for a while. So deep neural networks, reinforcement learning.
Matt 18:45 ↗
So 2012, AlphaGo was 2016 or 2016. Okay.
Misha Laskin 18:50 ↗
Then scaling up transformers, the GPT series of work.
Matt 18:53 ↗
2017, 18.
Misha Laskin 18:55 ↗
Kind of 18, but then leading really, I think, started shining in like the, in early 2020s with GPT-3, and that was both an architectural innovation and a data innovation. It was an architecture that could consume data on the internet, so it's kind of both hand in hand. Transformers are not just architecture, it was also data. And then I would say the last ones are RLHF, which was, okay, we know how to align models in the basic way, we know how to do basic reinforcement learning on top of language models.
Matt 19:22 ↗
Mm-hmm.
Misha Laskin 19:23 ↗
And then reinforcement learning coming back again with the reasoning models.
Matt 19:26 ↗
So if I was to, you know, summarize, I would say neural networks, deep, deep neural networks, transformers and internet-scale data and reinforcement learning in kind of its various incarnations. These are the ingredients that are required to build a super intelligence. And as a return of reinforcement learning at the end that you described, does that obviate the need for RLHF? Was that a temporary solution or are those parallel capabilities?
Misha Laskin 19:53 ↗
I think they're parallel capabilities because they do different things. RLHF was more, the design there was more to align a language model, like a pre-trained language model. If you play with one of these base models before they're aligned, they're really useless. They're, they are, they feel like stochastic parrots. They're, yeah, they don't follow instructions. They're extremely kind of high entropy, right? And...
The fact that you could just align them, tweak them to align them with something that is human consumable, I think was a pretty big breakthrough, and that was RLHF. Whereas RL with reasoning is more RL to drive kind of intelligence capabilities, which is, you know, make it really good at coding, make it really good at math, make it really good at whatever target domain that you have rewards for. And you use these in tandem where like RL in kind of the reasoning phase that sort of really expands on a capability, and then RLHF aligns it to be kind of human consumable.
And, but they're the same thing. It's a, it's in fact, I would say it's just, it's just the same thing. Like the machinery is the same.
Matt 20:55 ↗
So we have all the components for AGI, ASI. Your goal is to create this in an organizational enterprise context. And I guess let's get into the big news of this week, which is that you're launching your first product.
Tell us everything about it.
Misha Laskin 21:14 ↗
Yeah, we're launching our first product and the first milestone on the path to super intelligence. It's called Asimov, like the science fiction writer who had some thoughts on the subject. And this Asimov is the best-in-class code research agent built for organizations. So it's different than a coding agent, which is a thing that will go and write code for you, but that today we feel are pretty context poor.
So you have to, if the task is well scoped, coding agents today will do it pretty well for you. If you are spending, you know, most of your time trying to understand like some hairy problem in your engineering, why some infrastructure bug is happening, or really doing what engineers spend most of their time doing, which is this kind of work, there's no tool today that really unblocks them in that way. And so there's, I'd say, 70% of doing software engineering is actually, it's a code research job rather than a code monkey job. And we're building a product that addresses that problem. So the majority of time that engineers spend unpacking problems and trying to understand why something's happening, and, you know, oftentimes it's bottlenecked because they have to ask someone a question and it takes a few hours for that person to get back because they're busy. We've built a product that helps overcome these kinds of problems.
Matt 22:38 ↗
So just to play it back, like deep research for code. It's very similar in the concept to like a deep research for code. Yeah. A thing that will go, you know, explore your codebase and other sources of knowledge. It might take a bit longer than the traditional kind of snappy ask kind of products.
Misha Laskin 22:55 ↗
But it'll come back with much better answers. Things that kind of make it different are that, well, one, engineering knowledge does not just live in a codebase. It lives in all sorts of other surface areas and other software products like project management tools, chats, documentation, like things like this. And Asimov pulls from those things. So it's not just your codebase, it's aggregating all these sorts of information.
It has this new concept that I don't think has been introduced to date that we call team-wide memories. So today products have individual memories, which are remembering the personal preferences of the developer, but they don't have a team-wide organizational understanding. Like suppose you have a senior software engineer that understands some microservice, and you're not that engineer, and now you need to interact with their microservice and you don't have the context they do.
Matt 23:44 ↗
So now with Asimov, it kind of organically captures that information as it happens in chats, but also engineers can just teach it directly. Yeah, that's super cool. And then that addresses the problem you mentioned, I think, at some point earlier, which is like if somebody leaves, then the institutional memory goes with them. So you have like permanent organization-wide memory.
Misha Laskin 24:02 ↗
Exactly. It's kind of building a permanent organizational system of record for your engineering knowledge to start.
Yeah. A side note on that is something that's been interesting is that some of the most excited users have been these senior, you know, senior staff kind of level engineers who are fielding people's questions all the time. And so what we've seen is that, you know, we'll go to an organization and the first three weeks, there'll be four kind of staff, senior staff level engineers who are just populating its knowledge.
To kind of, it's kind of the first time I've actually ever seen engineers excited about documentation, effectively.
That's kind of a unique thing. And then the final thing is really around agent design that enables you to kind of what I was calling earlier, increase the aperture of your beam so that it's kind of looking at much larger code bases than agents were able to before. This is still a work, you know, in that sense, a work in progress in that long context reasoning is just a big fundamental problem. And I think there's a lot of work to be done there, but I think this is, this new agent design is a step in that direction.
Matt 25:10 ↗
Directionally, why and how are they able to do that?
Misha Laskin 25:15 ↗
This is not unique to us. I think that when I look at how state-of-the-art agents are being designed, they're being designed very much in kind of as these multi-agent systems. Agent design is effectively, it's a big reasoning agent, and that's, I mean, I think that's pretty standard, but it dispatches like small long context reasoning agents to go and kind of go search for different parts of kind of relevant chunks of information in the code. And so I think that it's this kind of decoupling of, you know, a big reasoning agent, like maybe a smaller context with a bunch of like these little retriever scout agents. It's a different design than what's happened to date, though I'm sure that other companies will converge on it as well.
You really want to design your agents for the problems that you're trying to solve. So if you want like a really snappy agent that's going to answer things immediately, then this is probably not the best design for it, right? You might want something that does RAG, which is very fast, or like a very basic search agent, kind of like what Claude Code or Cursor might do, which is something that just uses the terminal and like the file system there and use the same commands as an engineer. That's a lot snappier than sending a lot of these retrievers out. So I think what we'll start seeing is this is product co-evolving with the problems that you're solving, and there will be different agent designs for different problems.
Matt 26:32 ↗
And is a sort of like snappy one-shot agent necessarily a bad thing if you direct them at small problems and then you try to put them together, or does the sort of individual little agent need to be smarter?
Misha Laskin 26:45 ↗
No, I think that it's a really interesting question. And this is kind of one of the things that's interesting at research now, as opposed to before, is that before it used to be just around models. But now a lot of the research is in your agent design. And so what you ask is kind of an open question. You could, there could be a hybrid system that kind of routes some queries to one agent, you know, to one agentic system, and then routes like other queries to another agentic system. It could be that you figured out some elegant, simpler kind of multi-agent system that can do both things. It's kind of an open research question. It's very exciting, and in some sense, it parallels a lot of the unspoken research that was happening at DeepMind and probably in OpenAI as well during like pre-language models.
For example, projects like OpenAI's Dota 5 or DeepMind's AlphaStar project, which trained these expert-level agents to play pretty complex video games like StarCraft and Dota. A big question there that I don't think that many people appreciated is how do you design the environment for your neural network to actually dispatch actions, right? So the most simple thing you can think of is, well, it learns to use a keyboard and mouse like a human does. That turned out not to work. So when you read the AlphaStar paper, you see that they actually figured out this particular way of factoring out the actions in order to make neural networks play StarCraft.
And what that actually meant is that that was agent design. That's sort of, so now agent design is back in terms of designing scaffolding. Back then it used to be called environment design.
But it's the same thing. And a lot of the project was in these big projects was not even on training the models. It was figuring out how the agent should actually interface with the environment that you're training it in, and where do you get your data from? What's your data? How do you collect it?
Matt 28:44 ↗
Mm-hmm.
So on that point, so you had mentioned the three things like multi-agent design. Like I think that the first point was what sources of data it accesses. So is there, to what you just said, is there some difference in how those agents access data versus RAG, which is pretty much like straight up search?
I guess as a side question or related question, do those data sources need to have a special protocol to lend themselves to agents or like MCP-style kind of infra so that the super intelligent agents that go around and sort of grab information everywhere can interact with them?

68 more exchanges in this transcript

Sign in free to read the rest of this interview. No card required.

Sign in to read the full transcript

Cite this transcript

APA, MLA, BibTeX
APA

Laskin, M. (2025, July 17). Ex‑DeepMind Researcher Misha Laskin on Enterprise Super‑Intelligence | Reflection AI [Interview transcript]. The MAD Podcast with Matt Turck. CEOInterviews.AI. https://ceointerviews.ai/interview/3071996/

MLA

Misha Laskin. "Ex‑DeepMind Researcher Misha Laskin on Enterprise Super‑Intelligence | Reflection AI." The MAD Podcast with Matt Turck, 17 Jul. 2025. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/3071996/.

BibTeX
@misc{laskin2025_3071996,
  author       = {Misha Laskin},
  title        = {Ex‑DeepMind Researcher Misha Laskin on Enterprise Super‑Intelligence | Reflection AI},
  howpublished = {Interview transcript, The MAD Podcast with Matt Turck. CEOInterviews.AI},
  year         = {2025},
  month        = {jul},
  url          = {https://ceointerviews.ai/interview/3071996/},
  note         = {Speaker-attributed transcript with timestamps}
}