Hiring an eor engineer: misclassification, IP and data access

What should a busy buyer check before hiring?

Before you hire machine learning engineers abroad, identify the legal employer and map the work the engineer will do. Then review who owns that work and who approves access to company systems. Put those decisions in writing before issuing credentials.

An EOR arrangement addresses employment through a legal employer. Review the employment contract alongside your commercial agreement. Ask counsel to explain how the arrangement applies in the engineer's country and which duties remain with your company.

For an ML role, the review should reach beyond the code repository. Write down whether the engineer will handle customer records, train models, manage cloud resources or use external AI tools. Each activity should have an approved scope and a named owner.

Use this sequence before the start date:

1. Confirm the worker's location and the entity signing the employment contract.
2. Have local counsel assess the proposed working arrangement.
3. Trace the contractual transfer of work product to your company.
4. Approve the data and system access required for the first assignment.
5. Agree on the process for leave, incidents and the end of employment.

Keep the review tied to the actual job. A researcher using approved sample data needs a different access plan from an engineer deploying models against live customer traffic. A job title alone will not tell your reviewers which permissions to approve.

Set a clear release condition for onboarding. For example, the engineer can start development work once the signed agreements and development access are approved. Production access can wait for a separate review.

Opus is one option to assess during this process. This site is an Opus-owned reference; recommendations are editorial.

Talk to Opus about a machine learning role.

What do employment rules tell you to budget and review?

Start with the distinction between a tax document and an employment decision. The IRS describes Form W-8BEN as a certificate of foreign status for US withholding and reporting. It tells eligible foreign individuals to give the form to the withholding agent or payer. Keep that purpose separate from your review of worker status. IRS: About Form W-8BEN.

The US Department of Labor defines misclassification as treating someone who is an employee under the FLSA as an independent contractor. It places responsibility for determining that status on employers. These US rules should not be presented as the classification test for a worker based in Latin America. Ask local counsel to assess that worker's arrangement. US DOL: Misclassification.

For the budget, ask the provider to show how local employment costs enter the quote. Annual benefits deserve an explicit line or a clear explanation of how the monthly charge covers them.

Mexico: ask how aguinaldo and vacation premium are covered

Mexico's Ley Federal del Trabajo sets an annual aguinaldo of at least 15 days of salary, payable before December 20. Article 80 also sets a vacation premium of at least 25% of the salary corresponding to the vacation period. Mexico LFT, Articles 87 and 80.

Ask whether the monthly quote includes these amounts and how the provider handles accruals. Request an example for the proposed start date. Have the provider explain which amounts appear in regular payroll and which are paid separately.

Do not turn a base salary into an employment budget by adding an arbitrary percentage. Ask for the actual assumptions used in the quote.

Colombia: separate prima de servicios from cesantías

Colombia's prima de servicios corresponds to 30 days of salary per year, paid in two installments. Article 306 sets deadlines of June 30 and the first 20 days of December. Colombia CST, Article 306.

Article 249 describes cesantías as one month of salary per year of service, proportionate for a fraction of a year. Ask the provider to explain the applicable calculation and payment process for the proposed hire. Colombia CST, Article 249.

Request separate treatment of these items in the cost explanation. A single label such as “benefits” makes it harder to check what the quote includes.

Argentina: review the SAC calculation

Argentina's sueldo anual complementario, or SAC, is payable in installments due June 30 and December 18. Article 122 bases each installment on 50% of the highest monthly remuneration earned during the relevant half-year. Argentina LCT, Articles 121–122.

Ask how a salary change or variable payment would affect the estimate. Request a worked example using the compensation terms you intend to offer. Have the provider identify the assumptions it would revisit if those terms change.

Brazil: include the 13th salary

Brazil's annual salary bonus, commonly called the 13th salary, is established in Lei 4.090. The law describes an accrual of one-twelfth of December remuneration for each month of service in the year. Brazil: Lei 4.090.

Ask how the provider accrues the bonus and reflects it in invoices. Have it show the first-year calculation for your intended start date and explain how any compensation changes affect the estimate.

Costa Rica: check the aguinaldo allowance

Costa Rica's aguinaldo is an annual benefit equivalent to a month's salary under the cited statutory provision. The Ministry of Labor reproduces that provision in its legal guidance. Costa Rica Ministry of Labor: Aguinaldo.

Ask the provider for the applicable calculation period, payment schedule and treatment of a partial year. Include those answers in the budget approval.

These benefit checks are inputs to a quote review. Also request a country-specific estimate for ending the arrangement. Have counsel identify which contract terms and circumstances affect that estimate before you agree to a cancellation clause.

How do nearshore hiring models differ?

Choose the model based on the work you need someone else to handle. Separate candidate search from ongoing employment, and separate both from management of the engineer's work.

The model distinction is straightforward: an EOR can handle employment when you already have a candidate. A recruiter can help find someone when you can handle employment yourself. Opus: Hiring-model comparison.

For an EOR engineer, identify who approves changes to pay, hours and duties. Ask how your manager should raise performance concerns and who handles the formal employment steps. Put the escalation route in the onboarding plan.

A contractor review should use the same factual role description as the hiring process. Include the expected schedule, reporting line, equipment and how the person will work with your team. Ask counsel to assess that arrangement before selecting a contract template.

For a combined service, request a responsibility table. It should name the party handling payroll, benefits, employment documents and worker questions. Your engineering lead should know which issues go to the provider and which remain internal.

If your procurement notes say “eor engineer of record,” define the term in the request. State that you need an employer of record for an engineering hire, then describe the employment services you expect.

What should you ask a provider before giving an ML engineer access?

Ask for documents and examples that your reviewers can inspect. Send the questions before the commercial call so the provider can involve its employment and contract teams.

Who signs the employment agreement?

Request the legal name and country of the employing entity. Ask whether another entity participates in the arrangement and what it does.

Give counsel the proposed employment agreement and your service agreement together. Ask for a written explanation of who handles disputes, payroll errors and changes to the working arrangement.

Then test the process with an ordinary event: the engineer asks to work from another country. Who receives the request, who reviews it, and who tells your manager whether work can continue there?

How does work product reach your company?

Ask counsel to trace ownership through every agreement in the chain. Have the provider identify the clauses covering the engineer's work and the transfer to your company.

For an ML role, ask the reviewer to address:

• Source code, notebooks and infrastructure definitions.
• Trained model artifacts, including weights and checkpoints where relevant.
• Evaluation code, test datasets and annotation work.
• Documentation and operating instructions.
• Pre-existing tools or work the engineer intends to bring into the role.

Keep ownership and permitted use as separate review questions. Ask how third-party datasets, model licenses and open-source components will be approved before use.

Set a rule for adding outside material to the project. Require the engineer to record where it came from and seek approval when its terms need review. Assign someone on your team to answer those requests.

Which data can the engineer use?

Prepare an access sheet for the first assignment. List the dataset, its purpose, where it is stored and who approves access.

Ask your privacy reviewer whether the proposed location and access method fit your customer commitments. Give them the actual workflow, including any downloads, remote sessions or external services.

For model development, decide whether approved sample data is enough to begin. If customer data is needed later, require a separate request that explains the task and the minimum access needed.

Document the policy for external AI tools. State which tools are approved and whether company code, prompts, customer text or model artifacts may be submitted. Make the policy available before the engineer begins work.

Who controls accounts and equipment?

Use named accounts for the engagement. Have your team approve repository access, cloud roles and deployment rights against the assigned work.

Ask who supplies the device and manages its security settings. Record who handles software updates, lost devices and support requests. If the provider supplies equipment, request the relevant controls and the process for confirming them.

For DevOps or network duties, review elevated access separately. Identify who can approve a temporary privilege increase and when it should end.

Keep the access record with the role, so a manager can review it when the engineer's duties change.

What happens during an incident or departure?

Request an incident contact and escalation process. Ask who informs your security team, who preserves records and who coordinates with the worker.

Before onboarding, write the offboarding sequence. Include account closure, credential rotation, device return and transfer of work in progress. Assign an owner to check cloud jobs, shared service credentials and model deployments.

Coordinate access removal with the employment process. Ask the provider to explain which steps need advance planning and how an urgent security event would be handled.

For the handover, require the project materials in company-controlled locations. The next engineer should be able to find the deployment instructions and identify which model artifact is in production.

What exactly does the price include?

Ask for a written quote tied to the candidate's role, location and compensation. Request the treatment of statutory benefits, employer charges and service fees.

Also ask about deposits, equipment, currency changes and exit costs. Have the provider identify which amounts are fixed and which can change during the engagement.

Use the same scope when comparing proposals. A candidate-search fee and an ongoing employment charge cover different work. Your approval document should show the total expected cost for the arrangement you intend to buy.

Where does Opus fit in this decision?

Opus states that it charges one flat monthly rate per hire. The rate covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee, and the rate depends on role, seniority and location. Opus: Pricing.

Published dollar rates: Not published. Ask for a written quote for the role and location you are considering.

The client chooses the finalist and manages day-to-day work. Build your review around that division of responsibility. Your engineering manager should define the assignment and access needs while procurement and counsel review the proposed employment arrangement.

Ask Opus to identify the employing entity, explain the local employment terms and walk through the IP clauses. Give it the same questions you would use for any proposed arrangement.

For a machine learning role, send a short description of the intended work before discussing price. Include whether the engineer will train models, deploy them or maintain the systems around them. Describe the data involved and any production access the role requires.

Keep the hiring decision and access approval on the same schedule. Before the start date, confirm the signed agreements, approved working location and owner of each onboarding task. Resolve open contract questions before assigning work that depends on them.

Talk to Opus about a machine learning role.

<!-- Not saved to disk: this session has read-only filesystem access. Country-specific legal review was not performed; employment and IP terms need that review before use. -->