A founder's first hire in a new country usually comes down to one decision: engage them as an independent contractor, or bring them on as a formal employee through an entity or an Employer of Record. This piece lays out the misclassification risk behind that choice using published penalty and case data.
An independent contractor is self-employed, invoices for the work, and controls their own tools and schedule. A formal employee, hired through a company-owned entity or an Employer of Record, is subject to local labor law, receives benefits, and has taxes withheld. For a first international hire, the right choice depends on how the work actually happens, not which label the contract uses.
The label on the contract does not decide classification. The facts of the working relationship do.
Oyster HR's guide to employee and contractor misclassification frames the test around six factors: who controls when, where, and how the work gets done; who supplies the equipment; whether payment moves as an invoice or a regular wage; who handles tax withholding; whether the worker gets benefits; and whether the role fills an ongoing need or a short, defined one. A worker who sets their own hours, uses their own laptop, invoices monthly, and is engaged for a fixed project looks like a contractor on every axis. A worker who logs in on company hours, uses company-issued equipment, is paid a steady salary, and fills a role with no end date looks like an employee, regardless of what the contract calls them.
Most first international hires do not sit cleanly on either end. A founder brings someone on as a "contractor" to move fast, then keeps extending the engagement, adding hours, and directing day-to-day work the way they would direct an employee. That drift is where the risk accumulates. When we calibrate a search for a founder hiring their first person in a new market, this is usually the first question we help them sort out, before sourcing even starts.
| Factor | Looks like contractor | Looks like employee |
|---|---|---|
| Control over schedule and method | Worker sets own hours and approach | Company sets hours, reviews method |
| Equipment | Worker supplies own tools | Company issues equipment |
| Payment structure | Invoiced, project or milestone-based | Regular wage or salary |
| Duration and role | Fixed scope, defined end date | Ongoing, no end date, integrated into the team |
None of these factors is decisive alone. Authorities and courts weigh them together, and the pattern across all six usually determines how a role gets classified, not any single data point.
The exposure is not hypothetical, and it is not small once a pattern of misclassification shows up across more than one worker.
Deel's published guidance on misclassification penalties cites federal payment penalties of up to $1,000 per misclassified worker under US wage-and-hour law. California goes further: civil penalties range from $5,000 to $15,000 per misclassified employee for an honest mistake, and $10,000 to $25,000 per employee if the misclassification is found willful, on top of back taxes and back benefits owed to the worker. Penalties vary by jurisdiction, and a founder hiring outside the US faces a different set of local labor authorities with their own enforcement regimes, but the US figures alone show how quickly a single misclassified hire can become an expensive one.
The scale risk shows up when misclassification is contested across many workers at once, not just one. Remote's misclassification guidance cites the Knight-Swift Transportation settlement, in which the company paid out more than $100 million in damages to roughly 20,000 workers found to have been misclassified. That case did not start as a $100 million problem. It started as a classification pattern applied across a workforce, and the exposure compounded as the number of affected workers grew.
A founder's first international hire is one person, not twenty thousand. But the mechanism is the same: a classification choice that looks reasonable for one role becomes a liability if the company repeats the same pattern across its next five or ten hires in the same market.
Strip away the contract language and the real question is simple: how narrowly scoped is the work, and who is directing it day to day.
A narrowly scoped, contractor-directed engagement can reasonably stay a contractor relationship. Think of a fixed project with a defined deliverable, a worker who sets their own hours and uses their own tools, and an end date that is actually honored when the project closes.
An ongoing, company-directed role increasingly looks like employment the longer it continues. If the founder is setting the worker's hours, assigning daily tasks, providing the laptop, and the engagement has no real end date, the relationship has the substance of employment even if the paperwork says contractor. At that point, formal employment through an owned entity or an Employer of Record is the lower-risk path, because it puts tax withholding, benefits, and local labor law compliance on a structure built to handle them.
This decision sits upstream of anything related to sourcing or search. A founder can resolve classification correctly and still need help finding the right person, whether that means building a distributed team across US and CET time zones, working through the broader mechanics in how to hire international employees, or running a search in a market they have never hired in before, as covered in the international recruitment agency guide.
This piece answers whether a first international hire should be a contractor or a formal employee. It does not cover how an Employer of Record itself works, how it differs operationally from a company-owned entity, or what it takes on in terms of local compliance. That mechanism, including what an EOR actually assumes versus what a contractor relationship leaves with the founder, is covered in detail in Employer of Record vs Contractor: Which One Do You Need. The short version here: once a role is ongoing and company-directed, an EOR or an owned entity is the structure built to carry the compliance load a contractor agreement cannot.
A narrowly scoped, worker-directed engagement can reasonably stay a contractor relationship. An ongoing, company-directed role increasingly looks like employment, and the penalty exposure for getting that wrong is real: up to $1,000 per worker federally, $5,000 to $25,000 per employee in California depending on intent, and settlements that have run past $100 million when the same misclassification pattern repeats across a workforce. Decide based on the six factors, not the contract's label, and move to a formal employee structure, entity or Employer of Record, once the role stops looking like a fixed engagement and starts looking like a seat on the team.
The label on the agreement does not control classification. Authorities look at control over the work, who supplies equipment, payment structure, tax withholding, benefits, and whether the role is ongoing. If those facts point to employment, calling the relationship a contract does not change the exposure described in Deel's misclassification penalty guidance.
In the US, Deel's guidance cites federal payment penalties of up to $1,000 per misclassified worker, and California civil penalties of $5,000 to $15,000 per employee for an honest mistake, rising to $10,000 to $25,000 if found willful, plus back taxes and back benefits. Penalties vary by jurisdiction, and the exposure grows sharply if the same misclassification pattern is repeated across multiple workers, as the Knight-Swift Transportation settlement cited by Remote illustrates.
When the engagement stops being a narrowly scoped, worker-directed project and becomes an ongoing, company-directed role, with the company setting hours, supplying equipment, and treating the position as a permanent seat rather than a fixed deliverable. At that point, formal employment through an entity or an Employer of Record carries less classification risk than continuing the contractor label.
Yes. The specific penalty figures and enforcement mechanisms cited here are US federal and California examples; other countries have their own labor authorities, back-pay rules, and penalty structures. The underlying test, control, equipment, payment, tax treatment, benefits, and duration, tends to recur across jurisdictions even when the specific numbers differ.
A criteria-first look at international recruitment agencies startups actually consider, including Recruitmint, with the stated basis for inclusion and a link to each firm's own site.
CET and the continental US barely share a working day, which breaks the assumption that a distributed team can just meet whenever. This piece maps the actual overlap hours and shows how to structure a team that spans both without forcing anyone into a permanent night shift.
Hiring someone abroad usually means choosing between an Employer of Record and a contractor agreement. Here is how the two actually differ in cost and structure, cited to the EOR providers' own pricing pages.
Recruit