About Half of Google's Workers Are Contractors Who Don't Receive the Same Benefits as Direct Employees (bloomberg.com)
Every day, tens of thousands of people stream into Google offices wearing red name badges. They eat in Google's cafeterias, ride its commuter shuttles and work alongside its celebrated geeks. But they can't access all of the company's celebrated perks. They aren't entitled to stock and can't enter certain offices. Many don't have health insurance. Bloomberg: Before each weekly Google all-hands meeting, trays of hors d'oeuvres and, sometimes, kegs of beer are carted into an auditorium and satellite offices around the globe for employees, who wear white badges. Those without white badges are asked to return to their desks. Google's Alphabet employs hordes of these red-badged contract workers in addition to its full-fledged staff. They serve meals and clean offices. They write code, handle sales calls, recruit staff, screen YouTube videos, test self-driving cars and even manage entire teams -- a sea of skilled laborers that fuel the $795 billion company but reap few of the benefits and opportunities available to direct employees.
Earlier this year, those contractors outnumbered direct employees for the first time in the company's twenty-year history, according to a person who viewed the numbers on an internal company database. It's unclear if that is still the case. Alphabet reported 89,058 direct employees at the end of the second quarter. The company declined to comment on the number of contract workers.
Earlier this year, those contractors outnumbered direct employees for the first time in the company's twenty-year history, according to a person who viewed the numbers on an internal company database. It's unclear if that is still the case. Alphabet reported 89,058 direct employees at the end of the second quarter. The company declined to comment on the number of contract workers.
Some places use contract hiring for entry level positions to essentially avoid paying benefits to otherwise full time staff. At a laboratory with lots of 'early career' scientists I worked at, the contracts weren't even uniform; if you knew somebody that needed a job you wanted to refer them to the 'good' contracting agency, as if you referred them directly to management they'd bring them in through the 'bad' contracting agency that had crappier terms, no PTO, etc. It is different than in software where the contractors are short term and set contracts favorable to them.
The thing is, there is a fine line between being a genuine contractor, and being an off-the-books "employee".
And Google could get in a lot of trouble if they turn out to be the latter.
The problem is that though the line is, fine, it is not fixed. It is generally determined on a case-by-case basis. In order to be a contractor:
* You are expected to know how to do your job. If it's something you have to be taught to do (more than a bit of reasonable orientation), you're probably an employee.
* You are expected to set your own hours. If you have to be there 9 to 5, or punch a time clock, or fill out a time card, you're probably an employee, not a contractor.
* You negotiate your own rates.
There are a few others. These rules are enforced by the IRS and a few other Federal agencies, but mainly the IRS.
IBM and rather famously Microsoft were both busted for having "off-the-books employees" which they called contractors. It cost them big.
Don't get stuck being an off-the-books employee. If you are, the company probably owes you back benefits.
And setting your own hours is not enough. You must have control over them. Even simply reporting the hours you worked to a client, in some circumstances, can be considered prima facie evidence of your status as an employee.