Search for remote jobs worldwide and you get thousands of results in a second, which is the problem. A few of them are postings a company will hire for from any country. The rest say remote at the top and name a country in paragraph nine. Last night we read 12,686 live remote-claiming listings across 657 company hiring systems and labeled which was which. Here is what the split looks like, and which roles keep landing on the right side of it.
What the nightly scan says about remote jobs worldwide
Every listing that claims remote ends the night in exactly one of three states. It is locked to a place, or nothing restricts it but nothing confirms it either, or the company states outright that it hires worldwide. There is no fourth bucket and no guessing. Out of 12,686 live remote-claiming listings last night:
| State | What it means | Listings | Share |
|---|---|---|---|
| Locked | The posting names a country, a region, a timezone overlap or a language requirement | 10,959 | 86.4% |
| No lock found | Nothing in the posting restricts you, and nothing confirms worldwide hiring | 1,480 | 11.7% |
| Confirmed open worldwide | The posting states that the company hires from anywhere | 247 | 1.9% |
Read the bottom row as odds: roughly one in 51 listings tagged remote will tell you in writing that it hires worldwide. That is a small number and the honest one: a job only enters that state when the posting says so. The middle row is the one most job boards quietly count as open, and it is why people keep reaching a final round before anyone mentions payroll.
That pool is what is left after reading more than 49,000 postings a night, straight from company hiring systems: Greenhouse, Lever, Ashby, Workday, SmartRecruiters and a set of feeds. What gets parsed is the employer's own posting text and location fields, not a copy of a copy, and anything that has vanished from the source comes off the board the same night. The methodology page has the checks in order.
Which roles are truly open globally
The pattern behind worldwide-open postings is consistent: the work is judged by what it produces, it survives a twelve-hour gap between question and answer, and it does not need anyone standing in a room. Four categories fit that description.
Backend and infrastructure engineering
Server-side work is the most portable engineering there is. The interface between you and the team is a pull request, a design doc and an alert, all of which assume the reader is somewhere else and probably asleep. Companies that would never hire a designer eight hours away will hire a distributed-systems engineer there, because the review process was written down long before anyone thought about timezones. Skills that travel: Go, Rust, distributed systems, Kubernetes, cloud architecture, database internals. You can browse engineering roles on the board with the locks already labeled.
Technical writing and developer relations
Documentation, API references, tutorials and developer education are produced alone and reviewed asynchronously. Distance is close to free here, and spread is an asset: a docs team across three continents answers questions around the clock without anyone working a night shift. The catch is that developer relations often carries a conference travel expectation, a soft geography requirement with a budget attached, so read the travel line before assuming the role is as open as the writing. Skills that travel: API documentation, docs-as-code, developer education, open-source community work.
Security engineering and incident response
Security is one of the few functions where being far away is the requirement rather than the concession. Coverage follows the clock, so a team spanning continents gets follow-the-sun monitoring without paying anyone to stay awake. The exception is worth knowing: security roles touching regulated data, government contracts or clearances carry the hardest residency and citizenship locks we see anywhere. The same job title can produce the most open and the most locked listing on the same board. Skills that travel: application security, cloud compliance, detection engineering, penetration testing.
Design systems
General product design still sits inside synchronous rituals: sprint planning, live critique, whiteboards. Design systems work does not. Components, tokens, accessibility specs and usage documentation are built once and consumed by everyone else on their own schedule, which makes it behave more like infrastructure than product design. Skills that travel: Figma, design tokens, component APIs, accessibility, front-end integration.
None of that is a guarantee, and the caveat matters more than the list. Company policy beats job family every time. What a role category buys you is better odds per hour of searching, which counts when most work from anywhere listings turn out to be locked once you read to the end.
Why companies lock remote jobs to a region
Locks are not arbitrary, and they cluster. These were the places named most often across last night's locked listings, with each one's share of that locked pool:
| Place named in the posting | Locked listings | Share of locked |
|---|---|---|
| USA | 6,592 | 60.2% |
| Canada | 717 | 6.5% |
| United Kingdom | 603 | 5.5% |
| EMEA | 336 | 3.1% |
| Germany | 285 | 2.6% |
| Americas | 270 | 2.5% |
One listing can name more than one place, so the column does not sum to the locked total. Two things stand out anyway. The concentration at the top is extreme: a large share of what looks like a global market is one national market with a remote tag on it. And the region labels, EMEA and the like, are shortlists wearing a continent's name, meaning the countries where the company already has entities.
- Payroll and tax registration. Employing someone in a country requires an entity there, a provider that has one, or a contractor agreement. Each carries a setup cost and a legal review, so companies reuse the countries they already opened.
- Permanent establishment risk. Staff working from a foreign country can create a taxable presence for the parent company. That risk is why country allowlists get written and why they change slowly.
- Meeting habits. Teams that make decisions live have to keep everyone inside a band of hours. A timezone requirement showed up in 1.1% of live remote-claiming listings last night, small next to geography at 85.6%, but those are the ones that pass every location filter and still exclude you.
Language accounts for 5.1% of the same pool, and 5.4% carry more than one axis at once. Employer of Record providers are how companies get out of this, and they help: each of the larger ones reaches roughly 50 to 150 countries. But an employer activates a subset and pays per country, which is why "we hire globally through an EOR" and "we can hire you" are different sentences.
How to filter for genuine remote jobs worldwide
- Look for the affirmative sentence. Work from anywhere, anywhere in the world, we hire in any country. Confirmation is a sentence someone wrote on purpose, not an absence of restrictions.
- Read the location field and the body as separate claims. The field is a dropdown someone picked in thirty seconds. The body is where legal put the constraint.
- Treat every region label as a shortlist. Ask which countries inside the region, and you will often get a list of three.
- Find the overlap clause. It is usually one line in the requirements section and it is the lock most likely to survive your filters.
- Be careful with re-posted listings. When a posting is copied onto general job boards and aggregators, the fine print is what gets trimmed. Go back to the company's own posting before you apply.
Or start from the answer. The open-worldwide board holds only the confirmed state, 247 listings as of last night, rechecked tonight. The daily letter takes your country once and sends the jobs you clear each morning, and the full board shows the locked ones too, labeled, so you can judge a near-miss yourself.
What "no lock found" is worth
The middle state is the biggest of the three after locked: 1,480 listings last night, 11.7%. Nothing in the text limits you. Nothing confirms worldwide hiring either. Some of those are open and nobody thought to write it down, and some carry a country rule that lives in the applicant tracking form rather than the posting.
The practical version: that bucket is worth one email, not a cover letter. Ask which countries they can employ in today. If the answer includes yours, you have found a worldwide-open job that was never advertised as one, ahead of everyone filtering for the confirmed label. If it does not, you spent two minutes instead of an evening.
What we will not do is count that bucket as open. It would make our worldwide number look better and put you in exactly the position this search is trying to avoid. Locked listings tell you the truth up front. Unconfirmed listings are a question worth asking. Only the third state is an answer, and with nearly 9 in 10 listings locked, the difference between the three is most of what a remote job search is.