Job search
Inventions Assignment Agreements Before a Tech Job: Document Your Existing Side Projects
Organize existing project facts, separate later plans and prepare focused questions about the actual agreement for qualified counsel.
Before reviewing an inventions assignment agreement for a tech job, prepare five factual fields for each existing side project: its scope, dated records, contributors, resources and earlier agreements or licenses needing review. Keep that inventory separate from a conclusion that you own a project or that it qualifies for an exception. A repository name alone cannot answer those questions.
Aim to give qualified counsel a clear record and a focused set of questions. LandOffer publishes this guide; when you research recent tech roles, leave time to review the actual agreement packet before making commitments. Sources were inspected October 22, 2026. All project examples below are synthetic. No agreement was signed, repository changed, private code uploaded or professional contacted, and this article does not determine ownership, licensing rights or whether an exception applies.

Identify the actual agreement and its attachments
Gather the version you received, any referenced prior-inventions schedule, confidentiality provisions, outside-activity policy and other incorporated documents. Record the document titles and dates. An offer letter that mentions an assignment agreement is not a substitute for reading that agreement and its attachments.
Find the sections defining inventions, describing assignment, requesting earlier work and addressing material incorporated into future company work. Mark relevant clause numbers and unresolved terms without deciding their legal effect. Also record any governing-law or location-related language for counsel to evaluate; do not assume your home address alone answers which rules apply.
An inventory prepared for review is not automatically the employer’s completed disclosure schedule. The form may ask for statements about ownership, licenses, completeness or excluded work that go beyond your factual notes. If you cannot confidently explain a field, keep a question beside it rather than filling it with a broad assertion.
Record dates, contributors and resources separately
For each project, distinguish your recollection of when work began from the earliest retained note, commit, release or public announcement you can identify. Record what each item actually shows. A public release date describes publication of that version, not necessarily the date every component was created.
List the people and organizations involved, their described contributions and the supporting records. Separate your own changes from collaborators’ work and external dependencies. Being the repository administrator or the person presenting the project does not, by itself, complete the legal review of everyone’s rights.
Resources deserve their own field: devices, accounts, cloud credits, data, equipment, facilities and any work performed under another arrangement. This lets a reviewer ask about a specific input instead of relying on the project’s broad description. Do not reduce that field to “personal laptop.” The relevant questions can include the source of data, a collaborator’s contribution, an earlier employer’s agreement or work related to a consulting engagement.
Record public and private material differently. A public URL can identify a version for discussion; private code or an agreement should not be placed in a public repository just to create a convenient evidence link. Preserve only material you are permitted to retain and use an appropriate private review channel when needed.
Worked inventory: Beren describes an existing project without claiming an exclusion
Beren is a fictional engineer preparing to review an agreement before a proposed job start. His synthetic project, CacheMosaic, is a small local-first log-viewing exercise. The label refers to no actual repository in this article. The dates, collaborators and records are invented.
He completes this inventory rather than writing “all personal projects are mine”:
| Field | Completed factual entry | Boundary or question |
|---|---|---|
| Project description | Local-first log viewer with a parser, filter interface and test fixtures | Description does not claim patentability or ownership |
| Beginning of work | Beren recalls February 2024; earliest retained design note is February 11 | Recollection and retained record are separate |
| Version evidence | Earliest retained commit record April 2, 2024; first public version June 20, 2024 | These dates describe identified records; the earlier history and individual components still need their own evidence |
| Contributions | Beren describes parser, interface and tests; Lio contributed documentation | Review contribution records and any associated agreements |
| Resources | Personal device and account are noted; origin of one sample-data file is unresolved | No conclusion that personal equipment resolves all rights questions |
| Other material | External charting dependency appears in the project | Identify the applicable version and license for review |
| Earlier obligations | A previous consulting agreement may cover part of the development period | Obtain the permitted agreement copy and ask counsel about relevance |
| Review baseline | Inventory describes the version recorded October 21, 2026 | Planned later features are not silently included as existing work |
His completed project description for the review packet is:
CacheMosaic is a synthetic local-first log-viewing exercise. This inventory describes the October 21, 2026 review baseline and the earlier records listed above. I describe my contributions as the parser, interface and tests, with documentation contributed by Lio. The sample-data source, dependency terms and relevance of an earlier consulting agreement remain unresolved. This is a factual working inventory for review, not a representation that I hold every right or that the project is excluded from an assignment agreement.
Beren’s next questions are specific: which evidence should accompany the inventory, how should an unresolved component be described, and what statements would the actual employer form require? He has a useful packet without converting uncertain facts into a signed representation.
Read what a prior-inventions schedule actually asks
A publicly filed Firefly Neuroscience agreement dated September 9, 2026 illustrates why the attachment matters. Section 2.2 describes a prior-inventions list in Exhibit A, gives meaning to an incomplete or empty list, and separately addresses incorporating prior material into company work. This is one individual employer document, not a model that governs every tech employee.
The example also demonstrates that listing earlier work and reviewing later incorporation are different tasks. A project’s appearance in an inventory does not let this guide decide what a later license or consent clause means. Ask counsel to review the actual wording, definitions and related attachments together.
Treat the public exhibit as an illustration of requested fields. Its completed entries and checked boxes do not describe your projects. Your task is to understand the statements requested in your own packet. A factual list, a legal representation and an agreed exclusion can be different things; the record should make clear which stage you have reached.
Keep jurisdiction and intellectual-property categories visible
The official text of California Labor Code section 2870 contains conditions concerning an employee’s own time and employer resources, together with exceptions involving the employer’s business or research and development, or work performed for the employer. The page identifies a 1991 amendment. It was inspected as currently displayed on October 22, 2026; it is a California statutory example, not a nationwide “personal device means personal ownership” rule.
Whether a jurisdiction’s rules apply to an individual, how they interact with an agreement and whether facts meet a condition require qualified advice. The inventory helps make that discussion concrete. It does not choose the governing law or certify a project’s status.
The USPTO’s MPEP section 301, marked revision January 2024, discusses patent assignment and licensing separately. It also explains that recording an assignment is not an Office determination of the document’s validity or ownership effect. This patent-specific guidance does not decide a software project’s copyright, license, patentability or employment-agreement questions.
Worked questions: Sora separates existing components from later plans
Sora is another fictional engineer. Her synthetic SignalShelf exercise contains a schema browser and a small visualization. She is considering future improvements after a proposed job start, but has not made those changes, used employer resources or submitted any disclosure in this example.
She completes a component review record:
| Component or issue | Current factual record | Question prepared for counsel |
|---|---|---|
| Schema browser | Described in retained 2025 notes and an existing public version | How should the existing version and its boundaries be described in the actual schedule? |
| Visualization module | Includes a collaborator’s contribution | Which contribution or agreement records are needed before making a rights statement? |
| External dependency | Package and version can be identified; terms have not been reviewed | Which license information should be included, and what needs separate review? |
| Proposed exporter | Only a sketch; no implementation exists | How should a future plan be distinguished from existing work? |
| Possible use at a future employer | An idea, not permission or an implementation | Which incorporation, consent or licensing clauses would need review first? |
| Existing obligations | Earlier project-related agreement is listed but not assessed | How might that document affect the statements requested now? |
Her full unsent question draft is:
I am preparing a factual inventory before reviewing the proposed inventions assignment agreement. For SignalShelf, I can identify the existing schema-browser version, my described contributions, a collaborator’s module and an external dependency. The proposed exporter is only a sketch and is not part of the existing implementation. Could you advise which records are needed to review the requested prior-work statements, how to identify unresolved contribution or license questions, and how the agreement treats future development or incorporation into employer work? Please also identify which jurisdictional and earlier-agreement questions require review. I have not submitted this inventory as a completed exclusion schedule or authorized any transfer or use.
The completed result is a set of component-specific questions. Sora does not infer that a public repository permits every future use, that a collaborator’s work belongs to her, or that writing down a planned feature protects it. Those are precisely the conclusions she has left for review.

Prepare a review packet without changing the underlying history
Keep the original agreement and inventory as separate documents. Use stable identifiers already available for the version you are describing and label any later correction to your notes. Do not alter repository history, contribution records or dates to make the timeline look cleaner.
Include a short index of evidence rather than a large unfiltered export. An adviser can then identify what additional material is appropriate to review. Where information is confidential or subject to another obligation, note that a record exists and ask about a permitted way to describe or provide it. Do not assume that an employer’s generic attachment request authorizes disclosure of someone else’s private material.
Separate the factual questions from proposed contract language. “I cannot identify this data file’s source” is a useful unresolved fact. “This entire project is exempt” is a different statement that the inventory has not established. Keeping those categories apart reduces the risk that a working note is mistaken for a conclusion you intended to make.
Leave the meeting with identified next steps
A useful review can clarify which documents remain missing, which facts need verification and who is authorized to answer questions about the employer’s process. Record the agreement version, the project version described, the unanswered clause or field and the person responsible for the next clarification. A recruiter’s acknowledgement of a list is not, by itself, a conclusion this guide can treat as an agreed exclusion.
Before committing to a role found through LandOffer’s recent listings, prepare a project inventory like Beren’s and a component question record like Sora’s. Keep unknowns visible, distinguish existing work from future plans and bring the actual agreement packet to an appropriately qualified adviser. Use the review to identify which entries are supported facts, which statements need further advice and which documents remain missing.
Sources and Further Reading
- California Labor Code section 2870: official statutory text, jurisdiction-specific; displayed amendment 1991, inspected October 22, 2026.
- USPTO MPEP section 301: patent ownership, assignment and recordation guidance, revision January 2024.
- Firefly Neuroscience agreement dated September 9, 2026: individual public employer example, including section 2.2 and Exhibit A; not a universal form.


