Aaron Levie talking to Casey Newton about what kind of jobs he expects in the future dominated by AI coding assistants.
Newton: It’s the sort of thing I love to hear. I would love to not live through a massive disruption where we see super high unemployment. I also can’t help but note we saw almost 46,000 tech layoffs announced in March alone, with AI sometimes cited as a potential cause. So would you put a number to it? On the software engineering front, do you think in three years we have about as many software engineers as we have today, or more? Or do you think there’s a bigger shift?
Levie: I think we’re going to have more. I don’t want to be unsympathetic to people who really will face these changes. But big picture: if you were a CS grad of the past two decades from a top 25-to-50 CS school, by and large you were trying to go to a tech company — in Silicon Valley or a couple other places. So most of the software talent in the world of this cohort ended up building software for consumers. We were building ad apps, ride-sharing, enterprise software (thank God). We’ve accumulated a lot of engineers on that kind of work, and some of those companies have over-hired.
Who’s the loser of that equation? Every other company on the planet, because they couldn’t compete with Google and Facebook and Microsoft for that top engineer. They couldn’t automate things in the life sciences process, or the supply chain, or automotive AI systems. I don’t know how much software you’ve used from companies that aren’t in the Valley, but if you log into your bank and you’re happy, you’re a totally rare person. If you look at most car console designs of any car that’s not from two companies, you can imagine how unusable these systems are. That correlates to the fact that those companies couldn’t overstaff with all the top engineers and designers.
Now what happens? All of a sudden, what was maybe a 30- or 50-engineer problem previously, Claude Code and Codex come in, and now it’s a 5- or 10-engineer problem. For the first time ever, those companies are able to take on work that wasn’t possible before. They can bring automation to all the systems and workflows they couldn’t have afforded or justified.
So in some cases of tech, you’ll see a temporary dislocation. At the exact same time, the thing you should be tracking is the number of engineering jobs opening up at traditionally non-Silicon Valley tech companies — small businesses, consulting firms, life sciences, manufacturing.
And as a force multiplier, you’re going to have a number of new types of engineering jobs where the job is entirely about how to deploy agents inside the firm to automate work. I did this for fun just to make sure I wasn’t full of shit. If you go to the Eli Lilly careers page, as one does, they have this job title called “lab automation software adviser.” That person is an engineer whose job it is to bring automation through AI to the lab process.
Think about how many hundreds of thousands or millions of jobs will look like that in the future. My job is to take the innovation coming from AI-land and apply it to this particular business process in my organization. You’re kind of like an FDE — a forward-deployed engineer — but for that company. Those will be the people who would have gone to Meta or Google five years ago. They’re going to now work in pharma, banking, manufacturing. And those are actually incredibly stimulating jobs. You’re not just building an app, you’re automating drug discovery.
For the sake of my career continuity, I really hope that these forward deployed engineers come from Indian IT industry.
You must be logged in to post a comment.