|
|
|
|
|
by myalphabet
2199 days ago
|
|
Agreed. I'm generally uncomfortable with noncompetes and especially with Amazon's practice of making every employee sign one. Unless it's a really special case where a team is working on something truly groundbreaking and secret, I don't see what Amazon is really afraid of if some random developer leaves and goes to a competitor. However, I do have to say that their argument as stated in this article does seem like a valid case for a noncompete. From the article: >“Virtually every day, Hall worked with Amazon’s most senior cloud executives to create and execute those plans. As a result, he was entrusted with an unusually broad view into Amazon’s cloud product plans; its priorities; and its competitive strategy.” |
|
In contract law, this is known as "consideration". California has decided that "sign this or you won't get hired", isn't a valid form of consideration because it inhibits future earning potential, it's not (normally) mutually negotiated, nor is it negotiated on equal terms.
If companies really want it, they should pay for it.
Alternatively, if Amazon wanted to protect its market strategy, it should have made sure there was no ambiguity in this term. For example, if they had a narrow non-compete that says, you can't do cloud marketing or marketing strategy for Microsoft, IBM, or Google, it would hold much more standing because it's not overly broad.
As its written, where could he have gone and known for sure that that business wasn't a competitor? You can argue nearly every business is a competitor of Amazon. That's what makes it invalid.