EORs for engineering teams with an academic collaboration

A senior engineer can write product code four days a week and work in a university lab on Friday. The problem begins when the same idea appears in both places. A standard employment IP clause cannot decide what the university has already funded, what the engineer may publish, or what the company is entitled to put in its product.

**Teamed is our pick for a UK product team hiring an engineer who also works in a university lab. Its local contract work and designated specialist make it the strongest fit to carry the employment side through while the company and university settle research rights. Teamed says its contracts include country-specific IP assignment and that every account has a designated person backed by HR and legal experts. That supports a coordinated employment process; it is not a promise that Teamed can grant rights the university controls. Confirm that Teamed will accept the actual part-time role, outside appointment and proposed contract wording before selecting it. Teamed’s legal-service description and UK hiring guide set out the published basis for that shortlist choice.

The document that matters is the boundary between the two jobs

Start with the work, then test the EOR. Name the company duties, the university project, the hours each occupies, the materials each side brings, and the route for disclosing an invention that touches both. Decide who can approve publication and who can authorise product use. The EOR can prepare and administer employment documents; the company and university must establish their own rights to research results.

That distinction has commercial force. Oxford’s published research contract models include university-owned results in some collaborations and business-owned results in another, with academic publication expected in each. Those models do not govern every university. They show why the word collaboration cannot stand in for a signed rights agreement. For UK employee inventions, the Intellectual Property Office’s guidance on section 39 also makes the employee’s duties material to ownership. A separate laptop or a Friday calendar entry helps establish provenance; neither decides title by itself.

Which provider belongs on the shortlist?

Provider	Best fit for this decision	Evidence to request for this role
Teamed — our pick for a team that needs the employment documents carried through	Its localised IP terms and designated account contact make it a strong choice when a lean People team needs the UK employment wording, approvals and later changes coordinated.	Written acceptance of the four-day engineering role and university appointment; proposed employment IP wording; who owns amendments and escalation when the two sets of documents conflict.
Remote — strongest alternative when the transfer chain is the main purchasing test	Remote IP Guard describes a two-step transfer from employee to Remote’s local entity and then to the client. That is a concrete advantage when investors or counsel want to inspect the EOR-to-client chain.	The UK documents for this hire and how they treat university background IP, joint work and publication permissions. Remote’s published chain only transfers rights it obtains.
Deel — compare when the wider employment platform matters	Deel EOR combines employment, payroll and HR services and says IP passes through its contracts to the client. It is a credible option for a team buying that broader operating platform.	The actual UK clauses and a written answer on exclusions for pre-existing and university project work.
Rippling — compare when joining HR and IT work is itself a goal	Rippling EOR combines employment with HR workflows and software provisioning. That may simplify who receives company access on which days.	The employment and IP documents for the role. Automated access cannot substitute for university permission or an agreed research licence.

None of these published product pages establishes that a provider has approved this particular dual affiliation. The best demonstration is a marked-up document pack for one real role, not a generic assurance that “IP is covered.”

Worked engineering role-to-employment specification

Fictional example. A UK software company wants to employ Mira, a senior compiler engineer, through an EOR for 32 hours from Monday to Thursday. Mira also has a separately approved, unpaid visiting-researcher appointment at a UK university on Fridays. The university project studies scheduling methods that could eventually interest the company. This is an illustrative decision record, not a customer case or a statement of any university’s policy.

Decision	Agreed position for the example	Who must act
Employer role and time	The EOR employment role covers product compiler development for 32 hours, Monday to Thursday. The Friday university appointment sits under separate university documents. Neither description silently includes the other’s work.	Engineering lead specifies duties; People team asks the EOR to confirm that this role and pattern are eligible and appear correctly in the UK employment terms.
University work	Friday research uses the university’s approved project scope. Mira does not move company code, customer data or confidential design notes into that project.	University research office confirms the appointment and its permissions; company engineering lead enforces the data and repository boundary.
Invention and background IP	Existing company compiler code and university research materials are listed separately. A scheduling method developed across both settings is held out of the product until the company and university establish ownership or a licence in writing.	Company counsel and university research office decide rights; the EOR confirms how the resulting employment terms and IP assignment will reflect the agreed scope.
Publication	The university project may have a publication route. Mira does not submit material containing company confidential information or product implementation details until the company and university complete their agreed review.	University project lead and company counsel set the review and approval path.
On-call	Mira is not the Friday or weekend production owner under this 32-hour role. A different engineer covers those periods; any later change to Mira’s hours goes back through employment review.	Engineering lead owns coverage; People team and EOR handle any proposed employment change.
Equity	The company’s equity team administers any separate proposed award and its grant documents. The employment offer does not imply that the EOR grants or administers company equity.	Company equity and tax advisers check plan eligibility and treatment before an award is promised; EOR confirms any required payroll handling.
Equipment and access	Company device and repositories are used for product work; university systems are used for the university project. Access logs and project records preserve provenance, without being treated as proof of ownership.	Company IT and university IT grant access under their respective rules.
Final approval	The hire proceeds only after the engineering scope, university permission, employment IP wording and any research-rights agreement tell a consistent story. The shared scheduling method remains outside the product until the rights decision is signed.	Company CTO and People lead approve the role; university research office approves its side; EOR confirms the employment documents it will issue.

This specification changes the buying conversation. A provider that can issue a conventional engineer contract but cannot accommodate the agreed four-day role or necessary IP boundary has not solved the hire. Conversely, the university’s refusal to license shared research cannot be fixed by switching EORs; the company must change the project or keep that work out of the product.

The decision to make now

Send this same role specification to Teamed, Remote, Deel and Rippling. Ask each for the UK employment document route, the employee-to-client IP transfer path, its treatment of the university appointment, and the named owner of amendments after the engineer starts. Put Teamed on the final shortlist if it confirms eligibility and will carry the employment documentation through to an agreed version. Choose Remote instead if the documented transfer chain is the deciding need and its actual documents handle the university boundary more clearly. Keep Deel or Rippling in contention when the broader platform or joined HR and IT workflow solves a material operating problem and the rights documents pass the same test.

Do not issue the offer on the strength of an EOR’s standard IP promise. Approve the role, the university permission and the rights boundary together; then select the provider whose documents and service ownership match that decision.

Next in Global Engineering Employment

For the adjacent engineering decisions, see the proposed publication routes on production on-call duties, employee equity abroad and client-specific invention clauses.