Can your job interview notes be used in court?

Can your job interview notes be used in court?

Yes — interview records are discoverable, and a US federal court has just ordered a company to produce them. On October 13, 2026, Judge Edward Davila in San Jose granted Apple expedited discovery against OpenAI, its hardware company io and two former Apple employees, including production of OpenAI's materials for interviewing candidates who came from Apple. OpenAI got five days to hand over documents it had already collected and 14 days for the rest. Nothing has been decided yet about whether anyone actually took Apple's trade secrets; this is a discovery ruling, not a verdict. But the practical message for anyone interviewing while employed is blunt: your interview left a paper trail, and somebody else can subpoena it.

The order spells out what "interview materials" covers, and it's broader than most candidates imagine — interview checklists, guides, instructions, manuals, scripts, technical presentations, and records showing discussions of Apple technology or components. Apple also won access to private LINE messages involving two OpenAI employees who previously worked at Apple, plus depositions of those two and of OpenAI's chief hardware officer, a former Apple vice president. The judge refused several other requests, including research on metal finishes and power management and broad questions about what ex-Apple staff have built since joining, calling the requests onerous as written while leaving Apple free to narrow them and come back. A hearing set for the following day was taken off the calendar.

Buried in Apple's complaint is the allegation that should make every working candidate sit up: that former Apple employees already inside OpenAI coached prospective hires on what to bring to their interviews, and that one executive asked candidates to bring actual parts for a show-and-tell. Those are allegations, not findings, and OpenAI disputes the case in full. But look at the mechanism rather than the headline. What's being fought over isn't a stolen server — it's what people said and showed in a room, and what somebody typed up afterwards. My blunt view: candidates obsess over hiding their employer's name and barely think about the one specific number they blurt out in minute 40 of a technical screen.

Yes. Interview notes, interviewer guides, recruiter scorecards and internal chat messages are ordinary business records, and a court can order them produced in litigation.

Which hiring records survive long after you interview?

Hiring records outlive your application by years, and in the US keeping them is a legal duty rather than a filing habit. Employers with 15 or more staff must retain personnel records — applications, CVs, interview notes, test papers, reference checks — for at least a year after the relevant hiring decision or the date the record was made, whichever is later. That obligation covers rejected candidates too, not only the person hired. State and local government employers, educational institutions and many federal contractors work to a longer two-year window. And the moment a discrimination charge or lawsuit arrives, the retention clock stops mattering entirely: every record connected to the dispute has to be preserved until the matter is fully resolved.

Then there's everything the law doesn't even require. Your applicant tracking system keeps each CV version you ever uploaded, timestamped. Interviewers file structured scorecards with free-text comments. Recruiters trade impressions in email and chat. Take-home assignments, portfolio links, screen-share recordings and auto-generated transcripts all sit in cloud storage with nobody's finger on the delete key. If a note-taking bot joined your video interview, there's a verbatim record of your answers — worth knowing what the consent rules are when an AI note-taker sits in on an interview, because the transcript belongs to whoever pressed record, not to you.

Two consequences follow, and they're different in kind. The legal one: a single sentence about your current employer's unreleased work can be pulled out of a scorecard years later and quoted back at you under oath, stripped of all context and tone. The commercial one is more immediate and affects far more people. Those notes get read by the next panel, the hiring manager and the compensation committee, and an interviewer's parenthetical — "spoke freely about confidential roadmap" — quietly kills offers without ever being shown to you. Discretion in an interview isn't a compliance exercise. It's a hiring signal, and strong candidates get credit for it.

What counts as a trade secret you can't mention?

A trade secret is information that has independent economic value precisely because it isn't generally known or readily discoverable, and that your employer has taken reasonable steps to keep secret. That second half is what trips people up. The test isn't whether a document was stamped confidential; it's whether the information is commercially valuable in the dark and guarded in practice — through access controls, confidentiality agreements and enforced policies. So the unannounced product you're building, the yield rate on a part that hasn't shipped, the pricing formula, the vendor terms, the customer list and the internal benchmark numbers are all candidates for protection. Your own skills, judgment and professional reputation are not. Nobody can contract away your right to describe what you're capable of.

In practice the line sits at specificity plus non-public status. Safe ground: publicly announced products, published papers, granted patents, open-source work you contributed to, the problem classes you've solved, the methodologies you use, team size, and your own role and scope. Dangerous ground: unreleased features and timelines, architecture diagrams and schematics, exact performance or defect figures tied to unshipped work, model training details, named clients with their spend, and internal strategy such as pricing changes or acquisitions. Physical artifacts are the brightest line of all. Never bring parts, source code, slide decks, sample files or screenshots from your employer to an interview — that's the conduct that turns a hiring dispute into a misappropriation claim.

Your new role matters as much as your words. When the two employers are direct competitors and the job is closely comparable to the one you're leaving, some state courts will entertain an argument that disclosure is effectively unavoidable, though federal trade secret law bars injunctions that simply stop someone from taking a job, and states such as California reject the theory outright. The courts genuinely diverge here. What you can control is the record you create: if you're moving to a rival, say plainly that you'll honor your confidentiality obligations and won't bring material with you. The scripts for explaining a move to a direct competitor are worth rehearsing before the first call, not after.

How do you quantify impact without naming proprietary systems?

Swap the proper noun for a category, and keep the number. That single move solves most of the problem: "Led data migration for a top-five global payments processor" carries the same credibility as naming the client, and it survives a lawyer reading it. Recruiters are assessing scale, ownership and outcome, not brand trivia — nobody rejects a strong bullet because the employer appears as "a Fortune 100 consumer electronics manufacturer." Scrubbing the company name while leaving a precise figure attached to an unshipped product is the worst of both worlds, and it's exactly what most confidential CVs do. The identifying detail is rarely the name. It's the number bolted to something the market hasn't seen yet.

Three rewrites cover nearly every case. First, generalize the system: "an internal order-routing platform" instead of its codename. Second, convert sensitive absolutes into relatives — "reduced p95 latency by 40%" or "cut deployment time from hours to minutes" rather than raw throughput that reveals business volume. Third, lead with your mechanism instead of the design: what you decided, who you aligned, what broke and how you fixed it. That's also the layer interviewers actually score. If you keep a dated log of what you shipped, turning those records into quantified CV bullets is mostly editing — and the same log helps you prove impact without reaching for protected specifics.

Two refinements worth adding. If your current search has to stay quiet, list your employer as a descriptor rather than a name — "Confidential — enterprise SaaS, 2,000+ staff" — and expect to name it once you're in the room. And if a project genuinely can't be generalized, give it two bullets about your role, scope and method, flag that details are restricted, and let your non-restricted work carry the proof. When you're ready to redraft, an AI CV builder that rewrites achievements into measurable bullets makes the generalize-but-keep-the-metric pattern much faster to apply consistently across ten years of history.

What are three safe answers to "what did you build?"

Use one of three templates: scope-and-constraints, transferable-method, or decline-and-redirect. The first is your default. It sounds like this: "I led a team of nine on a new payments integration — regulated environment, hard latency budget, three upstream dependencies we didn't control. I owned the rollout plan and the on-call rotation, and we shipped on time with no customer-visible incidents." Notice what's there: team size, constraint, ownership, outcome. Notice what isn't: product name, vendor, dates relative to launch, internal metrics. Nine times out of ten the interviewer wanted the judgment, not the schematic, and you've just given a cleaner answer than the candidate who overshared.

Template two is for technical depth. Describe the method as you'd describe it to a conference audience: the problem class, the approaches you considered, the trade-off you chose and why, and what you'd do differently. "We were deduplicating events across regions with clock skew; we moved from timestamp ordering to a monotonic sequence per producer, which cost us some write throughput and bought us correctness." That's genuinely informative and genuinely generic. Template three is the refusal, and it must be explicit rather than evasive: "That one's unreleased, so I can't go into specifics — but I can walk you through how I approached a comparable problem earlier in my career." Then actually walk them through it.

Say the boundary out loud once, early, and don't apologize for it. Interviewers read a clean refusal as professionalism; they read a long, detailed answer about an unannounced product as a preview of how you'll treat their secrets later. The same discipline applies to what you're asked to bring: offer a clean-room portfolio you built yourself, a public repository or a written case study, never files or hardware from work. Before you send anything, pressure-test the document — a free CV analysis that scores ATS compatibility and clarity will show you how your achievements read to a machine and a stranger, which is usually where the overshare is still sitting in plain sight.

Frequently asked questions