· 7 min read

Apple Just Sent Legal Letters to 40+ OpenAI Employees. When a $3 Trillion Company Goes to War, Your Employment Agreements Just Became a Liability.

Lessons Building in Public AI

On July 10, Apple sued OpenAI. On July 17, Apple sent legal preservation letters to roughly 40 former employees now working at OpenAI. These aren't cease-and-desist notices: they're discovery grenades. And if you've spent time at a big tech company and you're now working as a consultant or independent operator, you need to understand what this means for your liability surface.

The lawsuit

Apple's complaint names two specific people: Tang Tan, a former VP of Apple product design, and Chang Liu, an engineer who worked on unreleased hardware products. The allegations are specific and damaging. Apple claims Tan systematically directed Apple employees interviewing at OpenAI to share internal secrets. Liu allegedly left with a company-issued MacBook he never returned. More interesting: Liu maintained ongoing access to Apple's internal file servers through a software vulnerability he discovered. His exact message, quoted in the lawsuit: "LOL, I found out I can access the [network storage], so funny."

The things allegedly stolen: hardware designs for unreleased products, manufacturing methods, supplier details, vendor specifications, the kind of information that directly informs product strategy and component sourcing.

Why preservation letters matter more than the lawsuit

The 40 preservation letters sent July 17 are the real signal. Preservation letters freeze evidence. They create a legal obligation on the recipient: don't delete anything, don't destroy records, don't alter documents. If you're one of those 40 people and you delete an email or wipe a device, Apple can argue obstruction of justice or spoliation of evidence.

This is pretrial discovery theater. Apple is signaling: we're not done. We believe more people are involved. We're building a case. The recipients of those letters now have legal exposure that extends beyond their employment relationship with OpenAI: their personal conduct is now at legal issue.

What this means for consultants and contractors

You know the non-compete clause in your employment agreement? The one you signed but never thought you'd actually have to worry about? It just became real.

Until this lawsuit, most indie operators treated non-competes as background risk: something an aggressive lawyer could enforce, but something big companies usually ignored as long as you weren't a C-suite executive or stealing code. You could leave a big tech company, take a consulting gig with a competitor, and feel reasonably safe because enforcement was expensive and imprecise.

Apple's lawsuit changes that math. When a $3 trillion company decides to make an example, they have the capital to do it. They can name names. They can send legal mail to dozens of employees. They can tie up people's time, money, and peace of mind for years. The fact that they might lose the suit doesn't undo the damage.

More importantly: other big companies are watching. If Apple wins (or even settles favorably), the template spreads. Google, Microsoft, Meta: they all have similar concerns about talent movement and secret protection.

The honest counter-take

Apple's lawsuit might lose. Big tech litigation is messy. Evidence gets disputed. Non-competes have mixed enforcement in California. OpenAI will likely settle quietly and deny wrongdoing. But even a settlement doesn't undo the fact that the people named in the lawsuit now have a public litigation record that follows them for years.

Future employers will see it. Client due diligence will see it. Background checks will see it. The stain is permanent.

The threat model shift

If you're working as an indie operator and you spent time at a big tech company in the last two years, your employment liability just increased.

Your risk zones: anything that looks like "I know how to do this because I worked at Apple" and you're now selling that knowledge to someone else. If your pitch to a client includes "I worked on hardware at Apple," or "I know their supply chain," or "I worked on product strategy at Meta," that's potentially knowledge that's protected by a non-compete or a trade-secret clause.

You might have a legitimate defense. Non-competes often require that you're actually competing with your old employer, not just working in the same field. Knowledge you learned through experience is generally harder to protect than trade secrets. But defense costs money. And uncertainty is expensive.

What to actually do

First: read your old employment agreements. Find the non-compete clause. Understand what it actually says. The boilerplate "you can't work in this industry for 12 months" is unenforceable in California, but specific restrictions on product categories or customer lists might hold up.

Second: if you're taking on a client, audit the engagement for risk. Are you selling knowledge that's directly tied to insider information? Are you competing with your old employer in the same customer segment? Are you using materials or methodologies you developed at that company? If the answer to any of these is yes, you need to either:

  • Get a written waiver from your old employer (rare, but possible)
  • Rebuild the knowledge independently (expensive, but defensible)
  • Decline the engagement (safest)

Third: add to your client contracts a clause that says you've disclosed any relevant non-compete or confidentiality obligations, and that your work is based on general industry knowledge, not proprietary information. This doesn't protect you from Apple, but it does protect you from your client claiming they didn't know about the risk.

Fourth: if you're a contractor or consultant now, and a big company came after you, you'd want legal representation immediately. This is not something you handle with a strongly-worded email.

The actual consequence for solo operators

The indie operator is not Apple's target. They're not suing you. But you're collateral damage in this war. You're now operating in a legal environment where big companies are more aggressive about enforcement, where the people you might hire or work with are more cautious about what they can share, and where "I worked at Google" is a more complicated credential.

That doesn't mean you can't work with ex-FAANG people. It means you both need to be conscious about boundaries. The people who build the best things often come from big companies. But the legal environment around that knowledge transfer just got a lot more expensive.

If you're positioning yourself as "the person who understands how big tech companies think," you're now also the person navigating a minefield of non-competes, trade secrets, and legal discovery.

Map the risk. Understand your specific exposure. And if you're hiring someone with big company experience, know that they might have legal obligations you can't see or override.

Author

Lukas

Sources

More Lessons articles →

Stay in the Loop

Get new posts delivered to your inbox. No spam, unsubscribe anytime.

Newsletter coming soon. Set PUBLIC_CONVERTKIT_FORM_ID in .env to activate.

Related Posts