3 ms·

I do love the "we contract to a third party" line used by multiple companies. It's pretty much the H1B body shop contracting applied to service jobs. Just bec

I do love the "we contract to a third party" line used by multiple companies. It's pretty much the H1B body shop contracting applied to service jobs. Just because you hired someone else shouldn't mean you are off the hook for what you are well aware is going on. I still think split shifts should be illegal unless compensated.

ocdtrekkie 10y ago
It also allows the company to talk about how "all of its employees" get X, Y, and Z, without bearing the costs of providing those perks to everyone who works for them. Imagine if Google had to provide their legendary perks to all of their 'contractors'... The scale of buildout that would be required.
- deleted 10y ago
  [deleted]
- GooglyMoogly 10y ago
  At least some contractors get some of the perks. I've seen kitchen workers, security, maintenance workers eating in the cafes. This article says bus drivers have access to the cafes and gym: http://www.businessinsider.com/google-bus-drivers-work-long-hours-for-little-pay-2014-9 http://www.businessinsider.com/google-bus-drivers-work-long-... If all the contractors became employees the diversity numbers would improve. But the pay rate correlation to minorities would decline.
- packetslave 10y ago
  There's only so much that companies can do to provide non-salary compensation (like perks) to contractors and vendors without getting in trouble legally. Blame 80's Microsoft for screwing things up for everybody by abusing their contractors.
  - ocdtrekkie 10y ago
    My inclination was less that tech companies should abuse their contractors, but that tech companies should actually directly employ people that pretty much solely work for them.
    - packetslave 10y ago
      Not implying at all that tech companies are deliberately abusing their contractors. My point was that because Microsoft did do so back in the 80's (and got slammed by the courts for it), now everybody is scared to even appear to treat contractors the same as FTEs. I don't know all the ins and outs of FTE vs contractor vs vendor (I'm a geek, not an HR person), but presumably there are business reasons for choosing one over the other. "One's cheaper" is an obvious one, but there are probably others (taxes? liability? who knows. me write code). There are definitely cases where job functions at major tech companies have been converted from vendor/contractor to FTE (Google physical security officers is one I personally know of. Presumably there are others).

ocdtrekkie 10y ago

It also allows the company to talk about how "all of its employees" get X, Y, and Z, without bearing the costs of providing those perks to everyone who works for them. Imagine if Google had to provide their legendary perks to all of their 'contractors'... The scale of buildout that would be required.

deleted 10y ago
[deleted]
GooglyMoogly 10y ago
At least some contractors get some of the perks. I've seen kitchen workers, security, maintenance workers eating in the cafes. This article says bus drivers have access to the cafes and gym: http://www.businessinsider.com/google-bus-drivers-work-long-hours-for-little-pay-2014-9 http://www.businessinsider.com/google-bus-drivers-work-long-... If all the contractors became employees the diversity numbers would improve. But the pay rate correlation to minorities would decline.
packetslave 10y ago
There's only so much that companies can do to provide non-salary compensation (like perks) to contractors and vendors without getting in trouble legally. Blame 80's Microsoft for screwing things up for everybody by abusing their contractors.
- ocdtrekkie 10y ago
  My inclination was less that tech companies should abuse their contractors, but that tech companies should actually directly employ people that pretty much solely work for them.
  - packetslave 10y ago
    Not implying at all that tech companies are deliberately abusing their contractors. My point was that because Microsoft did do so back in the 80's (and got slammed by the courts for it), now everybody is scared to even appear to treat contractors the same as FTEs. I don't know all the ins and outs of FTE vs contractor vs vendor (I'm a geek, not an HR person), but presumably there are business reasons for choosing one over the other. "One's cheaper" is an obvious one, but there are probably others (taxes? liability? who knows. me write code). There are definitely cases where job functions at major tech companies have been converted from vendor/contractor to FTE (Google physical security officers is one I personally know of. Presumably there are others).