I don't understand what you're trying to say here. In my experience, on both sides of this, a good deal of thought is put into what kind of position to seek / offer. I think employers and workers think a lot about which legal arrangement would work better and there is a great deal of choice involved.
For instance, I can imagine Uber offering jobs v.s. contractor positions with differing levels of support, remuneration, and expectations. That they don't do so seems like a choice to me?
Legally, in California, they can't do that. As outlined in the article, the 'ABC test' is the legal test for determining whether someone is an employee or a contractor. The 'B' part of that test is "The worker performs work that is outside the usual course of the hiring entity's business." If you are an employer, you could not have one group of drivers that you classify as employees and the other you classify as contractors, not if they're basically doing the same work.
Note this is common in a lot of different businesses, and there have been many lawsuits where contractors who DID want to be classified as employees argued that they were basically doing the same work as employees. There was a fairly famous case involving Microsoft 2 decades ago: https://www.computerworld.com/article/2589538/it-personnel-m...
Being a contractor is not fundamentally bad if US hadn’t tied medical insurance and companies hadn’t tied stock bonuses with employment. Technically there is no such need for “employment”. You go work for the time and you get paid equitably without an artificial status called “employment”. Unfortunately this status has became part of many arcane laws and difficult to get rid of.
That's not the fundamental difference in either federal law or the California ABC test. It's not a factor in the ABC test, [0] and it's one of several factors in the “relationship” prong of the federal test. [1]
[0] https://www.californiaemploymentlawreport.com/2019/03/unders...
[1] https://www.irs.gov/newsroom/understanding-employee-vs-contr...
Edit: Good article and video about how AB5 affects technology consultants: https://www.viodi.tv/2019/11/15/will-ab5-drive-software-engi...
I think that's case by case though. Contractors usually do finite focused projects and don't want to be employees. I myself was self-employed for 5 years doing specific contracts as a software engineer. I was "writing code" which is "the same work" as employees. Were all those companies breaking the law?
> Legally, in California, they can't do that.
Definitely wrong.
This is actually a really good thread, because most people are surprised to discover that yes, those companies probably were "breaking the law".
As other posters pointed out, AB5 is relatively new, so the test is relatively stricter now, and only relevant in California.
More importantly though, employment classification is only challenged when a plaintiff files a lawsuit. Thus, even if someone is technically misclassified, if the relationship is mutually beneficial, nobody is going to complain. This goes on all the time, which is why most people are surprised to find out they were technically misclassified.
Case in point: I worked at a company (in a state much more permissible regarding employment law than CA, and pre AB5) that forbid using the term "contract-to-hire", even though that happened pretty frequently. Reason being that technically contract-to-hire is not legal unless there is a substantial difference in the work and relationship when the person is a contractor. Now, many times there is, but that phrase alone can make it seem like the work contractors do is too similar to the work employees do, which is why our legal department banned the phrase.
I'll give a Dutch perspective (which perhaps applies to some degree to other parts of Europe):
Until 2016, clients had to proactively ask for a 'Verklaring Arbeidsrelatie (VAR)'. An 'explanation of the work relationship'. If I understand correctly, the contractor/freelancer had to prove that they had more clients than just that one, and it had to be reasonable. So no having five clients of which one accounted for 99% of all income.
If a client didn't ask for this 'VAR', it could cause problems down the road.
From 2016 on they changed this, but apparently the result has been a confusing mess, so in 2021 they'll try to clear up some of it.
Practically speaking, as a contractor, I've found that only the big clients (with legal teams, I imagine) would ask for a VAR, if at all.
Most of the time, whether working in Holland or Germany, I usually did the exact same work that their employees did. In some cases there seemed to be vague distinction where I worked on shorter projects and they did support and the like, but in practice that distinction was very blurry.
I suppose with some of these clients I could've caused trouble, but because I got paid well, often better than the full-timers (even with insurance and all that deducted), I didn't see any reason to.
My general impression is that NL is a bit more 'liberal' in these matters than many other parts of Europe, so I'd be curious to hear how this works in France/Germany/Italy, etc.
In Sweden, if you want to become contractor, you have two options - start a limited liability company of which you owns all shares (Aktiebolag). Or you can start a business in your own name (Enskild firma), which legally is not separate from your own liabilities.
In the first case, you are making yourself employed by the corporation you own. I do not know if there is any legislation that prevents that business from having just a single customer. But I know that in my own case, my business have had a single customer the entire time it has existed.
But I strongly suspect that this is one of those 'spirit of the law' situations. So I suspect that a company that doesn't want, well, liability, would avoid hiring an LLC that really is just one person working only for said company.
AB5 is looser than preexisting law, since it adopted the preexisting ABC test from the Dynamex decision, but added new exceptions.
There is no advantage to the individuals from that decision, nor is there any intended.
So people spending 5 years working for the same company doing the same commute and same work as employees, subject to the same kind of control over their work etc., cannot maintain a claim to be self-employeed for the tax flexibility that goes with that.
However. You "writing code" as a contractor is not the same work as an employee if the manner in which you are doing it differs.
For example, if you have to purchase your own equipment, set your own hours, work on a "statement of work" basis instead of set hours, can substitute a subcontractor to do your work for you, and can and sometimes do work for multiple companies at the same time, and often switch the site at which you are working, those sorts of things signify that you are not operating as an employee would, and that it would be correct to classify you as running your own business and therefore subject to business taxation instead.
Of course every contractor wanted to claim that status for the tax benefits, which are basically less income tax and the ability to deduct more expenses. The government saw this and decided, although the law was what it was all along, people weren't applying it adequately. So they changed who does the assesment, and the tax liability if they get it wrong, from the contractor to the company hiring them. This is called the IR35 reform; IR35 is the name of the legislation that sets out what kind of working patterns must be treated as employment for tax purposes.
Although the reform will change who is liable for making the assessment, in principle it is still possible for a contractor to be retroactively assessed for their past as having been an employee all along, and have to pay back-tax. That's because you are supposed to have done the right assessment for yourself already, or perhaps your accountant should. This seems unlikely for most people now as long as the changes are followed through, but some people have been caught out by it.
The AB5 law has only been in effect since Jan 1.
The federal rules are already very strict. Generally contractors violate them a lot. The law was pushed by IBM to eliminate competition, and the feds incorrectly thought they would get more tax money by making the software contractor industry into employees. It's a sordid tale ending in domestic terrorism and murder: https://www.nytimes.com/2010/02/19/us/19tax.html
I’m not convinced you have adequately eliminated other potential reasons he may have done the uncharacteristic thing he did. Even if he was in his right mind, I’m not convinced he had anyone’s interest at heart but his own personal one, as jobs are a form of social control. He desired to be free of this control. Even if individual liberty is worth fighting for, the Constitution doesn’t grant you the right to the job you want on the terms you want. That’s what the courts are for.
This guy was wrong to do what he did in every way but for the right reasons in a very minor way that is more a matter of principle rather than tax law. No matter his beef, it was just his own, and as such, it doesn’t justify so much as slapping someone’s hand, let alone the stunt he pulled.
I do see your point, though I disagree.
I'm not clear what point you are referring to. It's possible for all sides in a story to be wrong in their actions.
AB5 essentially codified the test the California Supreme Court adopted in Dynamex (April 30, 2018), though.
> Definitely wrong.
Based on what? Were you a contractor while AB5 was in place? Everything I have seen suggests that Uber and Lyft will be legally prevented from having drivers that are classified as contractors.
So, for instance, you might hire initially a contractor to create the encrypted part of your product, but once you had hired someone to do that work full time you would be legally barred from hiring additional contractors to do that?
Pretty much, though even then it is determined by what the courts decide is the company's "normal course of business." Obviously there are big gray areas here. And, also obviously, there are many cases where both the worker and the employer would prefer to treat the relationship as a contractor relationship, and if they both agree there is nobody to file a lawsuit contesting it (unless, of course, there are lots of people in the exact same role who could challenge the classification, as is the case with Uber).
Also, note while there are federal rules that determine IRS classification, California has stricter laws when it comes to employee vs contractor.
I don't know about Uber in US, but in Russia this is how it typically works. Drivers are hired by local taxi companies, which partner with large-scale Uber-like aggregators. This way, user-facing (aggregator) companies don't have drivers as employers, but contract other companies (or individual drivers, shall they want to act as sole proprietors) for the actual transportation services.
That is exactly how software development contract jobs are handled in the US. They are called contract companies (and many other names) but essentially find talent, place them at a contract position, then bill the company for that contractor. They pay the contractor directly, with or without benefits (W-2 vs 1099). And in most cases, the contractor gets to choose contract or employee status with the contract company, although at different pay.
Here is an example of Postmates doing it, I wouldn’t be surprised to see Uber doing the same.
You've effectively spend a few paragraphs adding nothing of value to the conversation.
You've effectively restated the grandparent's points, but tried to do so in an adversarial manner.
You might want to check what you consider "adversarial" when it comes to a discussion forum.
The issue is that the comment I responded to seems to be under the false notion that workers (or employers, for that matter) get to "choose" how they want to be classified, and that's what this debate is about. My point is that, when it comes to employment law, a worker or employer's preference about how they are classified does not factor in at all about how the law classifies the job.
If I owned slaves and called them unpaid indefinite interns the law would rightly disagree. You can call the relationship whatever you like, but the law is there to keep the playing field level for everyone. That it's taken Uber so long to play by the same rules as everyone else is a travesty and should take a billion dollar law suit or two for damages to sort out.
They are independent contractors in the sense that they can choose how much and when to work.
They are employees in that they cannot negotiate rates.
I don't think it's so clear cut.
Hmm... How is an Uber driver different from a plumber here?
Let's say Google needs some pipes fixed at one of its offices and they tell me how much they'll pay, refusing to budge from that figure. That doesn't make me Google's employee. I can choose to do the work for that price, or I can go fix Apple's pipes instead. What am I missing?
The driver doesn't have the ability to turn up a dial and say "I'm going to charge more now".
(This isn't the only distinction between an employee and contractor though of course)
A licenced taxi driver cannot do that, either.
If instead, my analogy were that I was a general contractor who built water slides and a water park put out a bid on construction of a water slide and refused to negotiate, my only option is to take that bid or leave it. Why does it matter what the water park is going to charge the people to ride the slide?
Now that the app driving companies turned over the apple cart by essentially cyber-squatting on the legal system while backed by high power lawyers paid by VC cash, the driving companies themselves want to cry foul when they don’t get the way they bought and paid for. I guess what they didn’t foresee is the long view of judgeship, and their concomitant dim view of cheaters, no matter the problem domain.
It’s too ironic to be believed. The judges apparently agree with me.
"I'm afraid you're repeating Uber's favorite talking point, which is that everyone should respect the worker's decision to be an employee or contractor."
I've never seen Uber argue that everyone should "respect the worker's decision to be an employee or contractor." I have seen them argue that drivers are contractors based on the flexibility in the job, but not that it should be "the worker's decision".
"Nobody disputes that Uber can have employees or contractors (or both), or that drivers should, in principle, be able to choose what status they hold."
Actually, pretty much all US employment law disputes that drivers should be able to choose what status they hold. Employee vs. contractor is not determined by what an employer says someone is, or what an employee says they are. Instead, it is determined by some key factors about the nature of the job, which (as you do point out) mainly centers around control of important aspects of the job.
But it is important to understand that you never really get to "choose" whether you're a contractor or an employee, it's determined solely as a function of the type or work you do and the nature of your relationship to the employer.