> Most of the engineers I've encountered can and do critically evaluate work in social science and the humanities, correctly conclude it's built on a very flimsy foundation of scientism, has little value
"correctly conclude", huh. You're basically saying "people with similar backgrounds as mine reject the theories proposed by people with very different backgrounds, and I think they're quite right".
I probably have a similar background as you do compared with a professor in social science, so I might agree with your conclusion (that a lot of theories in humanities are flimsy), but I see nothing to indicate (except your assertion) that those engineers you know actually evaluate work in social sciences and the humanities critically. Maybe they reject them because they sound so alien and unfamiliar?
If you mean they're "critical" because they don't easily buy into those crackpot theories, perhaps consider the crackpot theories in the software engineering profession -- Agile methodology? Test driven development? Best way to interview programmers? Benefits of using $fad_framework? These are actually questions that could in theory be answered using social science methodologies. Yet what we do as a profession is simply cargo cult what the big names do. IMHO a tech CEO being sold on useless "Agile" methodologies is basically the equivalent of "a non-technical CEO has been talked into buying some worthless overpriced piece of enterprise software".