Should an AI Startup Hire International Engineers as Contractors or Through an EOR?

The U.S. Bureau of Labor Statistics put the May 2024 median wage for software developers at $133,080 — 2.7× the $49,500 median for all occupations.

An AI startup that pays that same person as a contractor in Lisbon, Toronto, or Cape Town still books the invoice as a vendor cost. The classification test does not care what the invoice says.

Rise is a global payroll and Employer of Record platform for companies that hire, pay, and manage people across borders without standing up a local entity in every market.

The team at Rise sees this decision most often when a seed-stage AI company has three to eight engineers on contractor agreements, a Series A data room in 90 days, and no owned entity in the countries where those engineers actually work.

This article walks the 2026 cost math, the misclassification triggers that show up in an AI engineering org, when to switch off a contractor agreement, who should stay on one, and how to convert without stalling the sprint.

Key Takeaways

• Keep a true specialist on a contractor invoice. Switch a core international engineer to an Employer of Record once you control how they work, not once counsel finds the 1099s.

• On the BLS $133,080 software-developer median, U.S. employer FICA is $10,180.62 in 2026. Rise EOR is $399 per employee per month ($4,788 a year) through owned entities in the US, UK, Canada, Australia, Ireland, Cyprus, New Zealand, and South Africa, expanding to 60+ countries by the end of 2026.

• The IRS common-law test still turns on behavioral control, financial control, and the type of relationship. A Slack handle and a GitHub seat are control.

• The DOL's 26 February 2026 proposed rule would replace the 2024 FLSA contractor analysis. It does not rewrite IRS tests, state ABC tests, or host-country labor law.

• Host-country permanent establishment is a separate clock. The November 2025 OECD Model Tax Convention update generally treats a home office as not a place of business below 50 percent of working time over twelve months.

• This advice does not work for a six-week evals specialist who already invoices three other labs. Putting that person on EOR overpays employment cost for a relationship that was correctly a contractor.

The Contractor Invoice Looks Cheaper Until You Run the 2026 Classification Math

Let's start with why founders default to contractors.

A 1099, a B2B invoice, or a recibo verde in Portugal books as cost of goods or professional services. There is no employer FICA line, no local social charge, and no entity to stand up.

Here's the problem. Classification is a facts-and-circumstances test, not a document test.

The IRS says a worker is an employee if you have the right to control what will be done and how it will be done, even when you give them freedom of action. That rule is in Publication 15-A for 2026 and on the Service's contractor-or-employee page as of August 2026.

A remote AI engineer on your Slack, in your daily standup, on your sprint board, with a company laptop and a private GitHub org, is not selling you a result. They are inside your means and methods.

On the flip side, a specialist who bids a six-week evals audit, uses their own GPU cluster, invoices three other labs, and delivers a report is selling a result. That person can stay a contractor.

The DOL picture is in flux. On 26 February 2026 the Wage and Hour Division published a proposed rule to rescind the 2024 FLSA independent-contractor analysis and replace it with a streamlined test closer to the 2021 "core factors" approach. The 60-day comment period closed at 11:59 p.m. ET on 28 April 2026.

That proposal, as of August 2026, is not a final rule. It does not bind the IRS. It does not bind California's ABC test. It does not bind the Autoridade para as Condições do Trabalho in Portugal.

First of all, stop treating "the federal contractor rule loosened" as permission to keep core engineers on invoices.

What a 2026 AI-Engineer Hire Actually Costs as a Contractor vs EOR

At first glance, the contractor invoice is the cash-preserving move.

Run the federal employment-tax stack on the BLS median instead.

For 2026, IRS Publication 15 (Circular E) and the Social Security Administration set the OASDI rate at 6.2 percent each for employer and employee, on wages up to a $184,500 contribution and benefit base. Medicare is 1.45 percent each, with no wage cap.

On $133,080 of wages:

• Employer Social Security: 6.2% × $133,080 = $8,250.96

• Employer Medicare: 1.45% × $133,080 = $1,929.66

• Combined employer FICA: $10,180.62

That is 7.65 percent of pay, against $0 of employer FICA on a correctly classified contractor. The SSA max employer OASDI hit at the $184,500 base is $11,439, so a senior AI engineer above the BLS median still only adds Medicare on the dollars over the base.

Rise EOR is $399 per employee per month, or $4,788 a year, through owned entities in the US, UK, Canada, Australia, Ireland, Cyprus, New Zealand, and South Africa.

Add that fee to employer FICA on the BLS median and the "extra" versus a contractor invoice is about $14,969 a year — before local social contributions, paid leave, and benefits in the host country.

Here's why that matters. If you issued the required Forms 1099 and the IRS later reclassifies the worker, Publication 15's section 3509 rates still leave you with 7.44 percent Social Security, 1.74 percent Medicare, and 1.5 percent federal income tax withholding. On $133,080 that is $14,212.94, and you cannot recover the employee share from the engineer.

If you did not issue the 1099s, those 3509 rates jump to 8.68 percent, 2.03 percent, and 3.0 percent — $18,245.26 on the same wage, plus the full employer share already inside those figures.

That is the cheap invoice after the audit. It is larger than a year of Rise EOR plus employer FICA.

The 2026 Form 1099-NEC reporting threshold also moved. Publication 15 raises the information-return threshold from $600 to $2,000 for payments made after calendar year 2025. Missing a $2,000 filing is not a defense. It is how you lose the lower 3509 rates.

Host-country social charges sit on top of this U.S. math. A Portuguese employee, as of 2026, carries an 11 percent employee Segurança Social withhold and a 23.75 percent employer charge on gross salary. A trabalhador independente pays 21.4 percent on 70 percent of relevant income — an effective ~15 percent of gross — and that person is supposed to be independent.

You do not "save" 23.75 percent by putting a Lisbon ML engineer on recibos verdes if they only have one client, work your hours, and sit in your standup. You defer a bill that ACT and Segurança Social can reopen.

Five Misclassification Triggers That Show Up in an AI Engineering Org

But it's not just that the invoice is cheaper on day one.

AI startups trip the IRS three-category test in a pattern that looks almost identical from one seed round to the next.

1. Behavioral control. Daily standup, sprint commitment, on-call rotation, required hours overlapping U.S. product, a mandated stack, and a company laptop. Publication 15-A treats instructions about when, where, and how to work as employee facts.

2. Financial control. You reimburse Cursor, GPU, and coworking. You pay a monthly retainer, not a project price. The engineer has no unreimbursed expense and no chance of profit or loss. That is the IRS financial-control category.

3. Type of relationship. Open-ended SOW, "we'll convert you at Series A," equity on a contractor agreement, vacation that you approve, and work that is a key aspect of the business. Training the model is the business of an AI startup.

4. Exclusivity. A non-compete, a "no other clients" Slack rule, or a calendar that is 40 hours on your product. A contractor who cannot serve other customers is not in business for themselves.

5. Tenure. Ninety days of full-time-equivalent work with no end date. The IRS asks whether the relationship will continue. A rolling contractor who has been on the team since the seed round is an employee with a stale invoice.

Of course, one factor does not decide the case. The IRS is explicit: there is no magic number of factors.

Five of them pointing the same way does.

The DOL proposal, if finalized, would weight two "core" factors more heavily: the nature and degree of control, and the worker's opportunity for profit or loss. An AI engineer on your sprint with no other clients fails both.

Host labor law can be stricter than either federal test. Portugal's economic-dependency rule starts to bite when more than 50 percent of a contractor's income comes from a single client. That is a different 50 percent from the OECD PE test, and it can fire first.

Switch on a 90-Day Calendar, Not After Series A Diligence

Here's the decision rule Rise would defend.

If a person is going to be a core engineer — model, infra, evals, or product — budget them as an employee from the offer. Use EOR in any country where you do not have an entity.

If you must trial the hire, cap the contractor period at 90 calendar days of full-time-equivalent work, write an end date in the SOW, and convert on day 91 or let the contract die.

Do not wait for Series A counsel to find twelve 1099s in the data room. By then the facts are already employee facts, and the 3509 math above is the best case.

Use this calendar.

Day 0. Role test. Is this a bounded deliverable with the specialist's own tools and other clients, or a seat on the team? Seat on the team → EOR or local employment. Bounded deliverable → contractor, with an Agent of Record pay rail if you still want screening and compliant payout.

Day 30. Control test. If they are in standup, on the sprint, or on your GitHub, the trial is already an employment relationship. Convert.

Day 90. Tenure test. Open-ended plus full-time-equivalent hours is the type-of-relationship category. Convert or end.

Before the next fundraise. Diligence test. Investors will read contractor files against IRS Publication 15-A, host labor codes, and IP assignment. Convert the core roster first.

Before they hit 50 percent of working time in a host country. PE test. That is the next section, and it is not the same clock.

The contractor-of-record vs employer-of-record vs agent-of-record split is the model layer. This piece is the switch: when the contractor model stops being the honest one for a named engineer.

Host-Country PE Sits on a Different Clock Than the 1099

A clean contractor file in the U.S. can still be a dirty corporate-tax file in the country where the engineer sits.

The November 2025 update to the OECD Model Tax Convention commentary on Article 5 says a home or other relevant place is generally not a place of business of the enterprise if the individual works from it for less than 50 percent of their total working time for that enterprise over any twelve-month period commencing or ending in the fiscal year.

Cross 50 percent and you leave the safe harbour. You then test facts and circumstances, including whether there is a commercial reason for the person to be in that country.

An AI startup that hired a Lisbon engineer because Lisbon is cheaper, or because that person already lived there, is on the personal-convenience side of that commentary. An AI startup that hired them to serve EU customers, sit near a GPU colo, or run a local data partnership is on the commercial-reason side.

That means the PE question can fire even when the 1099 looks tidy.

EOR is the operating response when you want the person employed locally without a subsidiary. It puts a local employer on the contract, runs host payroll, and keeps your Delaware C-corp from being the named employer in that market.

It is not a PE waiver. No payroll product is. It is how you stop adding employee facts to a contractor file while the PE analysis runs.

Shadow payroll is a different tool. It reports host tax for someone who stays on home payroll. It does not fix a misclassified contractor, and it does not create local employment.

If the engineer should be employed in the host, you need a local entity or EOR, not a shadow file on a 1099.

Who This Advice Does Not Work For

Name the downside.

This switch-to-EOR rule is the wrong move for a six-week evals specialist who already invoices three other labs, uses their own GPU cluster, and delivers a written report.

Putting that person on EOR costs you $399 a month plus host employment charges for a relationship the IRS would still treat as a contractor under the three common-law categories. You also pick up paid-leave accrual and termination rules you did not need.

It is the wrong move for a staff-aug firm that already employs the engineer and invoices you. You are buying a service from an employer. Do not double-employ them.

It is the wrong move for a two-week model-audit from a consultancy with its own entity in that country. Pay the consultancy.

It is the wrong move if the only "engineer" is a founder paying themselves as a contractor in a market with no other hires and no commercial reason to be there. That is a founder-compensation question, not an international-roster question.

On the flip side, it is the right move for the ML engineer in Porto who has been on a rolling invoice since March, joins standup at 16:00 Lisbon time, and holds the evals pipeline. That person is an employee. The invoice is the risk.

Rise would rather lose the EOR fee on a true specialist than watch a seed company convert six core engineers the week before a term sheet.

Convert the Core Engineer Without Stalling the Sprint

You do not need a subsidiary to flip the file.

Pick the employment model first. Local entity if you already have one in that country. EOR if you do not. AOR only if the person still passes the contractor test and you need a compliant payout rail.

Then run a conversion that payroll can actually close.

1. Freeze the old SOW with an end date. Pay the final invoice. Issue the 1099-NEC if U.S. reporting applies and the 2026 $2,000 threshold is met.

2. Start the EOR employment contract in the host country, with a start date the day after the SOW ends. Do not overlap the two.

3. Move IP and access. New employment agreement, new IP assignment, same GitHub and Slack. The access pattern can stay. The legal relationship cannot.

4. Re-price to gross. The contractor rate was not a salary. Back into a host-country gross that preserves net, then add employer social and the $399 EOR fee. On the BLS median, budget ~$10,181 of U.S. FICA if the person is on U.S. payroll, or the local employer charge if they are not.

5. Put the next three hires on the same rule. Core seat → employee. Bounded specialist → contractor. Write it in the offer template so the 90-day clock is not a founder memory.

Rise's owned EOR entities cover the US, UK, Canada, Australia, Ireland, Cyprus, New Zealand, and South Africa as of August 2026, with the network expanding toward 60+ countries by year end. If the engineer sits in a country not yet on that list, do not invent a contractor as a bridge. Pause the start date, or hire through a local entity, until the employment rail exists.

Rise's take:

Switch the core international engineer to EOR on a 90-day clock, not after a diligence memo. Keep the six-week specialist on a contractor invoice. The DOL's February 2026 proposal does not buy you a third category called "full-time contractor in Slack."

The cost gap on the BLS median is about $15,000 a year in U.S. FICA plus EOR fee. The reclassification bill, even at section 3509 rates with 1099s filed, is in the same band — and that is the good outcome.

What you do next is a roster, not a blog post. List every international engineer. Mark each one core or specialist. Convert the core column before the next close.

Book a demo

If you want the team at Rise to map that roster onto EOR, AOR, or contractor pay, book a demo.

FAQ

Should an AI startup hire international engineers as contractors or through an EOR?

Hire true specialists as contractors. Hire core engineers through an Employer of Record or a local entity. The switch is control, tenure, and host-country presence, not the word "contractor" on the SOW. As of August 2026, Rise EOR is $399 per employee per month in owned-entity markets.

How much extra does EOR cost versus a contractor invoice in 2026?

On the BLS May 2024 software-developer median of $133,080, U.S. employer FICA is $10,180.62 and Rise EOR is $4,788 a year. That is about $14,969 of extra load versus a correctly classified contractor, before host social charges. A section 3509 reclassification with 1099s filed is $14,212.94 on the same wage — without recovering the employee share.

Does the DOL's February 2026 proposed contractor rule let us keep engineers on 1099s?

No. The 26 February 2026 NPRM would replace the 2024 FLSA analysis. Comments closed 28 April 2026. As of August 2026 it is not a final rule, and it does not override the IRS common-law test, state ABC tests, or host labor law.

When does a remote AI engineer create permanent establishment risk?

The November 2025 OECD commentary generally says a home office is not a place of business below 50 percent of working time over twelve months. Above that, you test commercial reason. Classification and PE are separate clocks. EOR employs the person locally. It is not a PE waiver.

Who should stay on a contractor agreement?

A bounded specialist with other clients, their own tools, and a written end date. A six-week evals audit from a person who invoices three labs is the named case. A rolling, exclusive, standup-attending ML engineer is not.