Your Day Job Might Own Your Startup's IP: The Clean Separation Playbook for Deep-Tech Founders

Reading Your PIIA Before the Risk Materializes

The document most founders sign on day one of a new job, buried inside an onboarding packet, is the one that can sink their startup years later. A Proprietary Information and Inventions Agreement (PIIA) assigns to your employer all right, title, and interest in inventions you conceive, develop, or reduce to practice during your employment. The standard clause does not limit that assignment to work you did at the office, on company hardware, or during paid hours. It covers inventions that relate to the employer's business, full stop.

Courts read that language broadly. California and federal cases have consistently held that "related to company business" reaches the employer's general industry or technology area, not just the specific projects you were assigned. In Cubic Corp. v. Marty, 4 Cal. App. 3d 209 (1970), and subsequent decisions, courts found assignment obligations on inventions the employer was not actively developing, as long as the technology fell within the company's broader field. If you spend your days at a semiconductor company and your nights building a novel sensor array, the "related to" test may well capture your sensor work, even though no one at your employer was working on that application.

Hardware and deep-tech founders face a structurally different exposure than software engineers. A developer can write code on a personal laptop, on personal time, with zero contact with employer systems. That clean separation is almost impossible in hardware. Physical prototyping requires components, test equipment, manufacturing access, and often conversations with colleagues who carry specialized technical knowledge. Each of those touchpoints is a potential "employer resources" argument. Even one is enough.

The Three Triggers, and Why Each One Is Sufficient

A standard PIIA captures an invention through any one of three independent triggers: you used the employer's time, you used the employer's resources, or you used the employer's confidential information. California Labor Code § 2870 provides a statutory carve-out, but it requires the invention to have been developed entirely on your own time, with no equipment, supplies, facility, or trade secret information of your employer. The word "entirely" is load-bearing. Using a company oscilloscope once, borrowing a supplier contact from a colleague, or sketching a design in a work notebook can each be enough to push an invention outside the carve-out and back into the employer's column.

Post-employment assignment clauses deserve special attention. Some PIIAs extend the assignment obligation 6 to 12 months beyond your last day, capturing inventions you were conceptualizing while still employed. If you left a job in January with a hardware idea already taking shape in your head, a clause like that potentially makes your former employer a co-owner of IP you filed in March. Reading that clause before you resign, not after you file your first patent application, is the difference between a clean cap table and an existential ownership dispute.

The Employer Resources Test: When 'Company Time' Is Less Clear Than You Think

California Labor Code § 2870 is the statute that carves out personal inventions from PIIA assignments. Founders treat it as a safe harbor. It is one, but the conditions are surgical. The carve-out requires that your invention was developed entirely on your own time, without using any employer equipment, supplies, facilities, or trade secret information. That word "or" carries most of the weight: contamination through any single vector destroys the entire carve-out, even if the other three are clean.

For a software founder writing code at home on a personal machine, satisfying all four conditions is demanding but achievable. For a hardware founder building physical prototypes, it is structurally harder. Hardware development requires components, bench equipment, manufacturing access, and technical knowledge drawn from a professional career. Each of those touchpoints maps directly onto one of the statute's four contamination vectors.

Equipment and Supplies: The De Minimis Trap

Most founders understand that using lab equipment at work to test a prototype creates exposure. Fewer recognize that the equipment vector reaches much further. Using a company-issued laptop once to look up a component supplier, opening a CAD file on a subsidized device, running a simulation on any hardware the employer owns or reimbursed: all of these are potential contamination events. Courts have not required that the equipment use be substantial. If the employer's equipment touched the invention, the carve-out is in jeopardy. The same logic applies to supplies: employer-owned components, raw materials, or consumables used in even one prototype iteration are a problem.

Devices purchased through employer discount or reimbursement programs present a specific risk. A "personal" laptop your employer subsidized at hire may be classified as employer equipment, depending on how the program is structured and how courts in your jurisdiction have analyzed similar arrangements.

The Confidential Information Vector: No Document Required

The most dangerous contamination path for hardware founders does not require taking anything. Under the trade secret framework incorporated into the § 2870 carve-out, "trade secret information" includes all forms of financial, business, scientific, technical, and engineering information your employer controls. That definition, drawn from 18 U.S.C. § 1839(3) and its state equivalents, covers the specialized knowledge you carry in your head: supplier relationships, proprietary testing methods, manufacturing tolerances, pricing structures, technology roadmaps.

Courts have found contamination where a founder used this kind of embedded knowledge to shortcut development, even without copying a single document. Mattel, Inc. v. MGA Entertainment (9th Cir. 2010) illustrates how PIIA assignment clauses can capture products conceived during employment. The 7th Circuit's decision in PepsiCo, Inc. v. Redmond, 54 F.3d 1262 (7th Cir. 1995) — the canonical inevitable-disclosure case — established that an employee's embedded technical knowledge can be so pervasive that its use in a competing venture becomes practically unavoidable. The mechanism is the same in hardware: if your deep-tech background at Employer A shaped how you designed your startup's architecture, a court can find that you used Employer A's trade secret information within the meaning of the statute.

California's § 2870 Carve-Out and the Six States That Copy It

California Labor Code § 2870(a) is the strongest statutory shield an employee inventor has in the United States. It voids any PIIA provision that purports to assign an invention the employee "developed entirely on his or her own time without using the employer's equipment, supplies, facilities, or trade secret information", as long as the invention does not relate to the employer's business or result from work performed for the employer. If you satisfy all four of those conditions simultaneously, your employer's PIIA cannot touch the invention, regardless of what the agreement says.

The operative word is "entirely." Not mostly. Not predominantly. Entirely. One afternoon of debugging on a company laptop, one Slack message asking a colleague for architectural feedback, one use of the company's AWS credits to run a test, and you have broken the statutory protection. The statute reads as a precision instrument: you either qualify or you do not, and courts apply it literally.

California also requires employers to tell you about § 2870. Under California Labor Code § 2872, any employer that includes an invention assignment clause in a PIIA must attach or reference the § 2870 text. If your employer did not do this, the assignment clause may be unenforceable. Check your agreement.

The Six States With Comparable Statutes

California is not alone. Delaware, Illinois, Minnesota, North Carolina, Washington, and Nevada have each enacted statutes that carve out employee inventions made without employer resources. That brings the total to seven states with statutory protection. If you signed your PIIA while living in one of these states, your analysis starts with the local statute, not just the contract language.

The differences between the seven statutes matter in practice. Washington's statute, RCW § 49.44.140, uses the same "entirely" standard as California — not a more permissive threshold. Illinois (765 ILCS 1060/2) and Delaware (Del. Code Ann. tit. 19, § 805) likewise track California's absolute "entirely" language. All three states apply the same rigorous standard and provide the same rigorous protection.

What the Statute Does Not Do

Even a clean § 2870 qualification does not make you safe on its own. The statute provides the legal framework, but you need documentary evidence to invoke it. That evidence is the prior inventions schedule, an exhibit attached to your PIIA that lists specific inventions by name, description, and date, and explicitly carves them out of the assignment. Industry-standard PIIAs from Y Combinator, the NVCA model documents, and major startup firms all include this schedule as a standard exhibit. Over-disclosure is safer than under-disclosure: list every invention you are reasonably confident predates or falls outside your employment scope. An omission is far harder to fix after a dispute starts than a complete list is to compile before you sign.

The next section covers the operational practices that make this protection durable: timestamped work logs, separate devices and accounts, and how to structure your prior inventions schedule to survive adversarial scrutiny.

Non-Competes and Moonlighting Policies

The federal non-compete ban is dead. In August 2024, a federal district court in Texas vacated the FTC's Rule on Non-Compete Clauses in Ryan LLC v. Federal Trade Commission (N.D. Tex. Aug. 20, 2024), and the FTC subsequently abandoned its appeal. The nationwide rule that would have voided all non-compete agreements for virtually every American worker is no longer operative law. State law controls, and the state-by-state map is hostile to founders in most of the country.

The State Landscape: Four Safe Havens and Forty-Six Variable Answers

Four states impose near-total bans on non-compete agreements: California (Cal. Bus. & Prof. Code § 16600), Minnesota (Minn. Stat. § 181.988, effective Jan. 1, 2023), North Dakota (N.D. Cent. Code § 9-08-06), and Oklahoma (Okla. Stat. tit. 15, § 219A). If your prior employer is in one of those states and you are too, a non-compete in your employment agreement is likely unenforceable. California went further with SB 699 (2024), codified at Cal. Bus. & Prof. Code § 16600.5, which extends the ban extraterritorially: out-of-state non-competes are unenforceable against California residents regardless of where the agreement was signed, and employees have a private right of action, including injunctive relief and attorneys' fees, against employers who try to enforce them.

Texas sits at the opposite end of the spectrum. Under Tex. Bus. & Com. Code § 15.50, a non-compete is enforceable if it is ancillary to an otherwise enforceable agreement and reasonable in scope, geography, and duration. The critical Texas-specific trap: courts will reform an overbroad non-compete rather than void it, as affirmed in Marsh USA Inc. v. Cook, 354 S.W.3d 764 (Tex. 2011). You cannot count on winning just because your employer's clause is aggressive. The court will rewrite it to a reasonable scope and enforce that version against you. Florida moved even further in 2025 with the CHOICE Act (HB 1023), which creates a rebuttable presumption that non-competes meeting basic durational and geographic requirements are reasonable, shifting the burden to you to prove unreasonableness.

Moonlighting Policies: The Underestimated Risk

Even if your non-compete is unenforceable, your employer's moonlighting policy may prohibit outside employment entirely, and violating it is independent grounds for termination and a potential duty-of-loyalty claim under the common law (Restatement (Third) of Agency § 8.04). The moonlighting risk is conceptually separate from both the IP assignment risk covered in prior sections and the competition restriction in a non-compete. You can have a clean prior inventions schedule, no PIIA contamination, and a non-compete that would never survive a court challenge, and still be fired for cause the day your employer discovers you are running a startup on the side.

NLRB guidance issued in 2023 noted that blanket policies prohibiting all outside employment without any approval process may be unlawfully overbroad under Section 7 of the National Labor Relations Act for non-supervisory employees. But employer-specific restrictions tied to legitimate business interests remain enforceable for most founders, who are typically supervisory or senior enough that Section 7 protection does not apply. The practical implication: read your moonlighting policy before you incorporate, not after. If it requires pre-approval for outside employment, get that approval in writing before you file your articles of organization. The conversation is uncomfortable. The lawsuit that follows an undisclosed startup is worse.

Building Clean Separation From Day One

The statutory protections and contractual carve-outs described in the preceding sections are real, but they share a common dependency: you have to be able to prove them. California Labor Code § 2870 gives you the legal right to exclude a qualifying invention from your employer's PIIA, but the statute does not prove itself. Courts have ruled against founders who had the right substantive facts — personal time, personal equipment, no trade secret use — and still lost because they could not produce contemporaneous evidence establishing those facts. The right without the documentation is a right you cannot exercise.

Documentation gaps are the primary reason founders lose IP disputes they otherwise would have won on the merits. That is not a speculative risk. The adversarial posture of an IP ownership dispute means the employer's litigation team will start with your weakest evidence and work forward. If your only record is your own testimony about what you did and when, a court has to weigh that against your interest in the outcome. Contemporaneous records — timestamped logs, receipts, commit history, calendar entries — have no such credibility problem.

Devices, Accounts, and Physical Equipment

The foundation of clean separation is hardware purchased before you join, on personal funds, from personal accounts. Every device, every component order, every cloud subscription for startup development should be traceable to a payment method your employer has no connection to and no subsidy relationship with. A laptop purchased through an employer's corporate discount or reimbursement program creates an equipment contamination argument, as discussed in prior sections, even if you intended it as a personal device. The safest practice is to acquire all development hardware before your start date and keep the receipts.

Account hygiene follows the same logic. Use a personal email domain — not your employer's domain, and not a free webmail account associated with your professional identity — for all startup communications, vendor relationships, domain registrations, and cloud service accounts from day one. If your startup's GitHub organization, AWS account, and supplier correspondence all route through a personal domain you control, the paper trail shows an unambiguous boundary. Switching accounts mid-development is technically possible but creates gaps that opposing counsel will highlight.

Timestamped Work Logs

Calendar records and commit timestamps are the most practical form of contemporaneous documentation available to a hardware or software founder. Block your startup development sessions on a personal calendar application — evenings and weekends, with enough specificity to show what you were working on. In hardware, supplement that with purchase receipts timestamped to non-work hours for components bought at local suppliers or ordered online. In software, git commit timestamps on repositories hosted on personal infrastructure provide a similar record automatically.

The purpose of this documentation is not primarily to convince a court that you never worked on your startup during business hours. It is to shift the evidentiary burden. Without records, the employer's theory — that you could have used company resources — is unopposed by anything other than your denial. With records, the founder's theory — that development demonstrably occurred on personal time — has affirmative support. That shift matters at every stage of a dispute, including settlement negotiations that never reach a courtroom.

Co-Founder IP Assignment and Chain of Title

Founders who hold startup IP in their own name — rather than assigning it to the company entity at formation — create a chain-of-title gap that surfaces as a serious problem in Series A due diligence. Every co-founder should sign an IP assignment agreement at entity formation, not at the raise. The assignment establishes that the company, not the individual founder, owns the technology the startup is built on. Investors require clean chain of title before they wire funds; a gap discovered during diligence delays closings, triggers renegotiation, and in some cases causes deals to fall apart entirely.

The Whitespace Memo

Beyond devices, accounts, and logs, founders should produce one additional document before development begins in earnest: a written analysis of why the startup's technology area falls outside the employer's current and reasonably anticipated business. Courts apply the employer's business as it exists and as it could reasonably develop — meaning a startup that operates in a space adjacent to your employer's roadmap faces greater exposure than one operating in a clearly distinct field. Writing out that analysis forces clarity about the risk before you are in litigation, and the document itself is evidence that you made a good-faith determination of non-overlap at the time of development, not a post-hoc rationalization constructed in response to a demand letter.

Pre-Departure Founder Checklist

The window between deciding to found a startup and submitting a resignation letter is the highest-risk period for IP contamination. Every decision made during that window — what hardware you use, which accounts you open, whether you disclose outside activity, whether co-founders have signed IP assignments — will determine whether you bring investors a clean cap table or a chain-of-title dispute. The checklist below organizes those decisions by phase so nothing is missed before you walk out the door.

1. Obtain and read your PIIA. Locate three things specifically: the assignment clause (and whether it is limited to current projects or extends to anything "related to the employer's business"), any post-employment tail provision (typically 6–12 months post-departure), and the prior inventions schedule. These three provisions determine your baseline exposure.
2. Check whether your employer provided the § 2872 notice. California Labor Code § 2872 requires employers to attach or reference the § 2870 carve-out text in any agreement containing an invention assignment clause. If your employer did not do this, the assignment clause may be unenforceable — consult employment counsel before you begin any development.
3. Complete your prior inventions schedule fully before you start building. List every relevant prior invention by name, description, and approximate date. Over-disclose rather than under-disclose. An omission discovered during diligence or litigation is harder to fix than a complete list is to compile before you begin.
4. Read your moonlighting policy. If it requires written pre-approval for outside employment, get that approval before you incorporate or begin development. This is an uncomfortable conversation, but violating an undisclosed policy is independent grounds for termination and a potential duty-of-loyalty claim — separate from any IP dispute.
5. Write a whitespace memo. Prepare a written analysis explaining why your startup's technology area falls outside your employer's current and reasonably anticipated future business. Draft it before development begins, not after you receive a demand letter. The document demonstrates a good-faith non-overlap determination made at the time, not a post-hoc rationalization.
6. Acquire all development hardware before your start date or on personal funds. Every device, component, and piece of test equipment should be purchased on payment methods your employer has no connection to. Devices purchased through employer discount or reimbursement programs — even if you consider them personal — create an equipment contamination argument under the § 2870 carve-out.
7. Use a personal email domain for all startup activity from day one. Vendor relationships, cloud service accounts, domain registrations, co-founder communications, and supplier correspondence should all route through an account your employer has no claim over. Switching mid-development creates gaps that are easy for opposing counsel to exploit.
8. Maintain timestamped calendar logs showing development occurred on evenings and weekends. Supplement with purchase receipts for components and materials timestamped to non-work hours. In software, git commit timestamps on personal infrastructure provide an automatic record. The goal is contemporaneous documentation that shifts the evidentiary burden — your denial alone is weak evidence; a corroborated paper trail is strong evidence.
9. Make no use of employer contacts, supplier relationships, or specialized technical knowledge derived from employment. The confidential information vector under § 2870 reaches embedded knowledge you carry in your head — proprietary testing methods, supplier pricing, manufacturing tolerances, technology roadmaps. Using that knowledge to shortcut development is a contamination event, even without copying a single document.
10. Execute a co-founder IP assignment agreement at entity formation — not at the raise. Every co-founder must assign all startup IP to the company entity before the first investor conversation. A chain-of-title gap discovered during Series A diligence delays closings, triggers renegotiation, and in some cases causes deals to collapse. For a well-structured founder agreement that covers IP assignment alongside equity splits and vesting, address this at the moment you form the entity.
11. Conduct a data wipe review before you leave. Confirm that no employer documents, emails, confidential files, or technical specifications have transferred to personal devices or startup accounts — even inadvertently through a forwarded email, a synced drive, or a screenshot taken during a meeting. Inadvertent possession of employer confidential information is still possession.
12. If your jurisdiction enforces non-competes, map the restriction before you give notice. Know the scope, geography, and duration of any non-compete clause. Know what competitive activity is prohibited and whether your startup's product and customer segment fall inside or outside that definition. Do not assume an aggressive clause is unenforceable — Texas courts reform overbroad clauses rather than voiding them; Florida's CHOICE Act shifted the burden to you to prove unreasonableness.
13. Have employment counsel review your exit and startup IP position before you resign. The engagement is inexpensive relative to what it protects. An attorney who reads your PIIA, your prior inventions schedule, and your whitespace memo before you give notice can identify exposure you missed and structure your departure in a way that narrows the employer's claims. The litigation is not inexpensive.

None of this is bureaucratic box-checking. Each item on this list represents a decision point where founders routinely create unnecessary exposure — not through dishonesty, but through moving fast without stopping to assess risk. An attorney who works through this list with you before your last day is not a formality; they are the person who determines whether your investor's counsel finds a clean chain of title or a problem that needs resolving before a term sheet can close.