39% of Engineering Skills Will Shift by 2030. The Definition of 'Adaptable' Hasn't.

39% of workers' core skills will change by 2030, according to the World Economic Forum's 2025 Future of Jobs Report, and tech, media, and telecom employers report the fastest pace of skill turnover anywhere in the labor market. Engineers entering the field in 2026 are being told to "be adaptable." Three researchers and practitioners interviewed by IEEE Spectrum say no one has agreed on what that means.

How steep is the skill shift?

The 39% figure covers the entire economy. The WEF draws on employer surveys across sectors. PwC's June 2026 AI Job Barometer narrows the picture to technology, media, and telecom, the industries where required skills are shifting fastest.

Software developers sit at the sharp end. A July 2026 Guardian analysis identified the role as one of the most exposed to AI-driven change. Software engineers now face a significant increase in code review, according to Microsoft research scientist Jenna Butler, who studies developer productivity and well-being.

Butler frames the moment as a paradigm shift. "I think we're still in this in-between, difficult period that we've seen before, but [it] is maybe moving faster than it has historically," Butler said. She describes the period as "the uncomfortable middle."

The lack of consensus is visible inside teams. "If you ask 20 developers, you get 23 different ways of working with it. Everyone is trying to sort it out," Butler said.

Why has "be adaptable" become empty advice?

Samantha Brunhaver, an associate professor of engineering at Arizona State University in Tempe, has spent six years on the question. She received a National Science Foundation award in 2020 to study workplace adaptability among young engineers. She has since interviewed engineering managers, early-career employees, and undergraduates.

Her conclusion: every manager wants the trait; nobody defines it the same way. "Managers are all saying adaptability is important," Brunhaver said, "but defining it in different ways."

Her working definition is short. Adaptability is "the ability to recognize that a change or uncertainty is occurring, and then respond effectively to that change." The skill is context-dependent. In software, it can mean absorbing daily turnover in tools. In aerospace or biomedical engineering, it can mean tracking shifting procedures and regulations.

The advice has a direct cost. "We tell engineers that they need to be adaptable when they graduate, but we don't actually explain what that means, demonstrate what that looks like, [or] help make sure that they're developing it," Brunhaver said.

How do you actually build it?

Brunhaver's three-step framework:

• Perceive a need to adapt.
• Evaluate your options.
• Act.

Before graduation, the work happens in classrooms and internships. Brunhaver recommends stacking real-world experiences — internships, team-based projects, community service, leadership roles. Each setting forces students to adjust to different constraints.

Reflection matters as much as exposure. "In order to adapt, you have to think that you have agency and the ability to get through a situation," Brunhaver said.

Inside the workforce, the surface of the work is shifting. Butler expects software engineering to lean more on prompting models and managing agents than on writing code line by line. The implication for hiring is direct.

"I think people who went into software because they like solving problems are going to have a lot of fun, and people who just enjoy the art of writing code are not," Butler said.

Has the engineering job actually changed?

Andy Hunt, a software developer who coauthored The Pragmatic Programmer (Addison-Wesley Professional) in 1999, says no. The book outlines practical coding principles and has been taught in many computer science classrooms. Hunt revisited it for the 20th anniversary edition. Seven years later, his view has not shifted.

"The fundamental part of the job is problem solving and communication, and that's always going to be there," Hunt said.

Hunt pushes back against language-based identity. Calling yourself a Java programmer is, he said, "like a carpenter saying, 'I'm a hammer user,' or 'I specialize in cordless drills.'"

He blames hiring filters that scan résumés for keywords and years of experience. The filters reward specialists and punish generalists. Employers, he argued, should recognize that "the tech's not the hard part, and it never has been. Understanding information theory, understanding systems thinking, understanding what constraints you're up to — that's still the hard part."

Who pays for the learning time?

The bill lands on three groups. Universities must teach adaptability explicitly. Employers must fund the time. Engineers must claim the space.

Brunhaver's prescription for universities is plain. "We need to be more explicit about what [adaptability] means and why it's important," she said. Managers, she added, should invest in professional development.

Butler's prescription is more specific. Reserve one hour per week for learning, with no expectation of code output. "I realize that's difficult," Butler said. "I would encourage people to do it on their own, but I would really encourage organizations and leaders to do it, because you're not going to get this sudden change in your people if they don't have time and space to learn how to work differently."

The pressure to skip that step is real. AI has accelerated the demand for productivity. Engineers who pause to learn new tools fall behind peers shipping code with AI assistance. A July 2025 paper on arXiv (2507.21280) documents developers doubling down on familiar tools under productivity pressure and burning out.

What should engineering leaders do next?

"I do imagine the next number of years could be challenging," Butler said. The reshuffle touches hiring pipelines, university curricula, and the daily structure of engineering work.

Butler pushes back against a passive read of adaptability. "Being adaptable sort of implies that you're going to change based on what's happening around you, and I would really like people to realize the change that's happening is somewhat up to us," she said.

Engineers choose which models they adopt and how they use them. "We need to be adaptable and go with the flow to a degree, but we also need to be directing that flow. The future with AI is absolutely not predetermined," Butler said.

For team leaders rewriting job descriptions today, the math is direct. If 39% of core skills shift by 2030, the engineers who adapt fastest are the ones whose managers protect learning time now. The definition of "adaptable" is still up for grabs — but the budget for it is not.