Real vs Fake Remote Jobs — How to Tell in 2026

The reclassification of "remote"

Around 2022, a quiet shift happened across UK and EU job postings. "Remote" stopped meaning "you can work from anywhere" and started meaning whatever the company felt like that month. By 2025, the single word covered everything from genuinely-distributed companies where you've never met your team in person, through "remote-first but you'll come to the office every fortnight", down to "we call this remote but expect you in three days a week and won't relocate you."

The result is that filtering job listings by "Remote" in 2026 is mostly useless. You'll get a mix of all three, and the third category dominates by volume. This guide is how to spot what you're actually applying to before you spend an hour writing the application.

Three categories, in plain English

Genuinely remote-first — the company has no expectation of office attendance ever, hires anywhere within the legal jurisdiction (UK-only, EU-only, sometimes globally), and runs everything async. You can work from a different city to your team, never visit, and nothing changes. This is rare and getting rarer.

Remote-but-with-strings — the company says remote in the listing but specifies one of: "you'll come to the office monthly", "occasional travel for offsites", "team gathers quarterly", "remote within 90 minutes of London". These are real jobs and often great ones, but they aren't fully remote. If you live in Manchester and the team "gathers quarterly in London", that's £200 in train fares and a hotel four times a year on you, plus the practical reality that the people who attend in person form the relationships that drive promotion.

Remote-as-a-recruiting-tactic — the listing says remote because "hybrid" gets fewer clicks. The actual expectation is in-office 2–3 days a week, the location is given as the city the office is in, and "remote" was added so the role appears in remote-job filters. You don't find this out until the screening call, after you've sunk an hour into the application.

How to tell which category you're looking at

Read the JD carefully. The signals are usually there:

Genuinely remote signals:

• The location field says "Remote (UK)" or "Remote (Europe)" with no city.
• The company has a careers page that explicitly states their work model (e.g. GitLab's handbook on async work, Buffer's distributed team docs).
• Salary is offered in a single currency for the whole geography (USD, GBP, EUR) — companies that hire across geographies usually flatten salary across them.
• Job mentions "async-first", "documentation-heavy" or "no office".
• Time zones explicitly named ("EU timezones", "GMT ±3").

Remote-but-with-strings signals:

• The location field says "Remote (UK) / London" — the slash gives it away.
• "Occasional travel for team building" or similar phrases.
• "We meet in person quarterly" / "All-company offsite once a year".
• A specific city named alongside Remote.
• Salary range given for that one city only.

Remote-as-recruiting-tactic signals:

• The location field says "Remote, London" or "Hybrid (London)".
• "Some flexibility to work from home" in the JD body — this means in-office most of the week.
• "We have a beautiful new office in [city]" anywhere in the JD.
• Benefits list includes "free lunch" or "commuter scheme" — the company expects you to be there to use them.
• The "remote" tag conflicts with a specific location field; the location field wins.

UK and EU companies that are genuinely remote-first

This list shifts year-on-year as companies tighten or relax their work models. Roughly accurate for 2026:

Genuinely remote-first (UK and EU hiring):

• GitLab — fully distributed since 2014.
• Automattic (WordPress.com) — fully distributed.
• Zapier — fully distributed.
• Buffer — fully distributed.
• Doist — fully distributed.

Remote-first with occasional gathering:

• Plausible Analytics — quarterly meetups.
• Posthog — quarterly offsites.
• Wildbit — yearly retreat.

Remote-friendly within the UK with strings:

• Monzo — selective; some teams remote-by-default, others 2 days in London.
• GoCardless — selective by team.
• Snyk — hybrid but flexible.

Worth knowing about as part-time remote:

• The civil service and NHS now offer "blended" remote roles for many digital professional grades. They're worth applying for but expect 1–2 days per week in a regional office.

What to ask in the screening call

If you've applied to a role labelled remote and you're not sure which category it fits into, the screening call is when to find out — before you go further into the process. Specific questions that get specific answers:

1. "What's the team's actual day-to-day office attendance pattern?" — vague answers ("we trust our people to find a balance") are a tell for category 3.
2. "How often does the team meet in person?" — quarterly is standard for remote-first; weekly is hybrid in disguise.
3. "Is the salary the same regardless of where I'm based?" — yes-answer means category 1 or 2; no-answer with "we adjust by region" means London is the centre of gravity.
4. "Are key meetings and decisions captured in writing?" — async companies say yes immediately; office-default companies pause.

How KeyStep filters this

The /remote-jobs page tags listings based on JD language, not just the listing's "Remote" tag. We flag category-3 listings (remote-as-recruiting-tactic) and demote them from the remote feed. The result is fewer total listings on /remote-jobs than on a generic remote-jobs board, but a meaningfully higher match rate.

If you're committed to going fully remote, the strategy is:

1. Filter by /remote-jobs on KeyStep.
2. Run KeyMatch on each role above 75 score.
3. Read the JD carefully for the signals above.
4. In the screening call, ask the four questions in this guide.

The candidates who land genuine remote-first roles aren't the ones who apply to the most "remote" listings. They're the ones who filter hard, ask precisely, and walk away from category-3 setups before they've sunk weeks into the process.