CEOInterviews.AI
Start App
Brian Schimpf
Cofounder, Anduril Industries

Behind the $61 Billion Startup Building AI Weapons for the Pentagon | Term Sheet

📅 Oct 12, 2026 Fortune Magazine 51 MIN 1518 VIEWS 97 SEGMENTS · 2 SPEAKERS
Can the U.S. replenish weapons stockpiles fast enough for modern conflicts? Fortune’s Allie Garfinkle sits down with Anduril CEO Brian Schimpf to discuss weapons production, the challenges of scaling manufacturing, and the testing needed to make complex systems reliable in the field. They also explore AI’s role in defense, lethal autonomous weapons, and why Schimpf says human commanders must remain accountable for decisions to use force. 00:00 Anduril’s Bet on Building Weapons Faster 05:28 The Leadership Trait Schimpf Values Most 10:57 Why Founders Need to Empower Great Talent 16:25 How...

What Brian Schimpf said

Written from the verified transcript and checked against it. Every figure links to the moment it was said.

Brian Schimpf, cofounder and CEO of Anduril Industries, discussed his personal identity as a builder, his management philosophy emphasizing self-honesty and creative sparks over conventional praise, and his views on AI's role in defense. He argued that lethal autonomous weapons are often misunderstood, noting the U.S. has long used bounded autonomous systems like torpedoes and anti-radiation weapons. He said AI improves precision and decision-making but keeps humans accountable. He addressed Anduril's unprofitability, attributing it to rapid growth and upfront costs, and criticized high valuations in defense startups. He discussed lessons from Ukraine and Iran, including the strain on munitions production and the shift toward targeting economic infrastructure. He also touched on the difficulty of deterring China and his belief in systemic forces over individual greatness.

Key takeaways

  1. Anduril's revenue has grown over 100% per year for several years, but the company is not yet profitable due to high growth costs.
  2. Schimpf said Anduril has never maxed out pricing in any funding round and could raise valuation by 30% to 100% if it wanted.
  3. He claimed the U.S. consumed 'a decade of Tomahawk production in three days' during recent conflicts, highlighting munitions production struggles.
  4. Schimpf said product managers at Anduril are writing 80% of code via Claude Code, a significant shift from a year ago.
  5. He noted that in a recent live fire test in Taiwan, Anduril achieved about a 95% success rate with its products.

Numbers and commitments

FigureWhat it refers toTypeAt
over 100% per year Anduril's revenue growth rate for several years metric 25:05
30% to 100% potential increase in Anduril's valuation if it chose to max out pricing other 26:31
80% portion of code written by product managers using Claude Code metric 13:03
95% success rate in a live fire test in Taiwan metric 34:33
50, 60% washout rate for senior roles at Anduril metric 6:28
12 to 24 months lead time before factories produce useful outputs other 25:14
six to 12 months time for new hires to become productive other 25:14
90, 95% share of returns captured by top two winners in disruptive spaces other 29:54

Chapters

  1. 0:00Personal identity and management philosophy
  2. 13:03AI's role and misconceptions
  3. 18:37Autonomous weapons and precision
  4. 23:11Anduril as an engineering problem
  5. 25:05Profitability and valuation
  6. 31:05Test site economics and product development
  7. 40:42Deterrence and economic infrastructure
  8. 46:35China and holistic national security
  9. 49:17Great man theory and future trends

Questions asked in this interview

12
  1. 0:28So I sat with CEO Brian Schimpf to find out: when the next war comes, can a startup build America's weapons fast enough?
  2. 1:59... to the beginning of your career, because you previously were head of engineering at Palantir, and very early on, you told me a story about how it wasn't exactly intentional that you became an engineer in the first place. How did it happen?
  3. 3:40We were talking about management. Can I curse here?
  4. 6:22How do you screen for that kind of self-honesty, especially when you're hiring, when you only have so much information about somebody?
  5. 7:30You know, what is the most extreme situation that you've tolerated because someone was brilliant, and how did you manage it?
  6. 12:48You know, what do you think actually is the biggest misconception about AI right now?
  7. 16:11I was gonna say, do you think AI will create or take jobs in defense?
  8. 18:45Do you think people understand that?
  9. 24:53What kind of story is that path to profitability?
  10. 34:22For our audience, what actually happened?
  11. 37:02Does it comfort you? Does it haunt you?
  12. 46:22When you think about this new model of deterrence and what we've learned from the conflicts in Iran and Ukraine, how does that transpose onto a potential conflict with China?
Brian Schimpf 0:01 ↗
People get nervous around the idea of lethal autonomous weapons. The reality is, the U.S. has...
Allie Garfinkle 0:05 ↗
The killer robots have to kill robots. Yeah, people are very scared of that. I'm here to tell you...
Brian Schimpf 0:09 ↗
...incorrectly. Like if it's done in a completely insane way, it would be a very bad idea.
Allie Garfinkle 0:14 ↗
Today, just five companies build almost all of America's weapons, and modern wars have shown that we are depleting U.S. munitions faster than we can build...
Brian Schimpf 0:22 ↗
...them. The volume of weapons that these modern conflicts are consuming is so high.
Allie Garfinkle 0:28 ↗
Anduril, a $61 billion venture-backed company, disrupted the traditional path, gambling its own capital to build AI-powered weapons and software, bringing Silicon Valley speed to the Pentagon. Its revenue is doubling year over year, and the company has billions in contracts with the Army, Navy, and Air Force. So I sat with CEO Brian Schimpf to find out: when the next war comes, can a startup build America's weapons fast enough? I'm Allie Garfinkle, and this is Term Sheet. So Brian,
Brian Schimpf 1:00 ↗
Hello.
Allie Garfinkle 1:00 ↗
Hello, hi. You and I spent many hours together as I was working on the profile of you that is now in this. This is your face.
Brian Schimpf 1:12 ↗
Pretty cool.
Allie Garfinkle 1:12 ↗
Pretty cool. Yeah. So we spent a lot of hours together. One thing I really noticed is that you are much more comfortable talking about ideas than talking about yourself. So I wanted to blast right past that right at the beginning. Now, existentially, spiritually, whichever way you decide to take it, who are you?
Brian Schimpf 1:29 ↗
So I think of myself as like, you know, I got two little girls, so I'm a dad. I love that. I've always wanted to be a dad. I love that part of my life. And you know, I just think of myself as a builder. I just like to build things. Kind of doesn't matter what. Like I've been doing it since I've been, you know, a little kid, since I've been like five, and just always building something. And it's just curious and wanna just make something. Like that's just who I am. Sometimes it's a physical thing because I'm an engineer. Sometimes it's organizations, just whatever it is.
Allie Garfinkle 1:59 ↗
But I want to go back to the beginning of your career, because you previously were head of engineering at Palantir, and very early on, you told me a story about how it wasn't exactly intentional that you became an engineer in the first place. How did it happen?
Brian Schimpf 2:13 ↗
Yeah, so you know, well, the engineering was, you know, kind of always there, but the management side was interesting. Where like, you know, I came in as a forward-deployed engineer, one of the first ones on the team.
Allie Garfinkle 2:24 ↗
Were they even calling it that then?
Brian Schimpf 2:25 ↗
Yeah, yeah, no, sure. They were actually calling it that, forward-deployed engineer, maybe like six months earlier. And you know, I was working for this guy Mike Schaffer, who I knew in college, great friend of mine. And you know, I remember just like a handful of months in, he was like, I don't really like managing. You know, more or less, you want to swap? And I was like, all right, this sounds good. I ended up turning out I liked it. I liked, you know, leading teams. I liked being able to work on a lot of these organization problems that were just, you know, kind of tricky puzzles. And how do you get people to be motivated to do the right things? It's like one thing you learn with engineers is, you know, I see a lot of people who, you know, kind of come from like a business background or whatever, and they think that if they're in charge, finally the engineers will listen to them. It's like, no, they don't listen to anyone. You have to convince them of everything, and they've got to want to do it themselves. And so just really thinking about like organizations through that lens of like the people, what are their motivations? How do you just enable them to do epic stuff? Like that's been a super interesting theme throughout, you know, everything I've been working on.
Allie Garfinkle 3:28 ↗
Now throughout this interview, we are going to be playing a game I'm calling the cutting room floor. Things that didn't make it into the story, but that I still want to bring back up to you because I think they're worth talking about.
Brian Schimpf 3:39 ↗
Yeah.
Allie Garfinkle 3:40 ↗
So here is a quote from you a few months ago. We were talking about management. Can I curse here?
Brian Schimpf 3:49 ↗
It will be bleeped. It will be bleeped. Can we...
Allie Garfinkle 3:52 ↗
Can we bleep? Yes. We have some execs here who can be really annoying, and that's okay. They're so valuable that we will just ultimately tolerate it. How do you know when someone is just that good?
Brian Schimpf 4:03 ↗
The thing I always value is that you see folks who just have this like creative spark, just have the right ideas, who are just like really driven to, you know, actually get stuff done, and that's pretty rare. So like just that creative ability. When you're building something new, I think people get confused a lot. Most people live in organizations where the company already exists, what they do already exists, and most managers, like most people, are just optimizing what was already created. This like process of creating a new thing, of, you know, defining, you know, a new business, everything has to be invented. So that invention skill is super rare. And so for what we're doing, that ability to just always be unsatisfied, really just pushing the envelope when they have an idea, it's just better than anything you can come up with. That's super rare. You can kind of tell. And for us, that's just a big part of what's made us successful. And then, how do you, you know, it's like nobody's like perfect at running a holistic organization. It's not how it works. Like, you know, there's so many dimensions to these things. The people who do really well are the ones who can be really self-honest about where they're good, where they're bad, and it's okay, right? Like, if you suck at managing people, but you're really creative, that's fine. Just defer that part to someone you can work with on it, or you're not great at operations or whatever it is. And so that self-honesty is probably the most important skill for any person to have, and then it bleeds over into an organization that is either actually reflective and self-honest and can critique itself and get better, or just has to lie to itself that it is great and everything's working. And organizations and people that lie to themselves, they don't survive very long. It just doesn't work out. And that's a big part. We've always tried to like drill in, I've always tried to drill in, where people just have to get adjusted to the fact that we don't do a lot of compliments, we don't tell you did a good job. It's mostly like what didn't work, you know, what could we do better, and then like how we're getting better next time. Like that's really all we talk about, which is really uncomfortable for a lot of people where they're used to like a reasonable degree of praise. Just not my style, not how we work, and it's once you get used to it, it's just really productive, though.
Allie Garfinkle 6:22 ↗
How do you screen for that kind of self-honesty, especially when you're hiring, when you only have so much information about somebody?
Brian Schimpf 6:28 ↗
It's pretty hard. I mean, like the washout rate in kind of senior roles is probably like 50, 60%. That sounds high. I don't know. I mean, maybe it's like actually probably accurate to what these things should be. There's always a question of like, does it fit? Not just like, are you competent, but like, do you fit with how we want to operate, your peers, your boss? You know, it's just like the whole system, and that's just impossible to screen for. The like introspection and like how they think about problems, you can tell that pretty fast. Like if you met a lot of folks, you can kind of get a sense of who is just deeply introspective and thinking about what worked, what didn't, what was their contribution, what would they have done differently. That's normally pretty easy to suss out. But then, like, are they going to be effective in our setup? Are they going to be effective for what we need? That's always just, it's so circumstantial and like actually, you know, not 100% correlated with how good they are. It's just, are they good in this context?
Allie Garfinkle 7:27 ↗
Well, I've been watching. Do you watch basketball?
Brian Schimpf 7:29 ↗
No, no. Yeah, you're not sports.
Allie Garfinkle 7:30 ↗
You're not sports. You don't do the sports ball. There is a paradigm in the NBA where someone can be great in one system and then terrible and fall apart in another. Yeah, it seems like there is a little bit of that here, yeah. You know, what is the most extreme situation that you've tolerated because someone was brilliant, and how did you manage it?
Brian Schimpf 7:48 ↗
Oh man, not gonna name names, because they're mostly still around. You know, a lot of folks were just like really creative, and maybe from a prior life, we had, you know, one person who is just like just absolutely brilliant engineer. And the challenge is always just, you know, can they get to that self-honesty and build a support structure around themselves? Can they take the help? Can they be honest about, you know, where they need somebody who's got complementary skills on management or whatever it is? And as they're going through that, it's often quite hard for the people that, you know, work with them or their peers. There's a lot of friction. There's a lot of difficulty as they like get, you know, like a lot of these people are like brilliant artists who just get offended that something's not perfect, and that causes a lot of friction and chafing with like people they work with. And that's, you know, that's what makes them great, but it also makes it hard for them to exist in these organizations. So, you know, how do you protect them, get them, you know, peace, plus get them to understand how they need to be most effective to operate, get the rest of the organization to understand like this person's brilliant in this way, you know, you're going to tolerate like these issues. Just suck it up, deal with it, because it's worth it.
Allie Garfinkle 9:06 ↗
It sounds like, it does sound like you're talking about brilliant artists. Literally, it's the same thing. High-maintenance geniuses, brilliant artists. They're...
Brian Schimpf 9:13 ↗
Really good. It's so good. And I think most organizations reject these people because it's just like, it's too hard, it's too annoying. Is it really worth it? You know, if you're changing like 5% per year as a company, or as an organization, is it worth someone who's high friction? No, right? You're like, it doesn't really matter. For you, it actually is worth it. It sounds totally worth it. Why? It's just like the rate of growth, the number of new things we're going after, the new products we're building. Like all of these require someone who's just like a brilliant artist. Like you just can't make a new product unless it's like an actual, like someone really brilliant leading it. You get very mediocre results, right? Like you don't build an airplane by consensus or committee. It's not how it works.
Allie Garfinkle 9:56 ↗
That is actually what I was going to bring up next. You actually said that to me previously, that you can't build an airplane by consensus. And I've thought about it many times because there's a theoretical dream, right, that in organizations you can all make decisions together, but actually I've come to believe that's pretty much not true for lots of things. It sounds like that's something you really don't think is true.
Brian Schimpf 10:13 ↗
There's a weird balance where you're trying to create an organization where people feel genuinely and are genuinely engaged in like their opinion matters and what they think matters, right? Like it doesn't work to just tell everyone like, you know, you just can't have an opinion on this thing. This doesn't work, right? It's like especially if you have a lot of, you know, brilliant people. So, you know, that balance of how do you create that real buy-in, get people really valuing their opinions, getting to a better outcome while still you've just got to be able to say somebody's in charge. We're moving out. They're making decisions. And I've screwed that up at different times in different ways, trying to, you know, manage the more consensus approach versus more like, you know, empowered, decisive approach. It's just genuinely hard, right? Like it's a genuinely hard balance. And, you know, these projects are always, anything we're doing is just like, you know, take the literal case of building an airplane, right? It's like, okay, well, there's like the design of the plane, but then there's like the testing program or the software approach or, you know, how we talk about it on business development or, you know, comm strategy. Each of those require a degree of like creative insight and how you're going to approach it to generate the right, you know, the right strategy for each of those dimensions. And it's just like, you know, it's not true that one person's going to be great at all of those things. So how do you create the right environment that the right experts, the right brilliant people, can just be empowered to run, and it works.
Allie Garfinkle 11:45 ↗
If you had one piece of management advice to give to the founders listening to this, what would it be?
Brian Schimpf 11:51 ↗
I think a lot of companies end up pretty thin where the founder ends up being the really like kind of brilliant artist and struggles to recognize that their job is to actually mostly just get brilliant people and, you know, empower them, right? Like that's most of what your job is. Not you being right; it's about getting the best ideas and getting the best out of people. And so the bench depth that a lot of companies actually like often ends up pretty bad, right? Where it's like the founder, the CEO, or CTO wants to be the person with all the ideas. I just think it's, if that's what you're optimizing on, if that's what you're subtly optimizing on, it goes really badly. You just can't do that much. So that ability to like really bring in and empower these brilliant artists, that's probably the number one skill. Like if you get that right, it tends to go pretty well.
Allie Garfinkle 12:48 ↗
Well, and in the age of the AI boom, I imagine there's already churn, but I imagine there's more competition for a lot of that talent too. You know, what do you think actually is the biggest misconception about AI right now?
Brian Schimpf 13:03 ↗
At least with AI today, and it's sort of hard to tell where it's going to be in a year or two, AI has terrible taste. It's like really good at thinking through like the technical details of a problem or the mechanical aspects of it, but the intuition around, you know, what's good, what's bad on any dimension. You know, it's like if this is like you're building a software product and thinking about like the right architecture or the right way this is going to operate, that taste around what is this thing and what should it be and how should it fit is often quite bad and it just doesn't have the context and it just, that's not what it's good for right now. But then you're like literally implementing the code. It's great, right? And I've kind of seen this across lots of different things. We're even seeing with internal apps, you know, product managers are writing 80% of the code via Claude Code at this point. The software engineer is thinking about how's this thing going...
Allie Garfinkle 13:55 ↗
Would you have thought that was possible a year ago?
Brian Schimpf 13:59 ↗
A year ago, no. Like it's changed dramatically. Like a year ago, the people who were getting the most out of the AI stuff, you know, talking with a bunch of different folks about this, they were a lot more of the like junior engineers, where, you know, they were already given fairly, you know, task-specific work, and it was helping them just write the code on the task work, right? Like fairly bounded stuff. Now it's like senior engineers. It's like the people who are like architects or product managers or any of these folks who are like, I know what I want this to do. I can think about what I want the outcome to be in a really high-end way and what good or bad looks like. Those people are doing incredibly well with AI right now. So it really shifted from a year ago. A year ago it was like good, but just not that impactful. Now, like, there's a reason Anthropic is taking off so much. Like how this is really manifesting in a very different way. So I think that's a big piece of it. The other piece is like, I don't think there's enough, you know, kind of honesty around, or kind of curiosity around how this is going to play out in the job market. I think it's sort of all doom and gloom. But there's going to be grades of this, right? It's like, you know, if you're a small business, it's probably in a lot of ways great for you. Where now all of a sudden you have access to world-class marketing talent, you have a finance team that's actually very good, right? Like you could start to do things that were never accessible to you before, and really amplify your reach. You know, is it going to lead to a real reflection on do we really need the, you know, marginal software engineer? Right? Can we get more efficiency? Yeah, that's going to be true. But, you know, what we're seeing is just we were always limited by the people, the rate we could hire. We had more ideas than we had bandwidth. Now that's like more unconstrained. Like that's a huge, huge difference. And so just the quality and volume of what we're going to be able to produce is just massively higher. And then the value that each person brings is going to be that much higher, right? Like we live in a world where doing more will yield more growth and a better outcome, right? Like better products, better revenue growth. For a lot of business, that's not true, right? Like if your back office is better or whatever, you know, it doesn't matter, right? Like you're still saturated in your...
Allie Garfinkle 16:11 ↗
I was gonna say, do you think AI will create or take jobs in defense?
Brian Schimpf 16:15 ↗
Create jobs, on the whole. I think the efficiency you're going to get out of people in terms of the rate you can bring new products to market, you know, the ways you can get like kind of new experimental capabilities move through to production very quickly, that's going to change dramatically. And the part I think everyone agrees is over the next five to 10 years, the world of atoms is going to do quite well. So if you're bending metal, you're making hardware, there's just going to be a resurgence in, you know, kind of manufacturing. And I think the AI is also going to have a massive benefit on the manufacturing efficiency. So that's going to yield, you know, better jobs, more jobs where it actually makes sense to manufacture in the U.S., right? And we're in a lot of these more expensive locations. So I think it's going to yield significantly more jobs into the manufacturing space. I think you're going to see the software engineers and a lot of the kind of product managers, program managers, just be wildly more efficient. They're going to be doing more valuable stuff. And I think the, you know, costs, you're going to make it easier to adopt new things, which is I think net going to drive a lot of new jobs.
Allie Garfinkle 17:32 ↗
Actually, let's go back to the cutting room floor here for a second. We were talking about AGI, I believe, on the plane to the Texas test site, which we will come back to. And the thing you said that I thought was really interesting is the part that everyone gets nervous about is self-improving systems. Once you have AI that can improve itself, you start to worry it can grow without bounds, and that's a legitimate concern. And I was thinking about this in the context of you and of Anduril. You make some of the most dangerous weapons in the world. How do you think about AGI and the possibilities around that?
Brian Schimpf 18:03 ↗
Yeah, so we don't make our own foundation models. We work with all the foundation labs, and they're great, and, you know, we have a good relationship with nearly all of them. The way we think about where AI is going to be most beneficial and sort of most ethically applied in defense, we kind of think of it in two ways. You know, one, you're going to be able to be more precise, right? So you think about, you know, people get nervous around the idea of lethal autonomous weapons. Well, the reality is the U.S. has had... the killer robots have people very scared.
Allie Garfinkle 18:33 ↗
Yeah, people are very scared of that. I'm here to tell you...
Brian Schimpf 18:37 ↗
...incorrectly. Like if it's done in a completely insane way, it would be a very bad idea. But nobody is proposing that. And...
Allie Garfinkle 18:45 ↗
Do you think people understand that?
Brian Schimpf 18:47 ↗
I don't. And I think the reality is when we think about it, it's like the U.S. has had this for a long time. In the sense of, you have a torpedo that you say, hey, in this region, in this, you know, geographic area, something matches this acoustic signature, it's a military target. Or anti-radiation weapons: if it's emitting like a radar, like a military radar, and it's in this box, that's a military target. And so we've already had this notion of like you can bound it in a way that's, you know, it's not making arbitrary decisions; it's making very narrow, very precise decisions. And I think that framework has existed for a long time. The way you test that has existed for a long time, the way you think about employing that, the policy around it. And so extending this to something that's using, you know, say computer vision instead, or taking a bunch of different sensor data, it only gets more precise and more selective and more accurate. So I think that net is going to be, you know, it's hard to make the counter argument that we should have less precise weapons. Like it's just kind of a crazy position to take. And so, you know, I think the precision side of this makes a ton of sense to me. The other dimension is on dealing with, you know, kind of fog of war, the volume of information. How do you make better decisions? And again, there's sort of an irresponsible version of this, and then a responsible version of this.
Allie Garfinkle 20:00 ↗
Walk us through both. What is the irresponsible...
Brian Schimpf 20:03 ↗
Yeah, like so, the irresponsible version of this is, you know, humans aren't in the loop. The AI is just making arbitrary decisions. Like that's a crazy position. Nobody is arguing for that. And the fundamental to the way the U.S. policy apparatus works, the way we think about this, is that you have humans be accountable for the decisions they are making. So if a commander on the battlefield employs, you know, makes a use-of-force decision, right? Like they're engaging a target or they're, you know, firing a weapon, they are accountable for what happens there. And so, you know, AI can do a lot to cross-check their assumptions, right? Like, hey, let me run through and make sure that, you know, this is, you know, definitely a military target, or cross-check every database. You know, we can kind of review the decisions that are being made. It can synthesize a huge amount of additional information so they can make those decisions faster, but, you know, kind of fully formed. Because again, today the alternative you're comparing it to is, you know, fleets of, you know, 18- to 20-year-old enlisted folks who are going through and running a fairly mechanical process. When you think about a lot of these targeting or lethal decisions that are being made, and, you know, if you're a commander, how much do you trust the repeatability of that process versus, you know, I want all the information, I want to be able to ask the questions, and I want something adversarially reviewing my decisions on this? That seems like a very responsible world to live in. And so I think that is going to have a lot of, you know, kind of benefit where the decisions that are being made, you can have a lot more confidence that they've been reviewed from multiple aspects, they've been looked at in different ways, and do it really efficiently in a much more...
Allie Garfinkle 21:44 ↗
...precise kill chain.

49 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

Schimpf, B. (2026, October 12). Behind the $61 Billion Startup Building AI Weapons for the Pentagon | Term Sheet [Interview transcript]. Fortune Magazine. CEOInterviews.AI. https://ceointerviews.ai/interview/3053107/

MLA

Brian Schimpf. "Behind the $61 Billion Startup Building AI Weapons for the Pentagon | Term Sheet." Fortune Magazine, 12 Oct. 2026. Transcript, CEOInterviews.AI, https://ceointerviews.ai/interview/3053107/.

BibTeX
@misc{schimpf2026_3053107,
  author       = {Brian Schimpf},
  title        = {Behind the $61 Billion Startup Building AI Weapons for the Pentagon | Term Sheet},
  howpublished = {Interview transcript, Fortune Magazine. CEOInterviews.AI},
  year         = {2026},
  month        = {oct},
  url          = {https://ceointerviews.ai/interview/3053107/},
  note         = {Speaker-attributed transcript with timestamps}
}