If you're recruiting engineers, product leads, or salespeople out of a direct competitor, your exposure starts in the interview, weeks before anyone signs an offer letter. The riskiest room isn't always the exit interview. Sometimes it's a 45-minute technical screen run by a hiring manager who has never read a trade-secret statute.
On July 10, 2026, Apple filed a complaint in the Northern District of California against two former Apple employees, OpenAI, and io Products (Apple Inc. v. Liu, No. 5:26-cv-07078). Much of what it describes isn't a file transfer. It's a hiring loop. Apple alleges that a former vice president, now OpenAI's chief hardware officer, used an internal Apple project codename to ask a candidate "What's the plan[?]" about an unannounced product, and that candidates still working at Apple were directed to bring "Actual parts," "CAD/design artifacts," and "prototypes" to interviews for "show and tell" sessions and to describe their "subsystem and component selection."
Here's where the case stands, verified as of August 4, 2026. On August 3, Apple moved for a preliminary injunction and for expedited discovery; a hearing is set for October 1 before Judge Edward Davila, with opposition briefs due August 17. No defendant has answered or moved to dismiss. Nothing has been adjudicated, and no court has accepted either side's account.
OpenAI has publicly disputed the allegations; no defendant has responded in court. OpenAI published an official statement on August 3 saying the injunction request is "based on false information and completely unnecessary because we do not have, nor want, any of their trade secrets." On the February 2026 contact Apple describes, OpenAI's account is that Apple's outside counsel emailed the wrong person after confusing two last names, apologized the next day, and never raised the suit's specific allegations at the time. In OpenAI's words, "We then heard nothing for five months until they sued." Keep four categories apart. Apple's allegations are allegations. OpenAI's version is a party's public statement, not a filed pleading, supported by emails it selected and redacted, and OpenAI acknowledges Apple contests the sequence. The procedural facts above are the undisputed part. Judicial findings: none, on anything.
The Controls That Run Before the Offer
Your company will never be a party to this, and it still lands on your desk. The alleged conduct isn't exotic espionage. It's a recruiting process without boundaries. Six controls fix that, each a document or a step somebody owns by name, because a control nobody can produce a record of is no control. Be honest about the reach, too: these cut documentary contamination, the parts and files and drives. What a senior hire carries in memory, pricing structures, roadmap sequencing, vendor terms, gets handled through role scoping and assignment, not a checklist.
1. A one-page recruiting boundary for interviewers. Don't ask about a current employer's project codenames. Don't accept parts, prototypes, design files, or documents. Don't ask for vendor or supplier specifics. That list tracks the conduct at the center of the Apple complaint. Owner: whoever runs the loop.
2. A written instruction to the candidate, sent before the first substantive interview. No bringing, sharing, uploading, or discussing confidential information from a current or former employer, and no prior-employer devices or accounts for anything touching your role. Send it as a message you can retrieve later. Owner: the recruiter.
3. Two paragraphs in your paperwork. The first is an affirmative representation in the offer letter or IP agreement that the hire has not retained and will not bring prior-employer materials. It helps show you set a boundary and communicated it. It does not protect a company whose actual conduct contradicts it, and no clause cures solicitation, knowing receipt, misuse, ignored warning signs, or an employee acting inconsistently with what they signed. Aim it at materials, not at where the person can work next. The second is the whistleblower-immunity notice under 18 U.S.C. Section 1833(b)(3). Its consequence is narrower than founders assume: skip it and you may not be awarded exemplary damages or attorney fees under Sections 1836(b)(3)(C) and (D) in a DTSA action against the employee who didn't get the notice. "Employee" covers contractors and consultants here, and the requirement reaches agreements entered into or updated after the DTSA took effect in 2016. It doesn't automatically eliminate state-law, contractual, or unrelated remedies, and it isn't a reason to paste one paragraph into every template without asking what that agreement covers. Owner: whoever owns the templates.
4. Device and account hygiene as a named onboarding step. Prior-employer hardware never touches your network. Personal drives and personal email don't get bulk-imported. Someone signs off in writing on day one. Owner: IT, with a named backstop.
5. A response scaled to documented risk, decided before the offer goes out. Most competitive hires don't need a clean room. Assess the hire using facts you can identify: technical overlap, seniority and prior access, prior hires from that competitor, how closely the new assignment resembles the old one, warning signs in the recruiting process, and any indication that material has already moved. Document the operational facts, the controls selected, and who owns them. When those facts raise a material legal question, involve counsel before recording legal conclusions or characterizing the hire as high risk; copying counsel on an ordinary business assessment does not by itself make the record privileged. Lower-risk hires may need only the written boundary and ordinary onboarding. Higher-risk hires may require documented independent-development procedures, access restrictions, or a changed assignment. A formal clean room belongs to the unusual cases at the top of that range. Owner: the engineering lead, with the hiring manager.
6. A named owner for escalation, with written triggers and a first move. Triggers: unsolicited confidential material from a new hire, a preservation or demand letter, several hires from one competitor in a short window, or someone proposing a way around a prior employer's exit process. The first move matters as much as the trigger, because the state statutes below reach acquisition. If material arrives, quarantine it, stop circulation and review, preserve it, route it to counsel, and write the sequence down with times. Owner: one person, named.
What Changed, and Why It Reaches the Interview
The complaint pleads six claims: misappropriation counts under the Defend Trade Secrets Act against the individual and corporate defendants, and breach-of-intellectual-property-agreement counts against the two former employees. Apple asks for an injunction, compensatory damages, exemplary damages, and attorneys' fees.
Those last two come from the statute, not the complaint. Under 18 U.S.C. Section 1836(b)(1), the DTSA gives a trade secret owner a private federal cause of action. Section 1836(b)(3)(C) makes exemplary damages of up to twice the compensatory award available only where the trade secret is "willfully and maliciously misappropriated," and attorneys' fees under subparagraph (D) rest on that same finding. Recruiting hard is not misappropriation. But evidence that solicitation was institutional rather than one manager's bad call can strengthen an argument that misappropriation, if it is found, was willful and malicious. That finding is the gate the bigger numbers sit behind.
Maryland and DC both follow the uniform-act model. Under Maryland Commercial Law Section 11-1201(c) and D.C. Code Section 36-401(2), misappropriation includes the acquisition of a trade secret by someone who knows or has reason to know it was acquired by improper means. Use is not required. So if a prototype crossing your conference table embodies trade-secret information, and your side knows or has reason to know it came through improper means, acquisition alone may satisfy the statutory definition even if nobody ever builds anything with it. Every link has to hold: the physical item, the information embodied in it, whether that information qualifies as a trade secret, whether the means were improper, and only then the separate questions of use or disclosure.
Section 1836(b)(3)(A)(i) says a DTSA injunction may not "prevent a person from entering into an employment relationship," and that conditions on employment "shall be based on evidence of threatened misappropriation and not merely on the information the person knows." Maryland's highest court rejected the inevitable-disclosure theory as a basis for injunctive relief under the state trade secrets act (LeJeune v. Coin Acceptors, Inc., 381 Md. 288, 849 A.2d 451 (2004)). That holding governs Maryland state-law claims. It doesn't set the federal standard, and it doesn't travel: hire someone who lives elsewhere, or hire away from a competitor headquartered elsewhere, and the prior employer's forum and choice-of-law clause may put another state's answer in front of you. District of Columbia courts have not clearly resolved the doctrine.
Why It Matters for Business Decisions
The mistake is treating "no noncompete" as "no restriction." Maryland voids noncompete and conflict-of-interest provisions for employees earning at or below 150 percent of the state minimum wage, and for certain licensed health-care workers providing direct patient care at or below $350,000 in annual compensation (Maryland Labor and Employment Section 3-716). The District generally bars them outside a "highly compensated employees" category tied to a threshold that adjusts annually with the Washington-area consumer price index, with a cap on length and disclosure requirements (D.C. Code Section 32-581.01). Federally, no rule bans noncompetes today: the FTC's 2024 rule was vacated in court and formally removed from the Code of Federal Regulations in a February 2026 Federal Register notice, though the agency has said it will still pursue case-by-case enforcement against unfair noncompete use under Section 5. None of that touches trade secret law. A candidate can be free to take your job and still create real exposure through what they bring into it.
Clustered hiring changes the shape of the problem. Apple sued a chip startup in 2022 over roughly 40 to 50 former system-on-a-chip engineers who joined in a short window; that case terminated in March 2024 after the parties reported a settlement. There Apple alleged both a pattern of coordinated recruiting and confidential files retained after exit. Concentration widens the factual surface and makes "isolated incident" a harder thing to say.
Say the counterpoint plainly: a competitor can sue a company that did everything right, and heavy process will cost you candidates you wanted. A documented process cannot prevent a lawsuit or guarantee a shorter one. What it can provide is an earlier, more credible account of the boundaries the company established, the controls it followed, and how it responded when a problem surfaced.
Decision Framework
1. Who asks your technical interview questions, and who trained them? If the answer is "whichever senior engineer is free," you have no boundary yet.
2. Could you produce the instruction you sent to a competitive candidate this year? Not a handbook policy. An actual message, retrievable today.
3. What happens on a new hire's first day with their old devices and accounts? Walk the sequence: laptop, cloud drive, personal email, phone. Name who checks.
4. Can you show that your last release was built independently? Point to the artifacts, not to the intention.
5. If a competitor's counsel writes tomorrow, who opens the letter? A demand letter sitting in a founder's inbox for three weeks is its own fact in the case.
Audience-Specific Implications
For Founders
Your hiring wave and your product roadmap are the same exposure. Where the roadmaps overlap, settle the boundary and the risk call before the first offer; separating a team that has built together for two quarters is close to impossible. A pending claim also becomes a diligence disclosure in your next round.
For Business Owners and Operators
The controls live in workflows you already own: the interview loop, the offer template, the IT onboarding checklist, the escalation path. The decision is who owns each one and how the record is kept, written so a hiring manager can follow it on a Tuesday.
Practical Takeaways
- Get the interviewer boundary in writing before your next competitive loop opens. A rule written afterward has no record behind it.
- Treat the candidate instruction as missing until you can retrieve one you actually sent. The acquisition rule above is why: liability can attach where a recipient knew or had reason to know of improper acquisition, and a retrievable instruction is evidence pointing the other way.
- Audit every template that touches confidential information for the Section 1833(b)(3) notice this quarter, contractor and consultant forms included. Check what each agreement covers instead of pasting one paragraph everywhere.
- Assess a competitive hire before the offer goes out. Document the relevant operational facts, the controls selected, and who owns them. When the assessment raises a material legal question, involve counsel before recording legal conclusions or characterizing the hire as high risk. Independent-development evidence must be created while the work is being done, not reconstructed after a dispute begins.
- Capture design logs, requirement sources, and prior-art notes while the build is happening. Contemporaneous or reconstructed, and only one of those reads well in discovery.
- Name the escalation owner this week, tell them what a trigger looks like, and give them a script for the first hour. The February 2026 contact in the Apple case is itself contested, and a botched contact becomes part of the dispute instead of the thing that ended it. Even a company that denies soliciting, receiving, or using anything confidential can land in an expensive dispute when its interviewing, access, offboarding, and documentation controls are weak.
Closing Perspective
The defense you'll want eighteen months from now gets built during the interview. Not after the letter arrives. That's the whole lesson, and it's cheap: a one-page boundary, two paragraphs of template language, one onboarding step, a risk call you write down, one named owner.
What I keep coming back to is how ordinary the alleged conduct is. Asking a strong candidate to show you what they've built is a normal instinct for a founder trying to hire well. It's also the one that has to be trained out of a loop running against a direct competitor.
Nothing has been decided, and the two sides are telling the public very different stories about the same February emails. Once a dispute like this starts, you don't control which version of your own recruiting process gets told. Your window sits between the day you decide to recruit from a competitor and that person's first day, and it closes the moment they start building.
This article is for informational purposes only and does not constitute legal advice. Every company's situation is different, and you should consult with qualified legal counsel before making compliance decisions based on the developments discussed here.
