On Tang Tan's alleged interview-room playbook, Chang Liu's post-departure cloud access, and what a 400-person talent pipeline looks like from the defendant's chair.
Apple's lawsuit against OpenAI names specific people doing specific things. The complaint is alarming.
Anti-AI
00
Skeptic
02
Neutral
00
Pro (practical)
02
Pro (hyped)
00
← Anti-AI · Pro-AI →
More than 400 former Apple employees now work at OpenAI. OpenAI's hardware initiative is run by Tang Tan, who until recently was a VP at Apple. These facts were not in dispute.
On July 10, Apple made them the foundation of a federal lawsuit.
What the complaint actually says
The lawsuit was filed in Northern California federal court. Three defendants: OpenAI, Tang Tan, and Chang Liu — a former Apple senior electrical engineer, now working on OpenAI hardware. The allegations against each are different, and specific.
Against Tang Tan: Apple claims he directed Apple employees interviewing at OpenAI to share Apple secrets as part of the interview process itself. Per the complaint as reported by CNBC, he also circulated an Apple offboarding document — one he either retained from his own exit or somehow obtained after leaving — to teach new OpenAI hires how to avoid triggering Apple's exit security checks.
Against Chang Liu: Apple claims he kept a work-issued Apple laptop after his departure. He allegedly discovered a bug that let him continue accessing Apple's cloud file storage months after he'd left. And while employed at OpenAI and working on hardware there, he downloaded dozens of confidential Apple files.
The materials at issue: product designs, manufacturing processes, and supply chain strategies for upcoming products.
The alleged sequence
- Pre-2026
400+ hires flow from Apple to OpenAI
OpenAI builds out its hardware team from Apple alumni, eventually including VP-level hire Tang Tan as hardware chief.
- Ongoing
Interview process used to extract secrets, Apple alleges
Tang Tan allegedly directed job candidates interviewing at OpenAI to share Apple confidential information as part of the process.
- Ongoing
Offboarding doc circulated
Tan allegedly distributed an Apple exit document coaching new OpenAI hires on how to avoid Apple's departure security checks.
- Post-departure
Chang Liu keeps Apple work laptop
Liu allegedly retains his Apple-issued device after leaving the company.
- Post-departure
Cloud bug exploited for months
Liu allegedly discovers a bug giving him continued access to Apple's internal cloud storage and downloads dozens of confidential files while employed at OpenAI.
- July 10, 2026
Apple files federal suit
Complaint filed in Northern California federal court naming OpenAI, Tang Tan, and Chang Liu as defendants.
Source spread
- CNBC — Apple sues OpenAI alleging trade secret theft — builder. Most complete on the complaint specifics: the 400-employee figure, Tang Tan's alleged interview instructions, Liu's laptop and cloud access behavior.
- Bloomberg — Apple sues OpenAI for trade secret theft — skeptic. Characterizes it as a "blockbuster case" and notes the scope: product designs, manufacturing processes, supply chain strategy.
- TechCrunch — Apple sues OpenAI over alleged trade secret theft — builder. Independent verification of the key claims; confirms the Northern California federal court filing.
- Axios — Apple sues OpenAI, trade secret theft — skeptic. Frames the 400-employee figure as the structural context; notes OpenAI has not responded publicly.
Pros & cons
What's documentably alarming:
- The allegations are specific, not generic. "Coordinated theft through job interviews" and "exploited a cloud access bug to download files" are the kind of detailed claims that suggest Apple believes it has evidence behind them.
- Companies sue companies. They name individual executives as defendants when the evidence is specific enough to justify the personal exposure. Apple named Tang Tan — a current VP-level OpenAI exec. That's a signal.
- The scope — product designs, manufacturing processes, supply chain strategy — is exactly what OpenAI would need if it's serious about building custom hardware. The motive is legible.
What to hold loosely for now:
- These are allegations in a complaint that Apple wrote. Nothing is proven. OpenAI will respond, and the response will matter.
- High-profile IP suits between tech companies have a long history of settling quietly, with no trial and no admission. This may never reach a verdict.
- Four hundred people sharing an employer doesn't mean four hundred people stole anything. The 400-employee figure is context, not evidence. The actual complaint focuses on two individuals.
What builders need to know
- If you're building software on top of AI, this is mostly background noise for now. The case targets hardware-layer IP — product designs, manufacturing processes, supply chain strategy. API builders and software product teams aren't the direct target.
- If you're hiring from device or semiconductor companies for AI hardware work, your IP intake process is now a risk surface. The complaint specifically names the interview as a vector. What you ask, what you document about what new hires can and can't use, and how long you quarantine certain prior-employer-relevant work matters.
- Watch the OpenAI response. They haven't said anything publicly as of July 13. A quick settlement offer implies thin evidence and a desire to avoid discovery. A vigorous defense implies they believe the complaint doesn't hold. The posture matters.
- Discovery, if this goes that far, will be worth reading. The documents produced could reveal how Apple's exit process actually works and how OpenAI's hardware hiring operated in practice. That's useful information regardless of the verdict.
Further reading
- CNBC — Apple sues OpenAI alleging trade secret theft — most complete on the complaint specifics
- Bloomberg — Apple sues OpenAI for trade secret theft in blockbuster case
- TechCrunch — Apple sues OpenAI over alleged trade secret theft
- Axios — Apple sues OpenAI, trade secret theft
- Forbes — Apple Claims OpenAI Stole Trade Secrets — summary with executive perspective
Liked this? Get the weekly digest.
Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.
Your take
How'd I do on this one?
What did I miss?
Tell Samwise (and Sam).
Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.