12960 Linden Church Road
Clarksville, Maryland 21029

Do Your Employment Agreements Say Who Owns What Your Engineers Invent?

Nov 18, 2026

You just hired your fourth engineer. The offer is signed, the start date is set, and nobody asked the question that may matter later: who will own what this person builds?

Suppose you run a 30-person technology company. Your engineers are writing the software that sets the company apart from its competitors. Their employment agreements were signed quickly, copied from a general template, or never reviewed again. Nothing has gone wrong, so nobody is worried.

Here is the question I would want answered before anything does go wrong: do your agreements with employees explain, in plain terms, what happens to the work they create?

Why It Comes Up at Hiring

Hiring is often the cleanest time to address ownership. The relationship is new, expectations are being established, and a clear agreement is a normal part of the process.

Wait until an engineer has been building for two years, and the same conversation becomes more difficult. You may then be asking someone to sign an agreement affecting work that has already been created.

At hiring, I would examine whether the agreement addresses the work the employee is expected to create and whether the language fits the employee’s actual responsibilities. An agreement written for a sales employee does not automatically fit an engineer building the company’s core product.

Federal copyright law generally places initial ownership in the author, subject to the work-made-for-hire rules. If a qualifying work is created by an employee within the scope of employment, the employer is generally treated as its author and owner unless a signed written agreement provides otherwise. 17 USCS § 201.

Please note that a job title or payroll status does not necessarily resolve every work-made-for-hire question. Courts use common-law agency principles to determine employee status under the Copyright Act, and whether particular work falls within the scope of employment can depend on the circumstances. Nationwide Mut. Ins. Co. v. Darden, 503 U.S. 318, 323 (1992).

A well-drafted agreement can also address assignment of rights that might not otherwise belong to the company automatically. The agreement should be tailored to the employee’s role, the expected work, and the law governing the employment relationship.

Why It Comes Up at Product Launch

A launch puts your software in front of customers, partners, and competitors. It also tends to put the product in front of other people’s lawyers.

Customers may ask whether the company owns what it is selling or licensing. A partner may ask the same question before integrating with the product. Those questions are easier to answer when the paperwork is organized and more stressful when the company must reconstruct the history under a deadline.

A launch may also disclose details about new work. Under federal patent law, public availability before a claimed invention’s effective filing date can qualify as prior art, subject to statutory exceptions. 35 USCS § 102.

Please note that not every launch discloses the same information or has the same legal effect. A public description of a product’s result may be different from a technical explanation of how the product achieves that result. The content, timing, audience, confidentiality restrictions, and potential countries of protection should be considered before the launch rather than after it.

Why It Comes Up When You Consider Protection

Some founders first think about intellectual-property protection when a competitor appears, an investor asks questions, or a potential acquirer wants to know what the company owns.

Perhaps the team built an internal platform that routes orders more effectively than available alternatives. Perhaps it developed a processing method that eliminates a manual step. Work like that may be commercially important and may justify an evaluation for patent, copyright, trade-secret, contractual, or other protection.

Before that evaluation can be completed, the company needs to identify who created the relevant code and who contributed to the potentially patentable invention. Those are related questions, but they are not identical.

Federal patent law requires joint inventors to be identified even when they did not work together at the same time, did not make the same type or amount of contribution, or did not contribute to every claim. 35 USCS § 116.

An employment or assignment agreement may require an inventor to assign patent rights to the company, but it does not change who legally qualifies as an inventor. Patent applications and patents are assignable through a written instrument. 35 USCS § 261.

That is why I look at the employment agreement and the invention together. The company should be able to identify the people who wrote the code, the people who contributed to the inventive concept, and the documents governing the resulting rights.

What to Check This Week

  1. Start by pulling the signed agreements for the engineers working on the product. Read each agreement for what it says about code, inventions, documentation, data, and other work created for the company.
  2. Then compare the language with what the employee actually does. If the agreement was prepared for a different role or does not address the employee’s technical work, flag it for closer review.
  3. Finally, confirm that the company has a complete, signed copy for every engineer, including founders and early hires. An unsigned template or an offer letter that merely refers to another document may not answer the ownership question.

Please note that state law can affect the permissible scope of employee invention-assignment provisions, particularly for inventions developed outside the employee’s duties and without company time, equipment, supplies, facilities, or confidential information. The governing law and the employee’s work location therefore deserve attention when the agreement is prepared or revised.

If you are unsure what an agreement covers, that uncertainty is useful information. It is better to identify it now, on the company’s timeline, than through a buyer’s due-diligence request.

Catching Gaps Early

This is the kind of review counsel can perform before a dispute or transaction creates a deadline. Employment agreements can be compared with the software the company is actually building instead of simply being stored in a folder.

It is also where combining business law with intellectual-property work helps. The person reviewing the employment agreement can consider not only the employment relationship but also what the company may later want to protect, license, or sell.

A Measured Next Step

Make a short list of the engineers, founders, and other technical contributors who have worked on the product. Next to each person’s name, identify the signed agreement that addresses ownership and assignment. If an agreement does not clearly address the work that person creates, set it aside for a focused review.

If you would like a second set of eyes on how your agreements line up with your software, reach out and we can talk it through.

Garcia-Zamor serves as fractional general counsel for innovators, protecting both business operations and intellectual property. Ruy Garcia-Zamor leads business growth strategy as a registered patent attorney with the United States Patent and Trademark Office. Elliott Alderman has more than 40 years of experience in intellectual property. Claudia Castillo focuses on employment law. Amulya Annasamudram focuses on patents and intellectual property and is a registered patent attorney with the United States Patent and Trademark Office. Call (410) 531-9853.