It could also be that folks that dislike nuance and ambiguity self-select to go into STEM fields because the problems and answers/solutions are more clear-cut and 'concrete'.
Also:
Its also very different from what STEM majors do. In life there are no specific right answers just ones that aren't wrong. STEM majors dont live in a world of binary right/wrong problems any more than anyone else does.
If anything, i think it applies to the m more than the ste.
Engineers deal with ambiguity all the time. They do so in a logical and systematic fashion using statistics and probability. Noise is an unfortunate fact of life.
A lot of engineers I’ve encountered who have little social science or humanities experience seem to not be well equipped to critically evaluate works in those disciplines when they do encounter them. Which makes them vulnerable to crackpot ideology, or just latching onto the first thing they encounter that makes sense to them.
It works both ways though. Many a non-technical CEO has been talked into buying some worthless overpriced piece of enterprise software over the objections of their IT department.
"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".
Or they may be an idiot. That happens, too.
Social sciences aren't criticized for being crackpot anyway, that's a strawman, it's more for the standard reasons that they produce a lot of claims but the evidential basis is weak. If social science was riven with internal debate in which these weak claims were constantly and publicly attacked, then we could compare it to the software world, but in practice we don't see that and dubious claims that come from one or two people often persist for decades before anyone decides to take a second look.
Solving a problem with one or more right answers is very different from critical thinking. Anecdotally I've seen people coming from a heavy STEM background struggle with nuance and ambiguity more than people coming from a well-rounded or heavy humanities background. I doubt the programs themselves are worse for critical thinking (good luck controlling for confounds), but it's not obvious they're better, either.