Most LATAM engineers who want a US remote job apply to the wrong places, in the wrong format, with the wrong proof. Then they decide the market is closed. It isn't. US companies are among the most remote-friendly employers you can apply to: in the 2025 Stack Overflow Developer Survey, the US had the highest share of developers working remotely among the top-reporting countries, at 45%. The door is open. You just have to walk through it the way a US hiring manager expects.
I read LATAM applications every week. Here is what separates the engineers who get offers from the ones who send 200 applications and hear nothing.
Key Takeaways
- US companies hire LATAM engineers mainly for timezone overlap and seniority, so lead with both.
- The screen is mostly about English, ownership, and proof you shipped real things, not a long list of technologies.
- A focused search (20 to 40 good applications) beats 300 one-click applies.
- Plan for 4 to 10 weeks from first application to signed offer. Faster through a partner that already vetted you.
Where the jobs actually are
There are four channels. They work very differently.
| Channel | What it's good for | The catch |
|---|---|---|
| LinkedIn and big job boards | Volume, seeing who is hiring | Hundreds of applicants per post, many roles are US-only |
| Remote-first boards (We Work Remotely, Remote OK, GetOnBoard) | Roles that already accept LATAM | Still crowded; filter by region |
| Direct to startups (careers pages, founders on LinkedIn, HN "Who's Hiring") | Less competition, faster replies | You do all the research |
| Placement partners like Ruzora | Roles that are LATAM-first by design, one vetting for many clients | You go through a structured process first |
The trap with LinkedIn is the "Remote" label. Often it means remote inside the US only, because the company has no way to pay someone abroad. Read the location line twice. If it says "US only" or lists states, move on. Don't argue with it.
What US companies screen for
When a US startup looks at a LATAM engineer, the questions in the hiring manager's head are simple:
1. Can I talk to this person at 10am my time without friction? That's English plus timezone. Put your timezone on your resume. Mention it on the first call.
2. Will this person own a problem, or wait for tickets? US startups are small. They want engineers who ask "why are we building this?" and then build it.
3. Have they shipped things real users touched? A resume that says "worked on the backend" loses to one that says "built the billing service that processes 40k invoices a month."
Your stack matters less than you think. A strong Python engineer who shipped production systems gets interviews for Go roles. A weak one with 12 frameworks listed doesn't.
The path, step by step
1. Fix the resume. US format, English, one or two pages, impact bullets. We wrote a full guide on the developer resume for US tech companies. No photo, no birth date.
2. Fix LinkedIn. Recruiters search it before they read anything else. Headline in English, with your stack and "Remote, UTC-5" style location detail. See our LinkedIn guide for LATAM developers.
3. Get your English interview-ready. Reading docs in English is a different skill from explaining a design choice live. Practice the second one. Here's how to pass a technical interview in English.
4. Know your number. You'll be asked for salary expectations on the first call. Have a USD figure ready. How to answer salary expectations covers the research.
5. Prepare for the assessments. Most US processes include a take-home or live coding round, and more of them now use async AI video interviews. Both have learnable rules: take-home challenges and AI video interviews.
6. Understand how you'll be paid. Contractor or employee through an EOR changes your taxes and your real take-home. Read how LATAM developers get paid by US companies before you sign.
7. Watch for scams. Fake "US remote" offers are common, and job seekers abroad are an easy target. Here are the red flags.
A Concrete Version
Take a composite engineer, call her Daniela: backend developer in Bogota, six years of experience, mostly Python and some Go, B2 English that gets nervous on calls.
In her first month she sends 90 LinkedIn Easy Apply applications. Two replies, zero interviews. Her resume is a two-page Spanish-style CV translated into English, with a photo and a list of 22 technologies.
Month two she changes the approach. She rewrites the resume around four shipped projects, each with a number (latency cut from 900ms to 180ms, a data pipeline moving 3 million rows a day). She drops Easy Apply and sends 25 targeted applications: 10 to startups hiring on HN's monthly thread, 10 to remote-first boards filtered for LATAM, and 5 to placement partners. She practices explaining one system design out loud, in English, every morning for 15 minutes.
Result: 7 first calls, 3 technical rounds, 1 offer in week 9. Same engineer. Different packaging and different channels.
The Honest Counterpoint
This path is harder for two groups, and I'd rather say it plainly.
If you have under three years of professional experience, most US startups hiring abroad won't take the risk. They hire LATAM engineers to get seniority, not to train. You're better off getting two more years at a strong local company or a US-facing agency, then applying.
If your English is below B2, fix that first. No resume trick gets you past a 45-minute technical call you can't follow. Our English guide for remote developer jobs has a realistic plan. And some roles really are US-only for legal or security reasons (defense, some healthcare data). Don't waste applications there.
Frequently Asked Questions
Do I need a US visa to work remotely for a US company?
Generally no, not for remote work done from your home country (general information, not legal advice; confirm your case with a local accountant or lawyer). You work as a contractor or through an employer of record in your country. A visa only matters if you'll physically work in the US.
Should I apply directly or through an agency?
Both, in parallel. Direct applications give you more options, a good partner gives you roles that already want LATAM engineers. We compared them in recruiting agency vs applying direct.
How long does it take to land the first US job?
For a senior engineer with B2+ English and a fixed resume, 4 to 10 weeks is a reasonable range. The first one is the slowest. After that, the US experience line on your resume does a lot of work.
The Bottom Line
The US remote market wants LATAM engineers. It wants them senior, clear in English, and able to show what they shipped. Fix those three things, apply in fewer and better places, and the numbers change fast. When you're ready, browse our open roles and apply to the one that fits your stack, like Python backend or fullstack TypeScript.
Roberto Espinoza is CEO of Ruzora, which places senior LATAM engineers with US startups. Browse open roles.
