Slashdot Mirror
Mr. President, There Is No (US) Engineer Shortage
McGruber writes "Vivek Wadhwa has written an article in the Washington Post titled, 'Mr. President, there is no engineer shortage,' which addresses the perceived national shortage of engineers. Wadhwa slams China for its practice of applying the 'engineer' label to auto mechanics and technicians, yet fails to slam the U.S. for its practice of applying the 'engineer' label to sanitation workers, building janitors, boiler operators, FaceSpace coders, MSCEs and DeVry graduates. He also says, 'Some of [the U.S.'s] best engineers are not doing engineering, and some of its best potential engineers are not even studying engineering, leaving us short-changed in solving the important problems of the day.'"
Shortage of engineering jobs, not of engineers or potential engineers. Its almost as if we moved many of our jobs to other countries for short term profits in exchange for long term economic vitality.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
"fails to slam the US for its practice of applying the 'engineer' label to sanitation workers, building janitors, boiler operators, "
I knew a woman who used to demand the title of "Domestic Engineer". Also known as "housewife"
If you want more software engineers, you can create them trivially : Allocate a half billion dollars or more to an academicly overseen open source initiative, roughly like google's summer of code, but higher salaries dependent upon education level. Voila, instant developers!
If unemployment means drawing down $50k per year working on your own pet project, that'll make the field unbelievably attractive to young people, and keep old folks in the game. And those projects will ocasionally convert into commercial open source companies that employ other developers.
How many NASA guys are now pumping gas in Florida?
Lack of engineers, my ass.
Hey Mr President, we need jobs and stuff to be designed and built. Then you'll see the engineers get back on the grid.
Huh?
There is definitely a shortage of engineers. A shortage of engineers that are willing to invest multiple thousands of dollars into a degree so they can watch BA majors rake in 3-5 times what they earn, who are willing to spend the better part of their life paying off their tuition bills while working their ass off, knowing that they, too, could have gotten that BA degree. Probably with less stress and less work.
Yeah, there's a shortage of smart people who are dumb.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
I just addressed this problem a few minutes ago, here. Too many people with technical degrees feeding the legal, MBA, patent, PHB food chain. Too few doing work.
Anecdote: Back when I joined Boeing (many years ago), we had a 'lead engineer' system. The lead engineer was just the go to guy (women not yet taken seriously there) who had the final word on technical issues within a group. That freed the first level manager to to his reports, go to meetings, etc. He was just (usually) the senior guy in the group who knew the system and could mentor the new hires. Then, it became common practice for management to offload planning, scheduling, employee evaluations and other tasks onto the leads. Pretty soon, that was the majority of their job (the question was: where were the managers going during the day). Management had long since become detached from the technology and it was common for the boss to have no clue about how their system worked. A few leads took voluntary demotions or shifted to different groups to get out from under these duties. Pretty sad. Soon, even the leads had become mini managers and were becoming separated from the actual work going on. In my final position with the company, management brought in a lead engineer who had no clue about what we did or the state of the art in our field of work. All he did was to run around and pester people for formal reports on their schedule projections and progress, and budget inputs in order to assemble his own reports on the same thing (Even though he had no idea what we were doing. He reported that we were through task X because we said we were.).
Everyone wants to get an MBA and be a manager. Because its the hierarchy and that's what dictates reward and respect. We need a system like sports teams have. The coach might be a fat slob and not necessarily the best player in his career. The star players get rewarded commensurate with their skills. The coach is rewarded for the ability to hold the whole thing together. But those are separate skill sets and often its the bad coach that gets sacked more often than the players.
Have gnu, will travel.
There is a lot of engineering talent (and potential engineering talent) in the US. The problem is that companies aren't willing to pay for it! The MBA management style has made it very hard to have a long tern engineering career- the engineer is viewed as a commodity (why do you think it is called "human resources"?) that can be easily replaced by another unit in another location, across the country or across the world. Why give a raise to retain an engineer in a position when you can save money by shipping the job somewhere else? Many people who are smart and want to have an income that slightly outpaces inflation may start in engineering, but don't stick around.
Some manager gets a promotion for lowering (apparent) costs by outsourcing, and after they're gone, another gets stuck with fixing it. We are very good at training engineers in foreign countries how to do what we do well, and in that, we have managed to do is to shift the engineering talent overseas, where it also gets more expensive, negating the benefit.
Can the medic build a sentry gun? No. Can the medic build a dispenser? No. Can the medic build a teleporter? No.
There are some good medics out there, and a good medic/heavy combo can wreck your ass worse than goatse, but most of the time a team will have 2 or 3 engineers and not a single medic.
Do you even lift?
These aren't the 'roids you're looking for.
My own unemployment situation is terminal - but it's a product both of the economy and my inability to relocate. If I'd been free to move to an area where the jobs in my field are three or four years ago, chances are I'd never have become unemployed in the first place. Of course, I've now been unemployed so long that I couldn't even get a job in those areas anymore. However, living where I do there's a major mismatch between what employers seem to want (seems to mainly be enterprise Java coders) and where the bulk of my experience lies (systems engineering). However, while I have the skill set to work with EJB 3 or Spring, that's just a side effect - in my last job, the work I was hired for never really materialized, so I ended up doing a fair bit of Java before they decided that they'd be better off using the money they were paying me to get a couple of dedicated coders, without all of the baggage of my experience doing other stuff, straight out of college.
While I've given up looking, I think a lot of problems lie in the areas of HR, whether in-house or through an agency. With the exception of a few particularly specialized tech-oriented agencies, there's a real disconnect between the people who run the departments who have the vacancy and the people who do the hiring. That's a problem, since it's difficult to convey what's really needed for the job, and where having skills A and B is a valid substitute for C, or cases where you've got experience in D and they don't know that implies your expertise in E and F is off the chart, or where experience in G can get you up and running with H very quickly even if you're not experienced with it. They feed the resume through their buzzword checker, and kick it out if it doesn't include C, E, F and H. So somebody who is quite capable of doing the job doesn't even get through the preliminary culling of resumes. A good tech agency can do a lot there - and I had one for a while, who put me forward for jobs that even though I didn't look like a good match to HR, they knew from extensive interviews and their own expertise what I could and couldn't do.
In the end though, I think a bigger contribution to me stopping looking was the way I'd been treated by employers and potential employers over the years. In my last job, my boss was *so* insistent that I had to get a specific piece of work done by an arbitrary date (arbitrary because it was between Christmas and New Year, and those who were depending on it weren't going to be back in the office until January 5th) that I had to work over Christmas day, and *then* laid me off on January 7th. Then there was the Dream Job where the hiring manager seemed *super* enthusiastic from the first interview, and had me in for a second and third interviews on the next couple of days, then told me that while he couldn't say I had the job since he had to get his manager's manager to sign off on it, it was really just a technicality - then it took 2-3 weeks for them to actually pin down the right people and get them to sign on the dotted line, so long in fact that the company changed its policy so that they would no longer hire people through agencies before it was all done, and after keeping me hanging on with "any day now" for close to a month it was "Sorry, we can't hire you, bye." Of course, the agency that had put me forward had me under an agreement whereby the company in question couldn't hire me directly for a year. Even though the agency went out of business about three months later, it was still too late. That one pretty much broke my spirit completely - it was the only job in my field that I've *ever* seen advertised here (excluding one local company that has as a mandatory requirement experience with a particular DoD standard that you can only get in this state by working for *that* company).
So I gave up. In theory I'm having a go at getting going on my own in iOS/OS X development, trying to funnel what I did for fun in my spare time into a job, but that's getting nowhere. I've spent seven of the last ele
Funny you should mention 'free markets' WRT jobs. The tech industry had the benefit of an ample workforce. In fact, there was such a glut of workers, the tech industry got exemptions from paying overtime into law. Such was the state of the workforce that it became expected that we programmers would work 60 hours/week. If someone didn't want to work that hard, it was easy to find a replacement. No other engineers that I know of would be expected to work such long hours. I was one who discouraged people from attempting a 'career' in tech.
'Free market' forces came into play and the next generation of college students avoided the tech industry with its draconian demands on its workforce. Enrollment in CS dropped off, and supply and demand started to revert to the mean. Of course, H1Bs, another sop to the industry, helped kill off the American tech workforce.
Any wonder that there is now a 'shortage' of workers in tech?
Here's a wacky idea, give people back decent pay, job security, company paid health benefits, decent pay, 401k matching funds, decent pay, and cut back on the hours. Did I mention decent pay? Now get a mature management in place and treat the workforce with respect. Does the industry truly believe there's a shortage of people willing to do the work, or are they just pining for the days when they had it so good?
Reminds me of the claims by the farming industry that there's a shortage of Americans who are willing to work as farm workers. Farmers were sneaking low-paid illegal workers into the country, and pretty soon you had to have a migrant workforce to be competitive. Result? Low pay and job losses for American workers. Money leaving farming communities and ending up south of the border. Rural towns drying up, and nobody willing to be honest about the reasons why. So they blame the victims, they claim that Americans are 'not willing to work'.
Best regards.