Signal
Insights July 12, 2026

Apple Sued OpenAI Over 400 Hires, and Accidentally Published a Hiring-Process Audit

Apple's lawsuit against OpenAI alleges a competitor built its hardware recruiting pipeline out of confidential project code names, show-and-tell sessions with stolen components, and coached security evasion. Strip out the trillion-dollar names and it's a hiring-process failure every fast-growing company can make at a smaller scale.

Apple filed a 41-page lawsuit against OpenAI on July 10 in the Northern District of California, alleging trade secret theft and breach of contract. The headline number is 400-plus: that's how many former Apple employees Apple says are now working at OpenAI. The lawsuit isn't really about the number, though. It's about the mechanics, and the mechanics are the part every hiring manager should actually read.

Apple alleges that OpenAI's Chief Hardware Officer, Tang Tan — himself a former Apple executive — used Apple's internal, unannounced project code names during recruiting conversations, ran "show and tell" interview sessions where candidates still employed at Apple were asked to bring in hardware components and prototypes, and coached departing employees on how to evade Apple's security and exit procedures. Separately, Apple alleges that Chang Liu, an eight-year Apple senior systems electrical engineer, left for OpenAI without returning his company laptop, kept access to internal file servers through what Apple describes as a software bug that gave him continued access, and used that access after he'd already started at OpenAI to pull hardware designs, manufacturing details, and testing procedures. OpenAI's public response was a flat denial: "We have no interest in other companies' trade secrets."

Whoever is right on the facts (and this will take years and a jury to sort out), the complaint itself is a rare document. It's a competitor describing, in granular detail, exactly what its hiring pipeline looked like on the way to a 400-person raid. And what it describes isn't a recruiting strategy. It's an absence of one.

Aggressive hiring and reckless hiring are different postures, and the difference is process, not intent. Every company racing to build a team fast is going to hire people who used to work for a rival. OpenAI is racing hard, entering hardware for the first time after buying Jony Ive's io Products for $6.5 billion. That's not the violation. Poaching talent from a competitor is legal, common, and often the fastest way to build real capability. What turns it into a lawsuit is what happens in the room during the interview and on the laptop during the exit.

If Apple's allegations hold up, OpenAI's interviewers were soliciting confidential product information as a matter of practice, and nobody in a position to stop it did. That's not a talent-strategy problem. That's a missing hiring protocol, at a company valued in the hundreds of billions of dollars, doing something a 40-person startup would get right by accident just because nobody thought to skip it.

I see the smaller-scale version of what Apple is describing constantly, and it's exactly as avoidable. A company hires three engineers off a direct competitor in the same month because the interviews went well and the offers hit fast. Nobody scripted the interview to stay on the candidate's own work versus their former employer's roadmap. Nobody built an IP-boundary line into the interview guide. Nobody has an offboarding checklist that revokes system access same-day, retrieves hardware same-day, and gets a signed exit acknowledgment before the new-hire start date even gets scheduled. Six months later, the losing company's outside counsel sends a letter, and the hiring manager who was just trying to move fast is now explaining to the general counsel why the interview notes reference a competitor's unreleased roadmap by name.

That gap is a staffing function, not a legal afterthought bolted on after the fact. It's the same gap OpenAI is now accused of leaving open, just without the billion-dollar price tag on the other side. A recruiting process that scales with velocity has to build the guardrails in from the first interview: what an interviewer can ask a candidate about their current employer, what a candidate can and can't bring or reference, and a same-day offboarding runbook on the other end for anyone hiring from or losing people to a direct competitor. None of that slows down a good hire. It's the difference between "we hired someone great who used to work at a rival" and "we're now Exhibit A in a trade secrets complaint."

Apple is asking the court for an injunction, damages, destruction of any Apple material in OpenAI's possession, and a redesign of OpenAI's upcoming hardware so it doesn't infringe. The complaint is free due diligence: a checklist of everything a hiring process should have caught before a recruiter ever picked up the phone. The lawsuit is the audit. Read it before someone runs it on you.


VC5 Consulting helps technology companies build engineering teams without building legal exposure. We work with CTOs and technical leaders on hiring processes, interview design, and offboarding protocols that let you compete for talent aggressively — including talent at competitors — without turning your recruiting pipeline into a discovery request. If you're scaling hiring fast and haven't audited what happens in the interview room or on exit day, let's talk.