Hiring across borders without setting up an entity.

Employing someone in a country, properly, requires a local legal employer. That employer handles the employment contract under local law, payroll and withholding, mandatory benefits, social contributions, and termination rules that differ everywhere.

Owning that yourself means opening a subsidiary. For a company hiring dozens of people in one country, it can be worth it, and some of those companies still choose not to. For a company hiring one to five people across several countries, it is a fixed cost that dwarfs the salaries, and it recurs: every additional country is another registration, another filing calendar, another local accountant.

The alternative that has become standard is the Employer of Record: a provider whose local entity is the legal employer, while the day-to-day working relationship, the work itself, the manager, the roadmap, stays entirely with you. Deel is the leading version of that infrastructure, which is why the partnership matters for this page specifically. The candidate gets a contract their country's law recognizes; you get an employee without a subsidiary; the provider carries the local compliance machinery it already built.

Contractor status looks tempting for exactly one week, until someone reads about misclassification. The comparison table above is the polite version of that discovery, and the impolite version arrives years later, with interest, in a jurisdiction you no longer hire in.

None of the employment infrastructure matters if the search cannot reach the right people, so the front half of the chain deserves its own scrutiny before anyone signs anything.

The point of hiring internationally is that the best person for the role is not in your city, and a search limited to where you already look defeats the purpose. Time zones are handled where they bite: outreach and screening run inside the loop rather than in your team's working hours, and scheduling lands interviews in slots that work on both calendars.

The screening bar is yours, the same as domestic: skills, seniority, the questions you would ask first. Interest is confirmed before anyone reaches your calendar, which matters twice as much internationally, where a candidate's real willingness to work for a foreign employer, on that employer's hours and in that employer's language, is exactly the thing a keyword match cannot tell you.

None of this page is legal advice; the boundary section above marks where your counsel still earns the hour.

It is worth walking the failure sequence once in full, because every team that has lived it recognizes the beats, and every team that has not is one good foreign candidate away from learning them.

The search goes surprisingly well. The candidate is excellent and interested; the interviews are clean; the offer goes out and the offer is accepted. Champagne. Then legal asks how exactly this person in another country will be employed, and the only real answer starts with opening an entity: a registered address, tax registration, ongoing filings, months of elapsed time, all to employ one engineer.

Contractor status gets floated in the same meeting and survives about a week of scrutiny. The candidate, meanwhile, has a start date and a competing offer from a company that already solved this. Their recruiter calls twice while your legal team is still comparing entity timelines. The search did not fail. The infrastructure did.

That failure mode is the entire reputation of cross-border hiring, and it is why the chain above is drawn with no seam in it. Where you already have an entity, none of this applies: the hire lands on your own contract and payroll, and the partnership simply is not invoked for that hire.

Notice also what the sequence implies about timing. The infrastructure question is cheapest at the brief, before any candidate exists, and most expensive in the week after acceptance, when a specific person is holding a competing offer. Teams that decide the employment model per role, up front, never meet the failure mode at all. Teams that defer it are betting the candidate's patience against their own legal department's calendar, and the candidate's patience is the shorter clock.

Most teams reading this have a specific ghost: the excellent candidate in another country they let go because employing them looked like a legal project. That ghost is the test case. Take that role, or the current version of it, and write the brief without the location constraint you previously imposed. Watch what the search returns when 190+ countries are actually reachable, and price the whole chain against what the local-only version of the hire has been costing you in vacancy months. The border was the reason the last one got away. It does not have to be the reason twice.