Industry


Ads by TechWords

See your link here


Are you supposed to get overtime pay?

In my experience, the most controversial IT career topics are (in this order): offshoring, H-1B visas, age discrimination and overtime pay. Regarding the latter, there's a natural and human tendency to think that if you can be yanked out of a vacation (or out of bed or out of a movie theater) when paged to handle some IT crisis, or if you have to work a weekend for a system cutover or maintenance, then you should get overtime pay.

But it's more complicated than that.

This article over at CIO.com identifies six things you should know about overtime pay. The law (the Federal Labor Standards Act, or FLSA) determines who gets overtime pay -- and employers determine who's exempt from the law. So naturally employers have a bias towards classifying workers as exempt. But they're supposed to follow FLSA regulations regarding exemptions.

I think the first thing to understand is that, when it comes to figuring out whether you're covered or exempt, job titles don't matter. Only the job duties matter.

With that out of the way, consider whether the duties are repetitive and routine -- the worker follows strict orders, follows a checklist or standard procedure, etc. -- or whether the duties require "independent judgment." Employees doing the latter are exempt.

For example, installing security patches or operating computer hardware, which must be done following strict procedures and with little individual discretion, could fall under the FLSA.

Also, programmers and other software design professionals are exempt if they "earn at least $455 per week on a salaried basis," the article says. On the other hand, software debugging could be considered routine, "non-exempt" work.

So it pays to become educated about the FLSA.

What People Are Saying

This is getting to be a hot topic

I'm hearing more ads on the radio, "Do you think you should have been non-exempt and getting overtime pay? Please call the law offices of Blab, Blah and Bleem."

Next thing I know I'm getting letters that some systems programmer is suing my company and I must respond if I DON'T want to be part of it. I responded of course. Pretty sad since my company provides adequate compensation but it is never enough for some. I knew going into this career I'd likely be salaried and I knew there would be weekends, oncall and late day duties at times. If you don't like the responsibilities then don't accept the job and find another career.

Apparently, the slowing economy is sending the lawyers after different scraps.

State labor Laws are also relevant

In Washington State, the Department of Labor made a Christmas-break rule change that said that anyone working as a computer person (and they listed a long list of job titles that included - programmers, testers, cable-layers, sysads, etc) cannot get time-and-a-half overtime pay if they make more than $27.26 an hour, unless they are in a union that has negotiated it.

The state was able to do this because programmers and geeks are notorious for being naive in the ways of the world, and in thinking that they can individually look out for themselves.

I say it's their own fault. There are enough people in the IT world that if they had gotten together in the late 90's and built up their strength, they wouldn't be looking for jobs as real estate agents or working for $20 an hour with no benfits nor overtime.

BTW, the issue above is not overtime pay, which is time and a half, but being an hourly wage employee. If you are on salary, then there is no such thing as overtime. The way most places work it is that you get "comp time", -compensation time - that allows you time off with pay to make up for the time you worked without pay.

But, in lieu of collective bargaining, if you don't have the skillset to bargain your own interests, if you can be easily replaced, you're screwed.

Independent Judgement

I guess, then, if I'm "exempt", then I can exercise my "independent judgement" to ascertain that the tasks at hand do NOT, in fact, require more than 40 to 45 hours per week to accomplish.

Data Rocks!!

Overtime

I was an hourly employee of an outsourcing sweatshop working for Anthem blue cross insurance co(with no medical insurance for myself!)
Without warning they stopped paying me for overtime(I used to work 50-80 hour weeks) I refused to work over 40 hours a week without pay so they fired me.
They told me they had plenty of H1B's that would take my job, I should be happy that with my 15 years IT experience I was still employed.

I was one of the few Americans working IT at Anthem.

Warning to American students DO NOT GO INTO A STEM FIELD! Long hours no overtime low pay no respect and indentured servants from third world countries are lining up for your job.

Just remember that frat boy with the MBA and a minor in binge drinking will be YOUR boss when you graduate with your hard earned engineering degree.

In the USA we call janitors Engineers and give them better pay and benefits than lowly EE's(Anthems janitors had insurance!)

Until our culture changes, Don't be a NERD, Geek, Dweeb etc. Besides the social concequences that come from long hours studying with little chance for fun during your college years you will not get any reward for your hard work, just a kick in the pants when someone cheaper comes along.

interesting you mention BSBC

i worked as a consultant at a blue cross, i wont mention which one

of all the places i had been a consultant to, or an employee of, it was an unusually mean spirited place, worst i'd ever seen. you could just feel it the moment you walked into the building. these people, most who went to church regularly, would screw anyone, any chance they got. just plain evil

Really

Really, I thought the people who I worked with were very nice. Anthem should screen it's contractors better. The company I worked for was out to screw them. They lied to anthem constantly about deadlines costs etc..