Everyone says "be adaptable" — no one says how, and your degree didn't teach it.
The Summary
- Engineers face constant change from AI tools, shifting expectations, and harder hiring, but university training doesn't actually teach adaptability
- Arizona State professor Samantha Brunhaver studied what adaptability means in practice: it's context-dependent and every employer defines it differently
- The gap: managers demand it, students hear about it, but no one demonstrates what effective adaptation looks like in real work
The Signal
Samantha Brunhaver got an NSF grant in 2020 to study something everyone claims matters but nobody teaches. She interviewed engineering managers, early career engineers, and students. The pattern was consistent: adaptability is the most requested skill and the least defined one.
Her working definition cuts through the fog: "the ability to recognize that a change or uncertainty is occurring, and then respond effectively to that change." Simple enough. But here's where it gets messy. A software engineer adapting means learning new toolchains every six months. An aerospace engineer adapting means tracking evolving safety regulations. A biomedical engineer adapting means navigating FDA approval processes that shift with political winds.
"Managers are all saying adaptability is important, but defining it in different ways."
The AI boom made this worse in three specific ways:
- New tools arrive faster than teams can standardize them
- Expectations for output inflated because "AI should make you more productive"
- Hiring bars rose because companies assume AI compensates for inexperience
University curricula haven't caught up. Students learn Python or React or whatever's hot when the syllabus was written. They graduate and discover the job wants someone who can learn the next thing, and the thing after that, without scaffolding. The gap between "I can code in X" and "I can figure out Y when the company pivots to it next quarter" is where careers stall out.
Brunhaver's research points to something uncomfortable: the industry wants engineers who can metabolize change without system design for how to build that capacity. It's like demanding cardio endurance from people who've only ever sprinted. The skill exists, but the training pipeline doesn't.
The Implication
If you're early in your career, stop optimizing for the perfect tech stack and start building a practice around learning new stacks quickly. That means documenting your own learning process, not just the code you write. When you pick up a new tool, track what made it click and what slowed you down.
If you're hiring or managing, Brunhaver's work suggests you need to make adaptability legible. Define what it means in your specific context. Show examples of people doing it well. Most importantly, give people safe room to adapt poorly first, because that's how the skill develops. The engineers who thrive in Web4 won't be the ones who knew the right framework in 2025. They'll be the ones who can pick up the framework that doesn't exist yet.