Skip to main content

7 of the world’s most powerful tech companies have been accused of forming an antitrust conspiracy.

7 of the world’s most powerful tech companies have been accused of forming an antitrust conspiracy to suppress the compensation of their employees by entering into “no poach” agreements. Today, a San Jose judge heard a motion to dismiss a class action civil lawsuit in which former employees seek damages from defendants Apple, Google, Adobe, Intel, Intuit, Pixar, and Lucasfilm.

The damning evidence against the defendants from a 2010 Department of Justice investigation that I first uncovered last week, as well as the plaintiffs’ opposition statement indicate there is more than sufficient evidence for the dismissal to be denied and the case to proceed towards trial. If the defendants lose to or settle, tens of thousands of full-time employees with the companies between 2006 and 2009 could be compensated.

[Update 4:30pm PST 1/26/2011: Judge Lucy Koh says "This case is moving forward...this case is going to survive the motion to dismiss." That means the defendants' motion to dismiss the case will almost surely be denied when the judge files her official ruling soon. Koh said she may dismiss some specific claims but the plaintiffs will be allowed to amend their complaint. She mentioned "It's hard to make the inference that there was no conspiracy". Read on to find out why and what that means for the companies. More details from the hearing at the end.]

Specifically, the senior executives of the defendants, including Apple’s Steve Jobs and Google’s Eric Schmidt, are accused of entering into a network of identical, interconnected illegal agreements not to recruit each other’s employees. Each agreement by itself may be a violation of antitrust laws including the Sherman Act, the Cartwright Act, and other California laws.

The plaintiffs also claim the agreements constitute an overarching antitrust conspiracy because each was made with knowledge of the other agreements, and relied on the other agreements to achieve a common goal of reducing compensation and mobility for highly sought-after skilled tech employees.

According to the plaintiffs’ statement (PDF), the chronology of some of the agreements is as follows:

  • January 2005 – Pixar senior executives (which include Steve Jobs) draft written terms for a no-poach agreement and send them to Lucasfilm
  • May 2005 – Apple and Adobe make agreements
  • 2006 – Apple and Google make agreements shortly after Eric Schmidt joined Apple’s board of directors
  • April 2007 – Apple and Pixar make agreements
  • June and September 2007 – Google enters into agreements with Intuit and Intel that are identical to the agreements between Apple and Google, Apple and Adobe, and Apple and Pixar

Additionally, Steve Jobs personally contacted Palm’s CEO Edward T. Colligan to propose an unlawful agreement, writing “We must do whatever we can” to stop competitive recruiting efforts between the companies.” Colligan declined Jobs’ offer, writing “Your proposal that we agree that neither company will hire the other’s employees, regardless of the individual’s desires, is not only wrong, it is likely illegal.”

The plaintiffs request “The Court should deny the motion, lift the stay of discovery, and permit Plaintiffs ‘to secure the just, speedy, and inexpensive determination’ of this action.”


The defendants claim that the agreements were isolated and not interconnected. They claim the agreements were pro-competitive parts of legitimate collaborations between the companies, many of which had executives on each other’s boards or started as the same company as with Pixar and Lucasfilm.

The defendants also claim “The alleged bilateral arrangement provide no support for the overall conspiracy that plaintiffs have alleged in order to name the defendants in a class action”. They motion for continuation of the partial stay of discovery and for the case to be dismissed.

However, my research and sources indicate the defendants’ claims are false, the plaintiffs case is plausible, and so there are no grounds for dismissal. Furthermore, the only reason more evidence about the interconnection between the agreements isn’t available is because they were made so secretively.

The case should be allowed to proceed because the plaintiffs have produced “smoking guns” indicating a deep conspiracy. Specifically, “Do Not Cold Call” lists which defendants used to implement the agreements, and the written terms of Pixar’s agreement with Lucasfilm. These signal that today’s joint motion to dismiss the case should be denied because if discovery is permitted to continue, there’s a reasonable expectation that evidence of illegal activity will be revealed.

Finally, the precedent is that motions to dismiss are “viewed with disfavor and are properly granted only in exceptional cases…A complaint satisfies Twombly [is only eligible for dismissal] if the allegations, taken as a whole, are not ‘facially implausible’” according to the plaintiffs’ statement. Therefore, it would take a very strong presentation by the defense for Judge Lucy Koh to dismiss the case.

If the defendants’ motion to dismiss the case is denied, the case will move towards a trial by jury in June 2013. Rather than leave an assessment of damages to the judge and jury, the defendants may try to settle the case, similar to how they settled with the Department of Justice’s federal case in 2010. In the defendants lose or settle, full-time employees of the defendants could be compensated for the 10-15% of lost wages estimated by the plaintiffs’ law firm Lieff Cabraser.

Update 4:30pm PST 1/26/2012: The judge has lifted the stay of discovery, saying “This case is moving forward…this case is going to survive the motion to dismiss.” Though her official statement hasn’t been filed, she’s likely to deny the defendants motion to dismiss the case. She also ordered Google to produce draft emails in addition to sent emails, and designate which are drafts and which were sent.

During the hearing, the defense argued against the conspiracy accusation and joint liability. It stated that plaintiffs don’t deserve compensation from companies they never worked for and that their employers didn’t have agreements with just because they were part of the so-called conspiracy.

The judge seemed somewhat sympathetic to this, and asked if the plaintiffs would consider breaking up the case to focus on each unlawful agreement separately. The plaintiffs maintained that the agreements were all interconnected.

Afterwards, The head attorney representing the plaintiffs, Joseph R. Saveri of Lieff Cabraser, told me the plaintiffs were comfortable moving forward with their single, joint antitrust conspiracy complaint. The plaintiffs will file an amended complaint that removes any claims dismissed by the forthcoming judge’s statement.

Next, another Case Management Conference is set for April 18th, where that amended complaint from the plaintiff will be reviewed. On June 28th, the court will convene to hear class certification to define what employees are eligible to be represented by the class action lawsuit. The plaintiffs plan to assess evidence surfaced during discovery and determine if only software engineers, software engineers and scientists, or all of the defendants’ employees will be represented by the class action lawsuit.

Following the hearing, Saveri gave reporters a conservative calculation of the possible damages that employees could be compensated for. He said software engineers make $100,000 a year (they make more), their compensation was “suppressed between 5 and 10%” and “tens of thousands of employees were affected”. That means for each year an entry-level full-time software engineer worked at one of these companies, they might be entitled to damages of $5,000 to $10,000. Higher paid veteran engineers could be entitled to much more. The total damages could therefore be at least $150 million if just 10,000 entry-level engineers were affected.

www.zanox.com

If you liked this article, subscribe to the feed by clicking the image below to keep informed about new contents of the blog:

windows_xp

Comments

Popular posts from this blog

How to change the size of the touch and on-screen keyboard in Windows 10

Windows 10 PCs come with two keyboard apps, one is the OnScreen Keyboard , and the other is the Touch Keyboard . Basically, you don't need a touch screen to use the on-screen keyboard. It displays a virtual keyboard on the screen and you can use the mouse to select and press the keys. Although the on-screen keyboard app is very useful when we don't have a physical keyboard, its size is always a problem for users. You can move or enlarge the virtual keyboard from the icons in the upper right corner. If you want, you can also easily resize it. Changing the size of the on-screen keyboard is very easy. Type On-Screen Keyboard in your Windows search and run the desktop app, or you can also go via Settings > Ease of Access > Keyboard> Turn on the On-screen keyboard.   To change the size of the on-screen keyboard, move the cursor to the corner and drag it to the desired size. Resizing the touch keyboard is as simple as doing it! Just drag it and resize it us

Designing the Windows 8 touch keyboard.

When we began planning how touch and new types of PCs might work on Windows 8, we recognized the need to provide an effective method for text entry on tablets and other touch screen PCs. Since Windows XP SP1, which had Tablet PC features built in, Windows has included a touchable on-screen keyboard. But those features were designed as extensions to the desktop experience.  For Windows 8, we set out to improve on that model and introduce text input support that meets people’s needs, matches our design principles, and works well with the form factors we see today and expect to see in the future. I’m writing this blog post on our Windows 8 touch keyboard using the standard QWERTY layout in English. As I look at it, the keyboard seems very simple and sort of obvious. This comes partly from having worked on it for a while, but also because keyboards are familiar to us. But there is more here than meets the eye (or, fingertips). We started planning this feature area with no preconcei

How to install offline .NET Framework 3.5 on Windows 10 using DISM.

Windows 10 comes with .NET framework 4.5 pre-installed, but many apps developed in Vista and Windows 7 era require the .NET framework v3.5 installed along with 4.5. These apps will not run unless you will install the required version. When you try to run any such app, Windows 10 will prompt you to download and install .NET framework 3.5 from the Internet. However, this will take a lot of time. You can save your time and install .NET Framework 3.5 from the Windows 10 installation media. This method is much faster and does not even require an Internet connection. Here is how to install it. How to install offline .NET Framework 3.5 on Windows 10 using DISM. Contents: [ hide ] How to install offline .NET Framework 3.5 on Windows 10 using DISM. To install .NET Framework 3.5 in Windows 10, do the following: Insert your Windows 10 DVD, or double click its ISO image, or insert your bootable flash drive with Windows 10, depending on what you have. Open 'This PC' in File