The AI Talent Trade War

Venture funded artificial intelligence companies now write trade secret and employee mobility protections into engineering offer letters because competitors have started paying signing bonuses as large as the $100,000,000 offers Sam Altman said Meta Platforms extended to OpenAI researchers in 2025. The legal toolkit available to a company defending its engineering roster has narrowed to trade secret law, confidentiality and invention assignment agreements, and carefully scoped non solicitation clauses, because the noncompete clause, the tool these companies used for two decades, lost its remaining federal backing when the United States District Court for the Northern District of Texas vacated the Federal Trade Commission’s noncompete rule in Ryan LLC v. Federal Trade Commission on August 20, 2024, and the Commission withdrew its own appeal of that ruling in September 2025.

California had already made the point moot for any company hiring engineers who might someday live or work there. Business and Professions Code section 16600, in force in its current form since 1941 and traceable to Civil Code section 1673 enacted in 1872, voids an employment noncompete outright, and Senate Bill 699 and Assembly Bill 1076, both effective January 1, 2024, extended that rule to out of state employers and created a private right of action with a $2,500 statutory penalty per violation. Minnesota banned noncompetes entirely under Minnesota Statutes section 181.988, effective July 1, 2023. Massachusetts kept the noncompete alive under General Laws chapter 149, section 24L, but only for a company willing to pay garden leave of at least half the employee’s recent base salary for the restricted period, a model Google’s DeepMind unit in the United Kingdom has adopted on its own initiative, placing some departing researchers on paid leave for as long as a year.

Two lawsuits now pending in the Northern District of California, X.AI Corp. v. OpenAI, Inc. and Apple Inc. v. Liu, show what happens when this body of law meets a mass lateral hire rather than a single departing engineer. United States District Judge Rita F. Lin dismissed X.AI Corp.’s claims in February 2026 because the complaint described only the conduct of departing employees, not conduct by OpenAI itself, and gave X.AI Corp. until March 17, 2026 to replead. Apple’s July 2026 complaint against OpenAI, naming OpenAI’s Chief Hardware Officer Tang Tan and former Apple engineer Chang Liu, alleges that more than 400 former Apple employees now work at OpenAI and seeks an order forcing design changes to hardware Apple says depends on misappropriated Apple technology. A venture funded company reading these cases correctly will conclude that the offer letter, the confidentiality agreement, and the exit checklist, not a noncompete clause, now carry the entire legal weight of protecting an engineering team’s work product from a well funded competitor’s recruiting campaign, and the balance of this report sets out exactly what each of those documents needs to contain and why.

Background and History

Trade secret law and noncompete law developed along separate tracks for three centuries before the artificial intelligence hiring wars of 2025 and 2026 forced them to work together inside a single offer letter. The noncompete clause descends from English common law, where the courts of the early eighteenth century treated any restraint on a tradesman’s ability to work as void unless the restraint was reasonable in scope and supported by consideration, a rule the English courts articulated in Mitchel v. Reynolds, decided in 1711. American courts imported that reasonableness test wholesale, and for most of the twentieth century a state court asked only whether a noncompete’s geographic scope, time limit, and subject matter were no broader than necessary to protect a legitimate business interest such as customer relationships or confidential processes. California broke from that consensus earlier than any other state. The California Legislature voided employment noncompetes outright in Civil Code section 1673 in 1872, decades before Silicon Valley existed, and carried the rule forward into Business and Professions Code section 16600 when it recodified the state’s business statutes in 1941. Legal historians, most prominently Ronald J. Gilson in a 1999 article in the New York University Law Review, have argued that this nineteenth century statutory accident, not any deliberate industrial policy, gave California’s technology sector a labor mobility advantage over Massachusetts’s Route 128 corridor, where noncompetes remained enforceable and engineers could not move as freely between competing firms.

Congress had a specific, practical reason to act in 2016 rather than leave trade secret protection entirely to the states. A company whose trade secret traveled across state lines, as training data, model weights, and engineering talent routinely do, faced a choice among fifty different versions of the Uniform Trade Secrets Act, each carrying its own case law on what counts as a reasonable secrecy measure, and no federal forum guaranteed to apply a single, predictable standard. The Defend Trade Secrets Act solved that coordination problem without displacing the state statutes; a plaintiff today can still bring a state law claim under the California Uniform Trade Secrets Act alongside a federal claim under 18 U.S.C. section 1836 in the same complaint, and most trade secret plaintiffs do exactly that.

Trade secret law took a parallel but distinct path. American courts protected confidential business information under common law tort principles for more than a century before the American Law Institute codified the doctrine in the Restatement of Torts in 1939, and most states later adopted some version of the Uniform Trade Secrets Act that the Uniform Law Commission approved in 1979 and amended in 1985. California’s version, the California Uniform