Why “Remote” on LinkedIn doesn’t mean what you think

You set the filter to Remote. You are in Lisbon, or Kraków, or Valencia. You apply to thirty roles over a fortnight. Most say nothing. Two send a rejection that mentions, almost in passing, a requirement to overlap with Pacific time — or to hold US work authorisation, which was never stated anywhere on the posting.

The filter was not broken. It did exactly what it says. The problem is that "Remote" is not one claim — it is at least four, and a job board that stores it in a single field cannot tell them apart.

Four things a job board calls "Remote"

• Remote, anywhere — you can be paid where you live and work when you like.
• Remote, within a country or region — legally scoped, usually to where the employer has an entity. "Remote (Germany)" is a real and honest version of this.
• Remote, US-only — distributed across time zones, but the employment relationship requires US work authorisation. Common, rarely labelled.
• Remote-ish — a hybrid role whose posting leads with the remote days and mentions the office in the tenth bullet.

Only the first two are reachable from an EU address. Search interfaces flatten all four into one checkbox, which is why the checkbox does not protect you. The information is usually there — in the location string, the eligibility line, an office list near the bottom — just not in the field the filter reads.

The tell is in the location string, not the badge

A posting that says "Remote" in the badge and "Remote, Austin, TX" in the location line has told you what it means. So has one listing four US cities and no European office. A state code sitting after a comma — CA, NY, TX, MA — is the single most reliable signal that a role is scoped to the United States, and it appears in postings that never say "US only" anywhere.

This is learnable. It is also tedious, and you have to do it per posting, after the filter has already told you the role qualified.

What we do about it

We read the same signals, before the role reaches you. A posting has to clear four gates to be shown as EU-remote eligible: it must be a technical role, it must not be tagged on-site, hybrid, or US-only, it must carry at least one location signal that opens it to Europe, and it must not carry a non-EU restriction that nothing else overrides. That last gate is where most of the work is — a role listing "Amsterdam" and "Palo Alto, CA" is genuinely open to you, and rejecting it would be as wrong as admitting a Texas-only role.

We source roles direct from company career pages rather than from reposts, which is why the eligibility text is intact when we read it. The next post takes the filter apart gate by gate, including the cases where it is still wrong.

Check whether a company is actually remote — free, no signup