Most objections to hiring across borders are not exactly wrong. They are outdated, or they describe a real risk while pointing at the wrong cause.
That distinction matters, because a company that dismisses the model for the wrong reason loses access it needed, and a company that proceeds while misunderstanding the actual risk creates exposure it did not price.
Here are seven persistent myths about hiring international software engineers, what is true underneath each, and what to do about it. Rise92 encounters all seven while building distributed engineering teams.
The seven, in short
| Myth | What is actually true |
| The engineering talent is weaker | Quality is distributed, access is not |
| You need a local entity | An employer of record removes that requirement |
| Contractors are the simple route | The fastest way to create serious liability |
| Time zones make collaboration impossible | Overlap is a design decision, not a constraint |
| They leave as soon as something better appears | Retention tracks role quality, not geography |
| Your IP is at greater risk | Real risk, but it follows classification, not location |
| Paying less means getting less | Cost structure and capability are separate variables |
Myth 1: The offshore engineering talent is weaker
What people believe: strong engineers concentrate in a handful of established technology markets, and everywhere else is a step down.
What is actually true: capability is distributed far more evenly than access to it. The largest technology companies in the world staff critical infrastructure from engineering centres across dozens of countries, and have done for two decades.
What differs by market is not the ceiling but the depth of supply in specific specialisms, and how easy that supply is to reach.
Where the myth comes from, honestly: companies that tried this and had a poor experience usually did not reach the senior tier of the market they entered. They posted a role, received applications from the actively searching population there, and concluded the talent was not available.
That conclusion is the same error made domestically. The strongest engineers in any market are employed, performing well, and not applying anywhere.
What to do: evaluate the sourcing method rather than the market. Reaching genuine senior depth requires a network route, which is the basis of off-market sourcing through closed networks.
The honest qualification: depth genuinely does vary by specialism. Production AI experience is thinner in most markets than general full-stack or cloud capability. Check the specific capability rather than assuming either abundance or scarcity.
Myth 2: You need a local entity to hire legally
What people believe: employing someone in another country means incorporating there, which means legal fees, a registered office, local directors, and months of setup.
What is actually true: an employer of record becomes the legal employer on your behalf. It issues the local contract, runs payroll, withholds and remits tax, administers statutory benefits, and handles compliant exit. You keep day-to-day direction of the work.
When an entity actually makes sense:
| Situation | Structure |
| Fewer than 30 people in the country | Employer of record, almost always |
| More than 30 people, multi-year horizon | Model the crossover honestly |
| Regulated activity requiring local licensing | Entity, usually unavoidable |
| Testing a market | Employer of record |
The common confusion worth clearing up: an employer of record and a professional employer organisation are not the same thing. One removes the need for a local entity entirely; the other assumes you already have one.
What to decide before sourcing: who will legally employ this person. Discovering the answer after an offer is accepted costs weeks, and occasionally costs the hire.
Myth 3: Contractors are the simple workaround
This is the most dangerous myth on the list, because it is the easiest to act on and the most expensive to unwind.
What people believe: engaging someone as an independent contractor avoids the complexity of international employment entirely.
What is actually true: contract language does not decide the outcome. Regulators examine the functional reality of the relationship, specifically control over how and when work is performed, whether the person can work for others, whether they carry business risk, and how integrated they are into your organisation.
A full-time engineer working your hours, using your tools, reporting to your manager, and appearing on your org chart is an employee in most jurisdictions regardless of what the agreement says.
What contractor misclassification actually costs:
- Penalties exceeding $100,000 per worker in high-enforcement jurisdictions such as Mexico and Brazil
- Up to $25,000 per worker in California alone
- Retroactive payroll taxes, interest, and mandatory benefit payments
- In the UK, under IR35, the hiring business determines status, so the liability sits with you rather than the contractor
Two details most companies miss:
Most Latin American jurisdictions default to employee status when classification is ambiguous, and the burden of proof sits with the company claiming otherwise. Brazil, Spain, France, India, Germany, and Canada are all repeatedly flagged as high-reclassification-risk markets.
US companies must also collect a W-8BEN or W-8BEN-E from foreign contractors before paying them, or face a 30% backup withholding requirement.
When a contractor arrangement is genuinely appropriate: defined deliverables, the person controls how and when the work happens, they work for others, and there is no expectation of continuation beyond the project. That is a real category, and it is narrower than most companies treat it.
What to do: audit existing relationships annually, and evaluate any long-running engagement without a defined project scope for conversion to employment before a regulator does it for you.
Myth 4: Time zones make real collaboration impossible
What people believe: a large time difference means asynchronous handoffs, a day of latency per exchange, and no genuine working relationship.
What is actually true: overlap is a design decision made at hiring time, not a fixed property of a market. Four hours of overlap supports live collaboration. One hour requires asynchronous discipline. Both work if chosen deliberately. Neither works if discovered afterwards.
What the difference looks like in practice:
| Overlap | Operating model |
| Six or more hours | Effectively colocated working rhythm |
| Three to five hours | Live for decisions, async for execution |
| One to two hours | Async default, one standing sync |
| Effectively none | Only viable for genuinely independent workstreams |
The real constraint, which is not time zones: coordination cost. Distributed teams may amplify unclear handoffs, fragmented documentation, and manager bandwidth limits. The organisations that succeed are not the ones hiring in the most convenient time zone, they are the ones that reduce coordination friction through written process and explicit ownership.
What to do: define the overlap requirement before you begin sourcing, and treat it as a hard criterion rather than something to negotiate when you like someone.
Myth 5: They leave as soon as something better appears
What people believe: international hires are less committed, treat the role as a stepping stone, and churn faster than local employees.
What is actually true: retention tracks the quality of the role relative to locally available alternatives, and the quality of the management relationship. Geography is not an independent variable.
What actually drives departures in distributed teams:
- Compensation drifting as the local market moves while your offer does not
- Isolation from the core team, where decisions happen in conversations they are not in
- No visible growth path or documented progression
- Headquarters bias, where their working hours are always the inconvenient ones
- Manager distance, where escalations stop reaching anyone
The pattern worth noticing: every one of those is a management failure rather than a hiring failure, and every one is equally capable of driving out a local employee.
What to do: benchmark compensation annually and adjust proactively, hold the weekly one-to-one without fail, rotate meeting times so inconvenience is shared, and make progression visible. Companies that treat international hires as peripheral get peripheral retention.
Myth 6: Your IP is at greater risk
This objection is the most serious, and also the most consistently misdiagnosed.
What people believe: code written in another country is inherently less protected, and cross-border enforcement is impractical.
What is actually true, and this is the sharpest point in the piece: IP ownership follows employment classification, and employment classification follows local law. The risk is real, but it is created by structure rather than by geography.
How this goes wrong in practice:
- Without explicit assignment language in the agreement, you may not own the code, designs, or documentation produced for you
- Jurisdictions handle ownership incompatibly. Some automatically assign employee-created work to the employer, others require explicit written agreement, and a few protect moral rights that cannot be waived by contract
- A misclassified contractor may retain ownership of work you believed you had bought, so a classification problem becomes an ownership problem
- Most employment contracts still carry domestic assumptions and miss country-specific assignment rules entirely
The compounding version: a contractor arrangement that survives scrutiny in one country may fail in another, and that failure does not only create tax exposure. It creates a gap where your ownership becomes contestable.
The adjacent risk worth naming: transferring personal data across borders without safeguards can breach GDPR, CCPA, or equivalent regimes, with fines reaching seven figures. That is a data governance question rather than an employment one, and it needs separate attention.
What to do:
- Use a consistent base agreement adapted for local requirements rather than one contract reused globally
- Include explicit IP assignment language, checked against local law in each jurisdiction
- Resolve classification correctly, because ownership depends on it
- Centralise contracts and classification documentation so the position is auditable
- Treat this as a legal review rather than a template exercise
Myth 7: Paying less means getting less
What people believe: a lower total employment cost signals a lower tier of capability, so you are trading quality for savings.
What is actually true: compensation levels reflect local cost of living, currency, and market competition. They do not reflect the ceiling of engineering capability in that market. A senior engineer in a lower-cost market is not a junior engineer; they are a senior engineer whose local market prices differently.
Where the myth becomes self-fulfilling: companies that lead with cost optimise for the lowest quote, source from the most accessible tier of the market, and then get exactly what they selected for. The poor outcome is caused by the selection criterion, not by the market.
The distinction that matters commercially: a transparent cost structure and a discounted one are different things. Marked-up models embed a percentage premium into compensation that compounds monthly. An at-cost model discloses every component, with no salary markup or embedded commission, so what you save is intermediary margin rather than capability.
What to do: compare total landed cost across models, including sourcing fee, employment fee, and any ongoing percentage, over a three-year horizon rather than a first-year one. The full comparison sits in transparent pricing.
The test to apply to any provider: ask for the complete fee breakdown in writing, and ask specifically whether any margin sits inside the salary. An evasive answer tells you which model you are looking at.
What genuinely does change
Dispensing with myths is not the same as pretending nothing is different. Four things do change, and they need owners.
| What changes | What it requires |
| Employment structure | Decided before sourcing, not after offer |
| Written communication | Becomes the primary medium, not a supplement |
| Coordination | A named owner, or the cost quietly grows |
| Contracts and IP | Jurisdiction-specific review, not a global template |
None of these is a reason not to proceed. All four are reasons to decide them deliberately rather than discovering them at offer stage.
Frequently asked questions
The risks are different rather than larger, and they are concentrated in structure rather than in capability. Employment classification, contract enforceability, and IP assignment all need jurisdiction-specific attention that domestic hiring does not require. Handled properly they are administrative, and handled carelessly they create real financial exposure.
Only where the engagement is genuinely independent, meaning defined deliverables rather than set hours under your direction. Contract wording does not decide the question, since regulators examine control, exclusivity, business risk, and integration into your organisation. Penalties for contractor misclassification exceed $100,000 per worker in some jurisdictions and include retroactive taxes and mandatory benefits.
Usually not below roughly 30 people in a country, where an employer of record is better economics and removes a two to four month incorporation from the critical path. Beyond that headcount, model the crossover, since per-employee fees eventually exceed the cost of running your own entity. Regulated activities requiring local licensing are the main exception.
Include explicit IP assignment language in every agreement and check it against local law in each jurisdiction, because some countries automatically assign employee-created work while others require written agreement and a few protect non-waivable moral rights. Resolve classification correctly as well, since IP ownership follows employment classification. A single contract template reused globally is the most common source of ownership gaps.
What to take from this
The choice is narrower than the marketing suggests. Establish whether the person is an employee or a genuine contractor, establish whether you own a local entity, and five of the six options usually eliminate themselves.
Then model total cost per country rather than comparing provider fees, because statutory variation dwarfs fee variation.
And keep the sourcing decision separate from the employment decision, because conflating them is how companies end up paying an ongoing percentage for something a one-time arrangement would have covered.
To work through which structure fits your situation, get in touch.
What to take from this
Six of these seven myths dissolve on inspection. One does not.
The IP and classification question is a genuine risk. It is frequently mishandled, and is not solved by good intentions or a strong contract template. It requires jurisdiction-specific legal review and correct employment structure, in that order.
Everything else on the list is either a management problem that exists equally at home, or a sourcing problem caused by reaching the wrong tier of a market.
The two decisions that determine whether this works are the same two every time: reach top 1% talent that may not be searching for opportunities on job boards, and employ them properly. To work through both for your situation, please get in touch.
