Slashdot Mirror
IT Job Market Is Tanking, But Not For Everyone
CWmike writes "Shortly after the COO of Automated HealthCare Solutions learned that Microsoft planned to cut 5,000 workers over the next 18 months, he and another employee of the medical services provider flew out to Redmond. AHCS now has more than 100 resumes, some of them from Microsoft employees, for about a dozen open positions. That's how the tech job market is these days: there's no doubt the market is tanking, but not for everyone. While numerous IT vendors are laying off workers, and corporate IT jobs are being lost as well, plenty of companies are still hiring. Microsoft's careers site lists more than 700 open jobs in the US, both technical and administrative positions. And IBM has about 3,200 jobs and internships listed worldwide, more than 550 of them in the US — even as it cuts thousands of workers in a move that it is describing not as a layoff, but an effort to 'match skills and resources with our client needs."
If you're good, you can always find a new job. Smart companies always have exception programs to let in talented individuals. Layoffs tend to be a way to get rid of a lot of the sub-average to average performers. If anything, finding good quality people is even more important after layoffs are announced- the good ones have the ability to get hired easily, so they'll hedge their bets by looking as soon as layoffs are announced. Its not uncommon to see an exodus of them before the layoffs actually occur. Plus you can typically hire one of them to do the work of 3 or 4 of the people you just fired.
I still have more fans than freaks. WTF is wrong with you people?
"Match skills and resources with our client needs" doesn't mean layoffs...its a feature!
Actually, IBM claims that it's not an extraordinary event - in the course of normal business, every quarter they lay off some people with useless skills and hire others with useful ones.
They didn't file an extraordinary activity report with the SEC because a certain level of layoffs is ordinary in an organization that size.
-- Support a free market in the field of government
Something that everyone forgets is that many companies use downturns as a time to clean house, to get rid of people that they feel are more dead weight than not.
Now anyone with experience in a large company knows that also can include some good people that ended up on the wrong side of an internal political battle, and doesn't usually include much middle management that may well be overburdened. Even so, layoffs are not always about a company needing to get rid of jobs so much as a natural resetting mechanism (at least at first).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
We're on hiring freeze despite a sizable number of openings posted.
Good point. Since people use job openings to judge the health of a company, it's possible to use it to send a misleading signal to the stock market.
-- Support a free market in the field of government
Not that smart. If I see too many people around me fired, I'll look for a new job before you get around to firing me.
If I'm good, and you want to keep me - I'll find another job.
-- Support a free market in the field of government
Here in Mass, I just went through a fairly time consuming round of interviews for an open Sr. Linux Admin position I had open. I must have had more than 300 resumes come my way, reviewing about 200 of them, phone interviewed about 25 people, personally interviews another 15, all over the course of the past 5 months. My bosses were having a very difficult time comprehending why I was having such a hard time finding someone in such a market, but frankly, quality people have been tremendously hard to come by. My bosses were getting frustrated that I wasn't getting the position filled fast enough. I stuck to my guns and recently (finally!) found a solid candidate.
It has already been mentioned, but in speaking with a few recruiters, the general opinion was that the company's that are laying off are cleaning house of dead wood for the most part. Those who are good at their jobs are staying put right now until the market seems to show some sense of light at the end of the tunnel. Of course their are casualties at all levels in various orgs, but I'm not yet left with the overwhelming sense that quality IT people are flooding the market looking for work.
The "fire 10%" strategy has the interesting side effect of ruthlessly exposing the quality of your performance metrics. If they are quite good, it might actually work. If they are indifferent or worse, you'll cut your own throat in short order. Nothing like an office full of people gaming the metrics and covering their asses to get things done.
I feel this is a good time to discuss my signature.
.sig as just a reminder of that horrible incident. So, think not of my signature as a juvenile C joke intended to frustrate an experienced DOS user, but instead the C port of the subroutine patch that costed me a Microsoft job at the time when, as a company, they were just about to reach their peak. Layoffs are not funny, even if caused by such a humorous-at-first-glance patch.
Years ago, when MS-DOS was just entering version 5, I worked for Micro(-)soft, and I was on the shell team. One little optimization could be made to the PAUSE function, I thought, so I added it in, and even when I told my manager of the patch, he said surely a promotion would soon ensue, and Dave Cutler might even consider me for this project called "Windows NT"!
So everyone approved, and the patch was added. It was written in assembly language, by the way. So the patch was added, and soon the final build of MS-DOS 6 shipped. However, soon we started getting calls from users saying their batch files crashed DOS, and a thorough code inspection went under way. While inspecting the last couple of patches, many bugs were found, some even I fixed, and we were sure MS-DOS 6.21 was the final solution.
How wrong were we! The test batch files still crashed the OS, and upon further inspection, it was found that the PAUSE() function would crash just after printing the characters to the screen. They inspected my patch, found an erroneous jz mnemonic (despite our getch setting the eax [return] register to a non-zero ASCII character).
The log showed it was my patch, and I was soon speedily fired before the compilation of MS-DOS 6.22, which corrected the PAUSE function I messed up so bad. I have since regretted that function every day of my life, and I put it in my
Never forget, slashdot, never forget.
Please don't think me greedy for what I'm about to say but I'm currently still employed after over 3 rounds of layoffs and I've recently kicked my job search into high gear. While I have to agree that what's currently left at the small company I work for is nothing but the best (at least in the IT department) the workload that was done by 30 is now done by 10 -- with as few as 3 people in one section of IT.
That being said, these *quality* people who probably have nothing to worry about are jumping ship (even management!), some without even having jobs to switch to yet. But I guess that's what happens when reason goes out the window and marketing calls the shots in an attempt to turn a profit for a change. That coupled with pay cuts leaves a bad taste in people's mouths.
I disagree with the thought that the good workers will sit idly by and take what the companies are doing and accomplishing what 3-5 of their peers used to. Sometimes what seems like a good job for a while can turn ugly and treat you poorly when things get tough and that's not necessarily a place you want to work. At least that's my reasoning.
Funny, I seem to recall something different said about your .sig. Still funny, though, I enjoyed the story, despite the obvious made-up MS-DOS versioning used.
Oh, here we go, cue the chorus of "Dude, if yer the best you can alwayz get werk..."
Listen up. You have to look at this systemically. If there are a thousand people willing to do your job for less, it doesn't matter how leet and brilliant you are. You are an expensive widget, and the business side will always sacrifice quality for cost. Do you really think the suits upstairs can tell the difference between Linus and Zaboomafoo the Typing Lemur?
My phone rings daily with scared-crapless kids whose networks are falling apart because they don't have the experience the position requires. Every one of those kids replaced some grey-haired 40-year-old who would have avoided the disaster months ago, but was let go because Billy the Paperboy braindumped his certs and offered the do the job for less.
No one, No. One. Ever connects the million-dollar disaster with the now-incredibly-cheap-looking salary that would have saved the company untold amounts of money.
So, for the Beavis-and-Butthead crowd sitting around crowing about how they're the best, look at it this way: The surplus resumes flooding the market may not cost you your job, but they will cost your your raise, as well as any leverage you might have had to push back against bad ideas. They'll cost you in the midnight calls you get and the tribute of overtime demanded because your boss knows you don't have any other options. And if you really are that good, it still might not save you.
He put his boots up on the table and made a face. "The sig," he smirked. "You can waste your life in search of the sig."
Ah, I had more fond memory of doing optimization. I'll chip in my story.
I just graduated in the early 90s, and started working the next day after my last exam, at a small telecom equipments company. The system was running on QNX 2, with every software components developed in house, except the OS and some of the drivers.
The company was built by hardware engineers, and I was the first guy from a CS background. There were 6 people in the engineering group. The "database system" was actually a small engine of simple linked list, and must load all data into memory to do anything. Insertion, modification, deletion, etc, were slow, database-related work is so slow, but everyone was used to it. Especially on a 386SX with 1MB of memory, and QNX had no virtual memory, the physical memory was precious.
After I started working, I saw this and said: "What the fuck?" Being good at data structure and algorithms, I decided to do something. Not to interfere with my day job, I spent a couple of evenings and one weekend, writing a memory-mapped B-tree engine, with some quite primitive transaction and rollback features, while trying to keep the same API as the original linked list engine. The memory-map part was so that I wouldn't have to load all data into memory to do the work.
After testing for 5 or 6 hours on the Sunday afternoon and evening, I plugged it in, replacing the old engine. I "checked in" the code. We didn't even have CVS, we just mount to the manager's machine, and put the codes there (basically, replacing what was there). I made the mistake of not informing the manager.
I went home the evening, it was raining hard, got wet, and had a fever. The next day, I called in sick.
At noon, the manager did a new build for testing. People where shocked that database-related operations just returned back right away. This normally would be an error situation. A few panicked, as there was no CVS to track who checked in what, and the db engine was there for almost 2 years already, and considered the most stable component. So no one looked there. But everything seemed to work just fine.
While I was sick, I also wrote a design document about the new engine, how to call the API, etc. On the 3rd day, I came in. After my first cup of coffee, I heard the news from my neighboring coworker. So I went to see the manager, told him about what I did, and handed him the design document. This was the first "real" design document, BTW.
The manager was relieved and excited, and finally, called in the CEO of the company too, and said: "Dude, you scared the shit out of me, but this is great work. Next time, tell me first before putting in the code, ok? I'm too old for that. BTW, do you see other areas that we can improve?" The CEO said: "I'd like to hear that too." With that kind of encouragement, I gave a list of areas that should be reworked, but with very low risk, and some areas that might need extra works.
The CEO said: "I want you to work on those items".
So, for the next 6 months, I was working more or less on every component of the system, including the UI framework that we developed (no, QNX Photon was still many years away), to do optimization and in quite a few cases, re-code them.
And I also downloaded CVS at home with my oh-so-slow modem (the company has no internet connection yet, only the CEO and VP had dialup), brought the floppy to the company, compiled the CVS source on QNX, asked and got a new machine to build a CVS server, so that we can track the codes better.
At the end of the year, I got a big bonus, with 2 extra days off for the Christmas holiday. It was fun.