Slashdot Log In
IBM Responds to Overtime Lawsuits With 15% Salary Cut
Posted by
samzenpus
on Thursday January 24, @07:55AM
from the give-with-one-hand-and-take-with-the-other dept.
from the give-with-one-hand-and-take-with-the-other dept.
bcmbyte writes "IBM in recent months has been hit with lawsuits filed on behalf of thousands of U.S. employees who claim the company illegally classified them as exempt from federal and state overtime statutes in order to avoid paying them extra whenever they worked more than 40 hours per week.
The good news for those workers is that IBM now plans to grant them so-called "non-exempt" status so they can collect overtime pay. The bad news: IBM will cut their base salaries by 15% to make up the difference."
Related Stories
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading ... Please wait.

Hmm (Score:5, Informative)
Re:Hmm (Score:5, Informative)
Re:Hmm (Score:5, Insightful)
It's a short term monetary gain (in the form of a settlement), for a net loss in wage security
Depending on the job, wage security is often less of a concern than schedule security, ie the possibility that the boss will tell you you're working 80 hours next week. Now he has to account for extra overtime over the usual in his budget, and that's a heck of a deterrent.
Each may very well be more important to different people. As another respondent said, this probably is best for the quality employees who always find themselves overcommitted and working hard, and maybe less good for clockwatchers.
Stapler (Score:5, Funny)
Re:Stapler (Score:5, Funny)
Typical. (Score:5, Insightful)
Re:Typical. (Score:5, Funny)
Re:Typical. (Score:5, Insightful)
Re:Typical. (Score:5, Interesting)
I've been "exempt" for the past 10 years, and wouldn't trade it for hourly wages + overtime for anything. The fact I'm "exempt" pretty much assures that I have a strong salary and needn't worry about those extra 5 overtime hours per pay period to make rent. I realize that sounds snobbish, but TFA gives examples of jobs in the 80k per year range...hardly the types of jobs that worry about making the rent payments.
A better solution than the labor unions would be for these 80k/year salaried folks to take their skills elsewhere, like to a company that values their contributions. I've never understood how a union supporter could go back to work for the same pricks they were fighting with in the first place.
Re:Some reference materials (Score:5, Insightful)
Previously, their annual salary would've been approximately 2000*x. It is now about 1700*x. Assume overtime is time and a half, they would get paid 1.275*x for each hour of OT. This means they would need to work about 236 hours of OT a year, or about 4.5 hours per week. If they were working so much OT that they were willing to sue, then this should be easy to make up and in the end they are making more money, since they weren't getting paid OT before.
Their only other option would've been to unionize; however, if these are programming and/or engineering jobs, you can bet IBM would've outsourced them in a second to save the money and the hassle of dealing with a workers union. Also, don't think there aren't plenty of engineers in the US who are willing to "scab". Most the engineers I know (myself included) absolutely abhor unions.
Again. (Score:5, Informative)
Re:Again. (Score:5, Insightful)
The end result is exactly what IBM did. Suddenly starting to pay for overtime means IBM is raising effective salaries by 10-20% or more, so naturally IBM lowers base salaries. The end result is that we are exactly where we started - people work the same hours, and get the same pay.
Well, at least on average; for individuals who work more or who work less, there will be some change. There are also motivational issues - if you are paid for overtime, you have less incentive to work efficiently (one reason why hi-tech managers, and many workers, don't like paid overtime and prefer to raise the base pay). Overall, it is hard to say that the change is for the better. The old salaries and norms were already 'working' - they were comparable to industry norms, were arrived at after years of haggling, corrections, and so forth, and most importantly people knew what they were getting when they signed on.
Lawsuit? Prepare for Other Pain... (Score:5, Interesting)
Sounds about right, actually (Score:5, Interesting)
Re:Sounds about right, actually (Score:5, Interesting)
In my experience, the biggest drawback to being an hourly employee is that the company tells you when you can't work. If you're really enjoying a project or on a roll, it's extremely frustrating to be told that you have to stop for the day/week. You can't just not record any extra hours worked either as it's a liability for the company.
It's stories like this... (Score:5, Insightful)
The bad thing about being a contractor is I only get paid for the time I work (no sick leave, public holidays, annual leave etc)
The good thing about being a contractor is I get paid for _every_ hour I work.
Strangely enough, once I was working on a strictly per-hour basis, the boss found far fewer 'emergencies' that required me to work all weekend.
Re:It's stories like this... (Score:5, Insightful)
The bad thing about being a contractor is I only get paid for the time I work (no sick leave, public holidays, annual leave etc)
The worst day working for yourself is better than the best day I've ever had as an employee...ever. There is a lot of detail work necessary: Invoicing, collecting on the invoices, insurance, license fees, expense tracking, quarterly taxes. And there are liability issues to consider. But as more and more employers keep pushing responsibility and accounting issues down to the lower ranks, the amount of paperwork really isn't that different. Many employers expect you to process all that paperwork on your own time and travel on your own time. Plus a lot of them are getting dickishly intrusive monitoring and spying on their employees.
Besides, cubicles suck ass.
IBM gets caught breaking the rules and responds by cutting salaries. Nice. Just keep pulling stunts like that and your turn over will remain painfully high.
Strangely enough, once I was working on a strictly per-hour basis, the boss found far fewer 'emergencies' that required me to work all weekend.
Funny how that works, isn't it? Want me to work all weekend? No problemo! Just sign this invoice...right there...here's a pen.
Penny wise and pound foolish (Score:5, Insightful)
Re:sounds about fair (Score:5, Interesting)
Re:Free market (Score:5, Insightful)
Re:regulated in contract or law? (Score:5, Informative)
When I used to work for IBM (10 - 8 years ago), it was standard U.S. practice: each year, your manager calls you into a meeting and tells you what your new pay level is. You can accept it, or quit your job, or treat it like the beginning of a negotiation, which will in most cases get you labeled as a difficult employee.
It's pretty laissez faire, except that they can't base your pay level / pay level changes on race, religion, etc.
Re:Free Market (Score:5, Insightful)
Re:Free Market (Score:5, Informative)
Re:Free Market (Score:5, Interesting)
This does sound like a slap in the face, but the first slap was by the employees -- suing your employer (or anyone) "means war".
No, the first slap was IBM breaking the law by classifying employees as exempt when they were not. The employees are totally in the right here, and IBM 100% on the wrong side.
Companies like to claim exempt vs. non-exempt is a "gray area." Its only gray when you're trying to screw your employees out of overtime pay.
My personal belief is that salary pay should be made illegal except for strickly management positions. That would solve this problem nicely.
Re:Seriously (Score:5, Interesting)
You have obviously not thought that through to completion. You decide to form a union, and your employer does not like it. One of several things can happen:
1) Your employer takes it on the chin and suffers from a significant loss in net earnings (usually gets executive types all fired up, pun intended).
2) Your employer accepts it after fighting about it and is then undercut by union free competitors, typically using H1B labor, or worse yet simply outsourcing to another country altogether.
3) Your employer gets smart and simply outsources your job, thereby skipping all of the intermediate steps.
Our economy has become a service economy because those are the only jobs that cannot be outsourced easily, but a service economy can't survive indefinitely without outside support. Either way, unionization is not the answer, the only viable answer is to accept that you will suffer a significant drop in standard of living to adjust for the fact that you were way far above the median to start with. Don't like it? tough, welcome to the global economy, there isn't a damn thing you or I can do about it. If you shut down all foriegn trade, there goes your cheap goodies from china, and your standard of living plummets. Imagine if you had to pay $30,000 for a low end car, because it was made using exclusively american labor? How about $120 for a pair of jeans? What about $5,000 for an entry level PC? If you need proof, just look at the cost of housing. It is hideously expensive because there is no good way to offshore the labor needed to build the houses, and as such the cost of these things has been rising at many times the rate of inflation. It is a no-win situation. Americans are not going to enjoy their standard of living much longer, but there isn't anything we can do to stop it. Maybe slow it down a little, or speed it up, but there is no stopping it.
-=Geoskd