Financial Times: IT graduates struggle to find work
ft.com
ft.com
Some of us went into computer science out of genuine interest in one of the most revolutionary sciences in our lifetime. If it hurts our job prospects, well, that's part of the sacrifice.
I think what we need to do is ask CompSci students what they're wanting to achieve after school. Universities need to offer (and encourage) a broader selection of software development degrees (software engineering, business software, etc) rather than try to dilute CS to be all businessy. I know some schools offer more, but I'm not sure they set student expectations appropriately. Businesses (maybe even more importantly) need to learn how to ask for the degrees/expertise they actually want rather than asking for CS all the time for every software engineering job.
If you're reading this and making hiring decisions-- you can help by changing the wording in your job postings. Stop asking specifically for CS degrees when you really just need someone with a degree who can hack with the best of them.
Think about it, when was the last time you saw "programmer" as a job title? At the very minimum now it's "developer" or "software engineer". No-one actually wants to get their hands dirty with code. And I'll tell you why: in today's modern culture, nothing is right or wrong. Lines, boxes and clouds on a whiteboard and just someone's opinion, no more valid than anyone elses. But code, that requires you to say "this is right" and "this is wrong". Kids these days can't face the pressure of making definitive statements.
That's Plutarch, complaining about the same thing almost 2,000 years ago.
And get off my lawn!
When I was in college (1996-2001), I would say an overwhelming majority of the CS students were there solely for all those tech jobs that their parents read about. They were only interested in learning something for either a grade in class or that someone might hire them to do it. Really, trade schools should be handling those types of people.
No. What IT really wants is "problem solvers".
It doesn't matter what technologies you learned at college, high school, trade school, or from books. Whatever it is, it won't be enough anyway. You'll be expected to get to work, use what you know, and pick up what you have to. For the rest of your life.
More importantly, you will be expected to understand abstract ideas (people and tech), break down complex issues, develop effective work habits, and communicate intellegently with many different types of people. Aren't these exactly the type of things that college is for?
That's simply not true. I agree that that is how it should be. But the vast majority of companies hire by key/buzzwords on a resume. You could be the greatest coder in the world but if you don't have "10 years Visual X+#" you won't even get past the HR screen. Everyone loses in that scenario, you don't have a job, the company doesn't have a worker. Sucks, but there it is.
vast majority of companies
Based upon what data?
I've personally conducted over 2,500 interviews and hired many of them. That's what I look for. And no, I'm not in HR or a headhunter.
That applies to everyone in any field, whether you went to school or not.
My point was that while IT (which to me, means IT department, not software companies) may want those things, what they hire for are the tech skills primarily. And by tech skills, I mean a laundry list of frameworks and APIs.
The skills you mention seem to be reserved for the managers at the places I've worked.
Back then even very proficient students at leading universities had hard time finding jobs. These were people who did programming outside of uni courses, had good summer work experiences, built multi-threaded distributed desktop apps as well as web apps, and were actual 'problem solvers' with good skills in mathematic modeling and algorithm design and architectural design skills. However there was simply no market, regardless of how good they were.
Now, it seems as courses get diluted it really only harms all parties concerned and I often think the best thing someone with good A-levels should do is go directly into industry or in a startup/SME atleast before going to uni.
1990-1994 was frickin' nuclear winter for (almost?) all engineering in (almost?) all western nations. Senior staff in many offices would be left reading newspapers at their desks (superb people with no contracts and nothing to do) and there were extremely few junior positions to be filled. Any work which brought in food and paid rent was welcome, and most of that was stuff I never thought I'd see with a degree.
On the flip-side: After surviving that, bootstrapping a company from scratch was a breeze.
Here's the dynamic a recent graduate faces in a severe recession:
No companies in your field are hiring. Period. Contract work is out as well, since larger companies are now scooping up all of the 'crumbs' which used to sustain junior contractors. There are no boring Q/A jobs to temporarily take, no support jobs, no documentation jobs. Nothing.
You could bump your expectations down and try for work for which you are 'overqualified', but there are tons of experienced, desperate and unemployed people fighting for those jobs too. They will accept less pay than you and any employer with half a clue knows you will bolt the moment you get an offer that fits your qualifications anyhow, making you an inevitable cost and waste of resources to train. Barring an awesome network or family favours, those are out.
So, where does that leave you? I'm sure the seasoned Gen-Xers on the board remember :-)
My own low point was sitting in a basement, handling dispatch phones for a school board's janitorial service, while the 'senior manager' of the group was briefing me on the arduous tasks I'd be facing; at one point explaining to me how to add a column of figures by hand ('you have to carry the one here...').
Most of my friends have similar recession stories and we can all laugh about them now, but things can get far shittier far faster than you'd ever dream possible.
I wouldn't suggest you face the future with dread, but don't kid yourself when you plan out what your 'worst case scenario' could be. Bad economic times can be _really_ bad and it's often a struggle to get through them.
You will, though. It's all cyclical and prospects do improve with time.
A recent graduate in recessionary times rarely has the luxury of sitting back and waiting for the next application round. When there's rent to pay, food to buy and an empty bank account facing you, things can be a little rough.
Not particularly, no. All I had to do was keep my wits and wait for the economy to turn around. These days, I can laugh off the entire experience and sum it up in a message board post.
As you say, in the end you'll be OK if you keep your head and plan for better times. Just remember that, no matter how bleak the environment might become, things will improve.
But there's really no reason why outsourcing will be limited to manufacturing and IT, especially as the kids of the 3rd world IT specialists grow up and choose new professions for themselves. You really only need surgeons, dentists, nurses, and pill dispensing machines on shore. American law books and internal medicine facts can be studied very well off-shore, and trials and meetings can be held via online video. Everything would be digital and operate even faster than ever before. Nurses would have two main specialties, consisting of taking care of the old and taking a patient's vitals for off-shore doctors and computers that are good at predicting events and prescribing solutions, to calculate.
This would also reduce the costs of healthcare for everybody. ;)
This is idiocy. Computer science has as much to do with their business needs as pharmacists have to do with biology. That's why biologists have figured out how to make separate programs for them.
Another question worth asking is what exactly is an 'IT Job'? From the sounds of things the IBM chap wants a Comp Sci degree to mean an IT Consultancy Degree. How useful that would be to some other business that wants really good developers is another matter.
Eventually, they would up getting either non-computer related jobs or being hired by clueless PHBs. There are some BAD programmers out there. 10% would not surprise me.
Some of the commentators in that article argue that CS degrees should be more relevant to the business world. I disagree - too many universities have already hobbled CS degrees to make them (apparently) more relevant to the business world. This leads the wrong people into CS and under-prepares the good students.
It's interesting that they mentioned medicine. Med students learn about a lot more than most of them will ever face in their careers. So medicine is hard and it takes a lot of work. But we expect this, because we expect them to have an integrated view of the body in order to diagnose us correctly.
So why do we settle on CS degrees that are patchworks of business communications, XML and web design?
My (not so humble) opinion: do justice to CS and push the standard up. Graduates from such degrees will be able to handle whatever you throw at them.
Agreed. The notion that 9 out of 10 CS graduates are capable of useful work is beyond laughable.
That said, I hope they find decent jobs.