Step 1 — Choose the hiring structure before you choose the person
There are three ways a U.S. company ends up with a Brazilian engineer, and they have different costs, timelines and risks.
Direct contractor means you contract the individual. It is the cheapest and fastest, and it puts the classification question on you: if you set their hours, require exclusivity and manage them like staff, a Brazilian labour court may look at the substance of the relationship rather than the contract. Many companies do this successfully; the ones that get hurt are the ones that never thought about it.
A studio or agency contracts the engineer and invoices you for a service. You get one vendor relationship, no Brazilian employment exposure, and a replacement obligation if the person leaves. You pay a margin for that.
An employer of record hires the engineer as a formal Brazilian employee on your behalf, for roughly $500 to $700 per person per month on top of salary. Choose it when you want a long-term employment relationship with benefits, or when your compliance team requires it.
None of these is universally right. Decide this first, because it changes who you can talk to.
Step 2 — Write the role for one person, not for a wish list
The most common cause of a failed nearshore hire is a job description that describes three jobs. "Senior full-stack engineer with React, Node, AWS, Kubernetes, data pipelines and mobile" will get you applicants; it will not get you someone who is senior at any of it.
Name the primary stack, the one system the person will own, and the single outcome you expect in ninety days. If you cannot write the ninety-day outcome, the role is not ready and no sourcing partner can fix that for you.
Step 3 — Screen spoken English live, early, and without apology
Written English in Brazil is generally strong; spoken English varies enormously, and a résumé cannot tell you which you are looking at. Reading level and speaking level diverge more here than most U.S. hiring managers expect.
Put a fifteen-minute unscripted conversation early in the process and make it about something technical the candidate has to explain, not about their background. Someone can rehearse "tell me about yourself"; nobody rehearses "explain why you chose that database".
The bar that matters is not accent. It is whether the person can disagree with you in a meeting. An engineer who understands everything and cannot push back is a worse hire than one with a heavy accent who says "I think that will break".
Step 4 — Replace the take-home test with a conversation over real code
Take-home assignments select for candidates with free evenings. Senior engineers who already have a job decline them, which means the filter removes exactly the people you want.
Use a sixty-minute session on a real codebase — yours, sanitized, or an open-source project with a genuine bug. Watch how they navigate unfamiliar code, what they read first, and what they ask. That is the actual job.
Ask about a failure. "Tell me about something you shipped that broke" separates people who have operated systems from people who have only built them.
Step 5 — Get the contract right on three points
Intellectual property assignment. U.S. law and Brazilian law treat work-for-hire differently, and the safe practice is an explicit present assignment of all IP created under the agreement, with a clause stating it survives termination. Do not rely on the doctrine that would apply in your state — say it in the contract.
Confidentiality and data handling. If your product touches regulated data, say specifically what the engineer may and may not download to a local machine.
Notice and termination. Thirty days in both directions is the market norm for contractor and studio arrangements. Anything longer is a red flag in a market where you are supposed to be buying flexibility.
Have your own counsel review it. This guide is not legal advice and cannot be.
Step 6 — Pay in a way that does not create a monthly problem
Most Brazilian engineers working for U.S. companies invoice as a legal entity — a Brazilian PJ — and receive an international transfer. Wise, Payoneer, Deel and traditional wires are all common. Expect the engineer to have a preference and to know the mechanics better than you do.
For contractor payments to a non-U.S. person for services performed outside the United States, U.S. companies typically collect a Form W-8BEN or W-8BEN-E for their records. Confirm your specific obligations with your accountant — the details depend on your entity and how the relationship is structured.
Whatever you pick, fix the currency. Paying "the BRL equivalent of $5,000" makes the exchange rate someone’s problem every month, and it will be yours the first time the real moves 8% in a week.
Step 7 — Onboard as a team member, not as a vendor
Give access on day one: repository, CI, staging, the incident channel, the design files. An engineer waiting five days for a GitHub invitation learns immediately that they are not really on the team.
Assign a named person to answer questions. Not "ask in Slack" — a name.
Ship something small in week one. A tiny merged pull request does more for a remote engineer’s integration than a week of documentation reading.
Key takeaways
- Pick the legal structure — contractor, studio or EOR — before you start interviewing.
- Screen spoken English in an unscripted technical conversation, early.
- Drop take-home tests; pair on real code instead.
- Put IP assignment in writing explicitly, and have counsel review it.
- Fix the payment currency so exchange-rate risk is not renegotiated monthly.
- Budget two to four weeks from role definition to start date.