Which Tech Roles Actually Travel, and Which Are Chained to a Timezone

Fewer than 5% of remote job postings are genuinely work-from-anywhere, no location attached (FlexJobs, 2026). The other 95% say "remote" and then quietly name a state.

But that 5% is not a random lottery. It is not that one company got generous and another did not. Whether a job can leave the country is mostly decided by the work itself, long before HR writes the posting, and the deciding factor is almost never how "technical" the role is. It is whether the work is asynchronous or synchronous, and whether the law lets the data cross a border.

So here is the role-by-role version I promised: which tech roles actually travel, which are chained to a clock, and which are walled off before you even apply.

The real variable is async, not "tech"

The instinct is to sort roles by seniority or by how much code they touch. Wrong axis. The axis that predicts whether a job survives a move abroad is how much of it has to happen at the same time as other people.

Most distributed teams quietly require about four hours of overlapping working time to function, enough to run a standup, unblock each other, and ship (Oyster HR / Rippling / HBS, 2024). Four hours is trivial if you are in Mexico City. It is brutal if you are in Bangkok, where the US workday lands in the middle of your night. So the honest test for any role is not "is it remote," it is "how many hours a day does this job need me awake at the same time as Denver."

That single question sorts the field.

Roles that travel well

These are the roles where the output is a thing, not a meeting. You are judged on what you shipped, and it does not much matter when you shipped it.

Backend and infrastructure engineering. Writing services, pipelines, and platform code is the archetypal async job: a ticket in, a pull request out, reviewed on someone else's schedule. It is no accident that Software Engineer is the single most common work-from-anywhere title in the FlexJobs data, and that software development is the largest single profession among US nomads (MBO Partners, 2025). If your day is mostly you and a codebase, your day mostly moves with you.

Data engineering and analytics. Same shape. Data Analyst is the second most common work-from-anywhere title (FlexJobs, 2026). Building models, pipelines, and dashboards is output work. The caveat is the meeting layer: an analyst embedded with a live business team, expected on every planning call, is closer to synchronous than one who delivers analyses on a cadence. Which kind you are predicts more than the title does.

Technical writing, and heads-down individual-contributor design. Docs, design systems, and IC product design that runs on written critique rather than live whiteboarding all travel. The moment the job becomes "facilitate the workshop," it stops.

The through-line: AI and DevOps engineering are the fastest-growing work-from-anywhere titles (FlexJobs, 2026), because the work is increasingly automated, output-graded, and reviewable after the fact.

Roles that are chained to a timezone

None of these are impossible abroad. All of them get harder the farther your clock drifts from your team's, and most of them quietly break past a few hours of offset.

Engineering management and any people-leadership role. Your job is other people's flow: one-on-ones, unblocking, incident calls, hiring loops. The work is the synchronous overhead. You can lead a team three hours away. Leading one twelve hours away means you are working nights, and you will not do it for long.

On-call SRE and production DevOps. This one is a trap, because the role looks technical and async on paper. But if you carry a pager, the question is whether your on-call window lands in your waking hours abroad. Being paged at 4am local for a US-daytime incident is survivable for a week and corrosive for a year. A follow-the-sun rotation actually makes this easier, if your employer runs one. Most do not.

Anything customer-facing in real time. Sales engineering, solutions work, customer success, live support. The customer is in a US timezone and expects you in it. The pay for these roles is real; the flexibility is not.

Meeting-anchored product management. A PM who runs the room, standups and stakeholder syncs and live prioritization, is synchronous by definition, even though Product Manager also shows up as a top work-from-anywhere title (FlexJobs, 2026). That contradiction is the point. "PM" spans a fully async write-the-spec-and-ship IC on one end and a calendar-is-the-job leader on the other. The title tells you nothing. The calendar tells you everything.

Roles that are walled off before async even matters

For a real slice of tech workers, none of the above applies, because the law or the contract says no before the timezone ever comes up. These are not "hard," they are closed, and I covered the enforcement basis in the cornerstone on working a US job abroad. The short version:

• Anything export-controlled: defense, aerospace, controlled tech. Accessing ITAR or EAR technical data while physically abroad is itself an unauthorized export, with civil penalties over $1.27 million per violation (22 CFR, 2025 figure). This is statute, not policy, and it does not care how async your job is.
• Security-clearance roles. Under SEAD-3, you must report and get advance approval for all personal foreign travel. A per-trip approval gate is incompatible with roaming.
• Registered finance roles. Under FINRA Rule 3110, the place you "regularly conduct" securities business becomes a registrable, supervised branch office. The rules assume a US, firm-inspected setup, not a rental in Lisbon.
• Government and CJIS-adjacent data work. The residency bar here is real but layered. It comes from contract clauses, the Defense Department's cloud security guidelines, and CJIS rules, not from a single statute. Assume it is there.

Two that get miscited: HIPAA and PCI-DSS impose security controls, not a country rule. If your health-data or payments employer says no, that is company policy, a real obstacle, but name it honestly as policy, not law.

The employer is the other half of the equation

Even a perfectly async role dies if your employer will not support it, and two things quietly decide that. The first is whether they can pay you where you are: platforms like Deel and Rippling let companies employ people in 185+ countries without a local entity (industry, 2026), so an employer already using one has a paved road, while one that is not may simply have no box in payroll for "lives abroad." The second is geofencing. Plenty of companies block foreign logins outright, and routing around that with a VPN is how a gray area becomes a fired area.

And keep the pay honest. Remote tech roles already run about 5 to 15% below their on-site equivalents in base salary (multiple surveys, 2025), before you add travel-medical insurance and a cross-border CPA. The arbitrage can still win. Just do the real math.

It is a search problem, not a packing problem

Here is where it lands, same as last time. Most people chasing this sort themselves by destination. The people who actually pull it off sort by role first, honestly, against the async test and the walled-off list, and only then filter the market.

Because the market will not filter itself for you. Ninety-five percent of "remote" postings are hiding a location line, and the 5% that are not are the entire game. That is exactly the read-past-the-label screening JobIntel is built for: it reads "remote" down to the restriction underneath, so you start from the listings that fit where you actually intend to be. Start your four weeks at jobintel.com and screen for the roles that can leave the country. Don't apply blind.

The where is the easy part. Whether your role can come with you is the whole question.