Slashdot Mirror


LinkedIn Busted In Wage Theft Investigation

fiannaFailMan (702447) writes that LinkedIn was just fined for the all too common practice of requiring workers to work off the clock Following an investigation by the U.S. Department of Labor, LinkedIn has agreed to pay over $3 million in overtime back wages and $2.5 million in liquidated damages to 359 former and current employees working at company branches in four states. The Fair Labor Standards Act requires companies to have record-keeping systems in place to record overtime hours worked and to ensure that employees are paid for those hours, requirements that the company was not meeting.

19 of 108 comments (clear)

  1. Go figure. by Anonymous Coward · · Score: 5, Interesting

    For Silicon Valley Companies, perma-temping and hiring H1B's is part of their business practice, and crap like this is written into unofficial cost of risk reports to execs.

    "High Reliability, High Availability, High Productivity through Meat Grinding."

    The underlying cost of perma-temping is you communicate to individuals who otherwise are worth it to invest in, or who want to invest in themselves, that they are not worth it to invest in only to be exploited, and that you as a company are not worth it to work for. Obviously, if you're an insecure executive manager, keeping the bar low is optimal.

    Remember, This comes on the heels of their entire customer password database being taken off with 2 years back and that feeding spamming and other sideband attacks for years and years. So you know they have significant technical debt.

    In Illinois, where I work, it's a misdemeanor for each offense of this, and a felony if you commit enough of them. Problem is the corrupt politics.

    Doesn't really matter at the end of the day though, because companies who engage in this sort of practice get known and get black listed by the competent.

    1. Re:Go figure. by swb · · Score: 5, Insightful

      While this makes sense in simple, easy to type in Excel, dollars and cents numbers, how is it good for productivity?

      Nearly every place I've ever worked where the company appears more interested in exploitation the quality of work suffers. The really talented people leave. The decent people do a lot less and the crappy people even manage to be even crappier.

      The quality of the work product sucks.

    2. Re:Go figure. by jcr · · Score: 4, Interesting

      The really talented people leave.

      That happened at LinkedIn years ago.

      I had a phone interview with them once, and I cut it short. The guy interviewing me was in no way qualified to ever be my boss.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
  2. Re:Need to hire more H1b's by Anonymous Coward · · Score: 5, Funny

    They also refuse to fritter away valuable keystrokes and time on trivial things, like punctuation.

  3. Ooh, get tough... by fuzzyfuzzyfungus · · Score: 5, Insightful

    It must be neat to be eligible for the section of the justice system where merely fulfilling your past obligations and agreeing to try harder next time is enough to get an official press release praising your integrity, never mind the absence of any actual penalty...

    1. Re:Ooh, get tough... by Noughmad · · Score: 5, Insightful

      Pirate mp3's? Pay damages of up to 600.000 times the cost of the album.
      Don't pay $3M in wages? Pay damages of less than the amount owed.

      --
      PlusFive Slashdot reader for Android. Can post comments.
  4. If only we had a union by Joe_Dragon · · Score: 5, Insightful

    It's about time for one for Tech / IT as a union will put a stop to a lot of this BS and the 1HB abuse.

    1. Re:If only we had a union by rockout · · Score: 5, Interesting

      I belong to a union. I'm a full-time freelancer, in a technical field (not IT), but I belong to a union that I pay union dues to.

      From your comments, it sounds to me like you either don't work for a union, or at one time you worked for an extremely shitty corrupt one. I assure you that while I pay union dues, I also make a lot more money on union jobs than on non-union ones (which I am far less likely to take on, because of the pay difference). I also now get my health care through a union plan, which is far cheaper than getting it on my own was.

      My union dues pay for themselves each year within the first 4 days of work I do, in form of increased day rates that I get paid - and those rates are higher entirely due to my fellow techs and I organizing in 2008. Literally overnight, I suddenly had an about-30% increase in pay, and all I had to do was sign a card saying I wanted to be represented by the union, and I agreed to pay 2% of each check to the union. Pretty good deal by any measure.

      Please don't paint all unions with your "commie unions and corrupt union bosses!!!" brush. It doesn't work that way in the majority of unions. But conservatives have done a great job convincing many Americans that that's actually the case. Which is unfortunate, as wealth continues to get more concentrated at the top. The thing is, my clients pay the higher union rates because they're still making money on each job. They just don't make as much of it, but that doesn't mean they just threw up their hands and said "oh well, we're only making 16 cents on the dollar now instead of 18, time to shut the whole thing down!" They have the money. They just want to keep more and more of it, no matter how much they make. Unions serve as a valuable counterweight to that greed.

      --
      I've learned that they're worthless, so I don't read AC comments anymore.
  5. So start organizing by sjbe · · Score: 4, Insightful

    It's about time for one for Tech / IT as a union will put a stop to a lot of this BS and the 1HB abuse.

    So what is stopping you from organizing a union? If you think it is so important then why are you not doing it instead of just complaining here on slashdot where it doesn't matter at all? Or are you just all talk and no action? Every time this topic comes up there is a bunch of complaining about how IT workers "need a union" but nobody ever seems to think it important enough to actually bother organizing.

    1. Re:So start organizing by Narcocide · · Score: 4, Insightful

      the dirty secret is we all hate each other

    2. Re:So start organizing by Sarten-X · · Score: 4, Interesting

      As a fellow Slashdotter once said, "the best union is the one you're threatening to form".

      Once you actually have a union, you also have a bureaucracy, and rules, and obligations. Sure, they're there to help you, but it still means headaches. On the other hand, if there's just a lot of complaints, the informal process is more flexible and can more easily reach an agreement, as long as the company in question is willing to compromise.

      --
      You do not have a moral or legal right to do absolutely anything you want.
    3. Re:So start organizing by Mashiki · · Score: 3, Interesting

      Back oh 10-15 years ago, I was part of a group that formed a union at a shop I was working at. We built industrial control panels for heavy machinery, lots of electronics and stuff in them, PLC's, relays and so on. If you ever see a small grey square box on the underside of a truck trailer, we built them too. They're used for shifting the rear wheels. Anyway, while you're right that you get the bureaucracy, rules and obligations. In some cases, the employer is such an ass, that it's worth those headaches vs the complaints, threats, and attempts to push people into non-paid OT.

      Some companies are willing to compromise, some businesses too. Some of them just want to see the world burn around them.

      --
      Om, nomnomnom...
    4. Re:So start organizing by Bacon+Bits · · Score: 4, Interesting

      No the dirty secret is when IT people are young we are all naive, idealistic Libertarians who couldn't fathom the idea that Labor might need protection from Capital when the Free Market can clearly fix all ills if only the government would get out of the way. When we're older one of two things has happened: we're in management and on the other side of the table, or we're still in the trenches and we'd rather dangle in the breeze than swallow the bitter pill of our own reality or try to convince the new, naive. idealistic, Libertarian junior coworker that he's getting the shit end of the stick on purpose.

      --
      The road to tyranny has always been paved with claims of necessity.
  6. Slippery Slope by Anonymous Coward · · Score: 4, Insightful

    If you pay some people for working, pretty soon everyone will expect to be paid for working!

  7. Obligatory by Anonymous Coward · · Score: 4, Interesting

    The job market views labor unions as damage and routes around it.

  8. Salaried Employees Get This All The Time by James-NSC · · Score: 5, Informative

    Some companies skirt this rule simply by paying "hourly" employees a salary above $23,600 (per FLSA) then work them 80+ hours a week and call it good. More and more employees, regardless of actual job duties are being paid a salary so they are then "exempt" from any overtime pay, even those that would traditionally qualify under the FLSA & I see this more and more often in the IT sector. If you look at the Computer Employee Exemption - you can make pretty much any IT job fit the bill if you phrase it correctly.

    Workers are left with little recourse because:

    • They've been exempt at every job they've ever had, so they no know different
    • Many - even some of the learned ones - do not know how the FLSA applies to them in this situation
    • Everyone around them is expected to work overtime w/out compensation, so it's not unusual.
    • Regardless of what job duties they will be doing up to and, frankly, especially those including "non-exempt" duties they are told by management that they are doing "exempt" duties
    • They have little real recourse, even if they know they are "non-exempt", unless other co-workers join them in a complaint. Co-workers who are unlikely to do so as:
      • There is little perceived gain and significant risk
      • It is expensive to the point of being cost-prohibitive in order to make a successful claim
      • Any employee who were to be successful would likely find repercussions pertaining to employ-ability later down the road. While not legal to do so above the board, it happens nevertheless (just look at all the wage-fixing and collusion in the valley - you actually think they'll hire someone again, or promote them over a co-worker who didn't sue?)

    At the end of the day, LinkedIn is far from an anomaly, it is standard business practice - unless there is a top to bottom review by some third party (I don't know if there is even an entity that would be suited for this sort of endeavor), this practice will continue unabated. We will work more and continue to be paid less than what we earn.

  9. Time for a professional organization in IT by ErichTheRed · · Score: 4, Insightful

    The current culture in IT is a breeding ground for problems like this. LinkedIn is a public company now, but I'm sure they still operate in Silicon Valley start up mode trying to grind 80-hour weeks out of everyone without paying for them or staffing appropriately.

    I know it's a total pipe dream, but I have an idea that would get IT the representation it needed without the Randian folk getting upset about unions...a professional organization. The AMA ensures high salaries for physicians by limiting the number of spots in medical school as well as setting a high bar for licensure. Professional Engineers (the actual licensed kind) are liable for their work and can refuse to sign off on things that they deem unsafe. Law is a bad example (the ABA went down the same roads we in IT are traveling.) Professional organizations would bring at least a minimum level of universal training to the field. Right now, what passes for education beyond a CS degree is provided by vendors with a vested interest in you buying their product. Projects that you see all over the IT press that blow up after millions of wasted dollars were flushed down the toilet probably would have a better chance of getting shot down right away.

    The problem is that there would have to be a split in the field with regards to job duties, and I don't know how that would be easily separated. Things like tech support, documentation and basic systems administration might be better classed as paraprofessional jobs so that things like OT and on-call hours would be easier to ensure compliance on. And on the other side, systems architects and engineers would need to step their game up...mandatory continuing education, etc. Right now, skill levels and education experiences vary wildly. Hiring someone involves either giving them ridiculous tests to see if they're lying about their experience or just hoping you can smell BS. It would be a good thing for employers as well in the long run.

    I'm sure things will have to get very bad indeed for anything to happen given the culture in IT. IT people have really done a good job convincing themselves that they're white collar professionals, lone wolves and would never need any leverage against an employer. Having a professional organization rather than a union would probably quiet some of this, espeically when people see that they could increase their income and improve working conditions for everyone by doing it. The problem is the toxic "job creators vs. lazy entitled workers" meme -- people need to realize that business owners aren't just going to welcome you into their club if you play by their rules. It's an adversarial relationship, always has been, and people need to treat it that way. Workers will always try to get more for their labor, and management will always try to squeeze as hard as they can. The only way to balance that out is to organize.

    1. Re:Time for a professional organization in IT by RabidReindeer · · Score: 4, Insightful

      ... And on the other side, systems architects and engineers would need to step their game up...mandatory continuing education, etc.

      Here's part of the problem. Long, long ago, there was this thing called "Certified Data Professional" Locally, some people tried to make a big deal of it, and I even knew 1 or 2 people who took the exam. In fact, I have the study guide.

      But it didn't work then, and that was back when just knowing COBOL and basic I/O was good for the majority of the jobs. Unless, of course, you worked exclusively with FORTRAN, PL/1, RPG or Assembler. And then there's which OS to be proficient in JCL for. Or which brand of hardware: IBM, Univac, Burroughs, or one of the other "7 dwarfs".

      The field has exploded since then. We have batch and interactive, multiple flavors of GUI systems, mobile devices, various and sundry web platforms - and I can't even count just the ones for Java, even before Ruby on Rails, Django, and on and on. We have scientific computing, AI, business processes, multiple database options, LDAP, virtualization, containers, clouds, Big Data - something new every week.

      There's NO TIME to make a one-size-fits-all professional competence exam based on continuous learning. We're all learning different things, and we can't slow down because we're already at the point where we need to learn something else.

      I have no solution, other than to notice that the cram-and-barf exam/cert solution is obviously worthless. The only certs I've seen that I'll credit are less on details and more on things like whether you can bring up a general-purpose Linux (or Windows) server in 4 hours.

      I'd be inclined to simply make it a "web of trust" thing where to be certified, you needed a certain number of votes from people already in the club. Meaning that they're willing to risk their reputations that you're decently competent. But that, too has its flaws. Good Ole Boys get free passes and unwashed twerps with bad social skills get left out. And bad social skills are almost a badge of honor in IT!

  10. Re:Need to hire more H1b's by praxis · · Score: 3, Informative

    H1b's just do the OT with out makeing a big deal and if they quit or get fired they have to go home if they cannot find a new job and complete the transfer within 30 days after being fired (which is very likely to be the case).

    You are correct about not rocking the boat, but I corrected the sentence for you.

    The poster you "corrected" appears to be more correct than your correction. According to Klasko (I tried for ten minutes to find the relevant document on dhs.gov), there is no 30-day period. The visa status ends immediately and the employer must arrange travel back to the country of origin. In practice, a new H1-B petition *might* be approved by the government but it appears there is no grace period, it is at the whims of the petition reviewer.

    If an employer terminates an H1-B employee before the end of that employee’s period of authorized stay, the employer is liable for the “reasonable costs” of return transportation for the employee to his or her last country of residence.

    Contrary to popular belief, there is no “10-day,” “30-day” or other grace period for terminated employees holding H-1B status. Once the employment relationship terminates, the H-1B employee is out of status. While USCIS has proposed a 60-day period within which an H-1B worker may seek new employment, that period remains only a proposal.

    From: http://www.klaskolaw.com/artic...