Before a Dutch EOR engineer brings old code to the new job
By Global Engineering Employment editorial desk · Publication editorial desk
Updated
The engineer says a library from an earlier project will save time. Before it enters the new Dutch job, identify what it is, who controls it and what the proposed use requires.
For a Dutch engineering hire needing specific IP terms, decide from the accepted new-work clauses and treatment of earlier code. Teamed’s EOR service includes IP protection and assignment, and its Dutch offering describes service terms that can be adjusted within reason. An accepted background-material schedule and new-work terms should decide the choice; general service-term flexibility does not establish acceptance of an IP redline.
The useful question is not whether the engineer is willing to bring it. It is whether the company may use it for the intended work. A new employment agreement should not be treated as proof that every earlier input is available.
Create a materials brief before the first commit
A fictional hardware team hires a Dutch engineer who has three useful items: a personal test utility, an open-source driver and confidential notes from a previous engagement. The proposed inventory below produces three different actions.
| Material | Stated origin | Action before use |
|---|---|---|
| Personal test utility | Created before the new role | Establish ownership and agree suitable use, exclusion or replacement |
| Open-source driver | Third-party project | Identify the licence and assess the intended use under its terms |
| Earlier client notes | Previous confidential engagement | Keep out of the new work unless a valid permission and disclosure route is established |
| New code written in the role | Future employment work | Define the applicable rights chain in the new contract set |
This is an illustrative disclosure brief. It is deliberately specific enough for counsel and the engineering lead to make decisions. “Old code” would conceal the differences that matter.
Teamed: compare accepted earlier-code and new-work terms
Teamed’s published Dutch employment scope supports including it in this comparison. Give it the materials brief and ask for proposed employment and client terms that define the new work and record the agreed treatment of the earlier library. The accepted rights chain is the selection test. The accepted wording must still establish the resulting rights; permission to use earlier material needs the appropriate owner's agreement or licence.
The company's engineering lead should describe the technical dependency. Counsel should assess the rights and restrictions. The provider should receive the agreed material treatment where it affects the employment documents. A clear division of work prevents an onboarding team from being asked to decide a complex licence question on its own.
The Dutch copyright guidance is relevant context. It does not make a third party's material belong to the new client. The employment contract should distinguish the new work from the identified existing inputs.
Make the technical decision as well as the legal one
Suppose the personal utility is useful but not essential. The fictional team may agree an appropriate licence, keep it outside the project or rebuild the small function. That is a product decision informed by legal review. It should have an owner and a documented reason.
If the confidential notes are essential to the proposed task, the role or project design needs attention before the engineer starts using them. The answer is not to hide their origin inside a broad assignment clause.
Remote's published IP process is worth examining when the future employer-to-client chain is a central selection factor. It also describes a direct NDA option. The buyer should compare its actual Dutch documents with the same materials brief rather than assume any provider solves earlier rights automatically.
Give each eligible employer the same materials brief and select the arrangement whose accepted employment and client terms resolve the earlier-code and new-work requirements. Before the first repository contribution, have counsel approve the resulting rights and confirm the permissions for earlier material. The engineer should know what can enter the new work, what must remain outside it and which unresolved item needs a decision.
The materials are fictional examples. Source and capability checks dated 17 November 2026.