Slashdot Mirror
The STEM Crisis Is a Myth
theodp writes "Forget the dire predictions of a looming shortfall of scientists, technologists, engineers, and mathematicians, advises IEEE Spectrum contributing editor Robert Charette — the STEM crisis is a myth. In investigating the simultaneous claims of both a shortage and a surplus of STEM workers, Charette was surprised by 'the apparent mismatch between earning a STEM degree and having a STEM job. Of the 7.6 million STEM workers counted by the Commerce Department, only 3.3 million possess STEM degrees. Viewed another way, about 15 million U.S. residents hold at least a bachelor's degree in a STEM discipline, but three-fourths of them — 11.4 million — work outside of STEM.' So, why would universities, government, and tech companies like Facebook, IBM, and Microsoft cry STEM-worker-shortage-wolf? 'Clearly, powerful forces must be at work to perpetuate the cycle,' Charette writes. 'One is obvious: the bottom line. Companies would rather not pay STEM professionals high salaries with lavish benefits, offer them training on the job, or guarantee them decades of stable employment. So having an oversupply of workers, whether domestically educated or imported, is to their benefit...Governments also push the STEM myth because an abundance of scientists and engineers is widely viewed as an important engine for innovation and also for national defense. And the perception of a STEM crisis benefits higher education, says Ron Hira, because as 'taxpayers subsidize more STEM education, that works in the interest of the universities' by allowing them to expand their enrollments. An oversupply of STEM workers may also have a beneficial effect on the economy, says Georgetown's Nicole Smith, one of the coauthors of the 2011 STEM study. If STEM graduates can't find traditional STEM jobs, she says, 'they will end up in other sectors of the economy and be productive.'"
Whereas it's practically accepted that just possessing an bachelors degree in Education means that someone is qualified to teach children what they need to know to advance in STEM fields.
You can easily have an abundance of STEM people overall, and yet have a shortage of people in specific fields. The shortage is of course most likely in new and in growing fields, while surpluses are most likely in old and settled, or declining areas.
So, mismatch can easily explain the discrepancy without ascribing malicious intent to anybody (which is not to say there is none). Instead the problem really is the tension between learning a field and training for a specific job.
Seems US and European corporations are more and more insistent on finding workers that fit right into a specific job with little to no training*. Which seems good in the short term, but people with mostly job-specific training will have a much harder time retraining for a different kind of job when the winds inevitably change. They'll act as anchors for their employers, and collectively reduce the pool of qualified replacements if or when their employers decide to kick them to the curb.
I suspect that this practice is in fact bad in the short term as well; but since the effects across the life cycle of an employee are felt in very different parts of an organization it's not a waste that any one person will normally notice.
* Japanese corporations, on the other hand, go overboard in the other direction. They hire mostly or only new graduates for any career jobs, and you - and the company - generally don't even know what you will actually be doing once you start. They want to hire blank slates they can train and mold as they see fit.
Trust the Computer. The Computer is your friend.
I am increasingly dismayed by the number of individuals who profess ten or even twenty years of IT experience on their resumes, yet who cannot solve the most basic design problem or answer questions about the fundamentals of the language they use daily.
I've been programming for a long time as a hobby. I've been at my current job for 10 years now. I write webapps (mostly as a cowboy coder), do some administration work on enterprise systems and basically I'm the guy in my division they call when any project gets stuck on a technical issue.
I see interview questions for SQL and Java which I've used a lot of in the past 10 years, some of them I can solve, some I cant. I really wonder what kind of hell I'd have to go through to get another job. Half the time I think "I'd just google that if I had to do it and figure out the best methodology from there". I've really come to the conclusion that my best skill set is that I read documentation, I can find answers quickly on google, I can come up with creative solutions to business process issues, and I've been doing IT for so long that I can deduce what an issue is fairly quickly just from experience. I really don't know how you figure those things out in an interview, or how you communicate them to a potential employer. Furthermore, employers seem more interested in you knowing some nuance of a programming language, or something that just doesn't apply to day to day programming.