Apple just made poaching AI talent a legal problem

If you have hired anyone from a big tech company lately, or you are about to, Apple just changed the math. The fight with OpenAI is not only about two engineers. It is a warning shot to anyone building a team by pulling talent from a rival. Let me catch you up on what shifted and what to watch.

The two names on the complaint

Apple filed a trade secrets lawsuit against OpenAI, and it went straight at the top. The complaint alleges misconduct reaching OpenAI's chief hardware officer and says more than 400 former Apple employees now work there.

The two people named are Tang Yew Tan and Chang Liu. Tan was Apple's VP of Product Design and is now OpenAI's Chief Hardware Officer. Liu was an iPhone engineer who left at the start of the year. Apple's claim is simple: these people carried confidential hardware knowledge with them, and OpenAI used it to build the consumer device it is now working on. OpenAI denies it.

Forty letters, one message

The lawsuit is only the front door. Apple also sent legal preservation letters to roughly 40 former employees now at OpenAI, telling them to save any documents or messages tied to their old jobs.

That is about 10 percent of the ex-Apple people at OpenAI. In its filing, Apple called the two named employees "just the tip of the iceberg." Read that as a message to the other 38 people: we are watching your work, and you may face discovery requests. It is a cheap way to freeze people in place and make anyone think twice before touching their old projects.

The timing that stings

OpenAI is reportedly eyeing an IPO as early as later this year, which makes this lawsuit land at the worst possible moment. A trade secrets case hanging over your hardware roadmap is exactly the kind of open question that spooks bankers and buyers.

OpenAI's public response has been careful and hedged, which tells you their lawyers are steering the tone. If you are planning around either company's device timeline, treat it as soft. A drawn-out case can slow hiring, slow product, and push a public offering to the right.

Where the people are actually going

The talent shuffle runs both ways, and not all of it ends in court. Ryan Beiermeister left OpenAI after two years as VP of Product Policy and joined Founders Fund as a partner. Her exit was messy, tied to a scrapped ChatGPT "adult mode" feature, but she walked into a clean landing on the VC side.

The lesson for you is about kind of move, not just company. Beiermeister carried policy judgment, not product blueprints. That travels freely. The Apple case is about specific hardware knowledge tied to specific projects. Know the difference before you extend an offer.

The deep cut

The risk is not the senior hire everyone reviews. It is the mid-level engineer or designer who joins your team and starts working on something close to what they built at their last job. Apple did not sue over resumes. It sued over people touching adjacent work. So the practical move is boring and it works: when you hire from a competitor, write down what that person will not work on for the first year, and keep them off any project that maps to their old one. Do it before day one, not after a letter shows up.

Three questions for your team

• For our last five hires from competitors, can we show they are not working on the same thing they built before?
• If a preservation letter landed on one of our new hires tomorrow, do we have clean records showing they brought nothing over?
• Which parts of our roadmap depend on OpenAI's or Apple's device timeline, and what is our backup if that slips a year?