TL;DR

  • “Remote-first” and “async-first” are not the same thing. Most remote jobs assume you’re online 9–5 in a Slack channel.
  • Genuinely asynchronous work makes remote roles realistic for chronically ill, neurodivergent, and carer-disabled workers.
  • A handful of European-friendly employers genuinely operate async-first. Most don’t.
  • Read the language of the job ad. “Core hours”, “fast-paced”, and “always-on” tell you everything.

Most “remote” jobs in Europe aren’t asynchronous. They’re synchronous jobs you happen to do from your kitchen table.

If you’re managing a chronic illness, neurodivergence, caring responsibilities, or a body that doesn’t run on the same clock as everyone else, that distinction matters more than any other word in the job ad. A job that demands you be in a Slack channel from 9 to 5 with a four-hour reply window is structurally no different from being in an office. The walls have changed. The timing has not.

I’ve been writing about remote work in Europe since the early years of this century, and the category I see most frequently underserved – and most frequently misadvertised – is genuinely asynchronous work. The roles where deep work in your own time, on your own rhythm, is the actual norm rather than a grudging exception.

I sometimes think of async as the higher dimension of flexible working. We have to start with remote itself, and move towards flexibility on where the work is carried out. But once we’ve established that, the next thing that has to go is dependence on the clock. Employers who empower their people to deliver their best results when and how it works best for them create a win-win situation.

This article is for the people who already know they need this. Not because async sounds nice (it does, for most of us) but because synchronous remote work is, for them, simply not workable. Long-COVID. Limited energy windows. ADHD context-switching cost. Autistic sensory recovery time. The unpredictable pattern of caring for someone who has good days and bad days. Migraine cycles. The brain on its own schedule.

If you’re in that group, the standard remote-jobs advice (“try LinkedIn filters!”) will fail you, because LinkedIn doesn’t filter on the thing that matters. Below is what to actually look for, who’s hiring this way, and how to read between the lines of a job ad.

What “asynchronous-first” actually means

Asynchronous work is built on the assumption that no two people on the team are required to be online at the same time. Decisions get made through written documentation. Communication defaults to long-form: a thoughtful comment on a doc, a recorded Loom, a structured GitHub issue. Synchronous calls happen rarely, by exception, with a clear agenda.

In practice this means status updates are written, not spoken. Meetings are the last resort. The expectation is that you respond within a working day or two, not within an hour. Your work product is what gets evaluated, not your activity timeline.

What this is NOT:

  • “Remote-first” – most remote-first companies still operate synchronously over Slack.
  • “Flexible hours” – flexibility usually means a flexible start time, not “respond when you can”.
  • “Distributed across time zones” – even distributed teams can demand four-hour overlap.
  • Being able to work from a beach.

You can tell whether a company is genuinely async-first by reading their public documentation. Doist, GitLab, 37signals, and Automattic all publish their working principles. If a company can’t show you in writing how they communicate, they probably haven’t thought about it. That alone is a signal.

Why async-first is structurally accessible

Remote work without async isn’t accessible. It’s the same demands, performed in your kitchen.

When the structural assumption is real-time synchronous communication, every form of disability that affects energy, predictability, or context-switching becomes a daily negotiation. You spend cognitive load not on the work but on the meta-work: timing your replies, masking fatigue, performing availability. That cost is real, and it is the thing that tips employability even in jobs that look like they should suit you.

Truly async-first companies don’t have to make accommodations, because the structure is the accommodation. You take a long lunch and respond at 4pm. You work in two-hour windows, not eight-hour blocks. You write your thinking once, properly, instead of summarising it five times across different threads. You disappear for the school run. You handle a flare-up day without telling anyone, and the work still moves.

The companies that operate this way write about “long-form communication” as a core skill, measure outcomes rather than activity, and have explicit policies on how long you have to respond. That language tells you whether the structure exists, not whether the company likes you. The fact that we now have amazing AI tools to help us with this kind of communication makes async even more accessible than it was in the past: Need to catch up on messages or summarise an update? Translate it into your first language? All of this is so easy now. But working in this way at an organisational level remains sadly far from the default

The accessibility benefit is not a side effect. It is, increasingly, the design intent. Doist has written publicly about why async helps neurodivergent team members specifically. GitLab’s handbook treats time-zone fairness as a core design principle.

European-friendly employers genuinely operating async-first

These are companies where the public written record demonstrates async-first practice. I’m naming them because vague claims about “async cultures” without evidence are exactly what wastes your time.

  • Doist ( fully distributed) – makers of Todoist and Twist. Async-first since founding. Hires across Europe in customer support, marketing, engineering, and content.
  • GitLab (EMEA-wide) – the canonical distributed-first handbook. Operates across all time zones. Around 2,000 staff. Salary bands published; non-tech roles run €60K–€110K depending on level.
  • Automattic (UK / EU presence) – makers of WordPress.com, distributed for around 20 years. Strong async culture. Hires Happiness Engineers, content, engineering, operations.
  • 37signals / Basecamp (US-based, hires Europe) – the “Calm Company” model. Very strong on async, written-first. Limited hiring but consistently good roles.
  • Buffer (distributed, EU presence) – async-first, transparent salary system. Marketing, customer advocacy, engineering.
  • Zapier (distributed, hires EU) – async-strong, widely-published practices.
  • Hostinger (Lithuania / EU-wide) – not classically async-first, but operates with significant async overlap due to its EU-wide distribution. Worth investigating role by role.

A note on the US-based companies on this list: tax and EOR setup is the variable. If a company can hire you in your country (often via Remote.com, Deel, or a direct entity), they’re a real option. If they require you to relocate to a list of “approved” countries, they’re not.

How to spot fake async in a job ad

The language is the giveaway. Words that should make you cautious:

  • “Core hours” – there will be required overlap, often four hours. That isn’t async.
  • “Responsive” or “fast-paced” – synonyms for “stay in Slack and answer quickly.”
  • “Daily standups” – synchronous by definition, even if remote.
  • “Flexible hours within UK working day” – flexibility within a constraint, not async.
  • “Always-on” – exactly what it sounds like.
  • “Strong communication skills” with no further detail – often code for “available”.

Obviously there are roles where core hours and responsiveness are absolutely appropriate, but when you see this kind of verbiage in roles which are not interdependent by nature, they are culture signals you should take note of, and be ready to probe at interview. What is the meeting cadence for this role? What kind of response times are expected in your chat? etc.

Words that suggest the real thing:

  • “Long-form writing”, “documentation-first”, “writing-heavy”.
  • “Outcomes over activity”, “results-based”, “deep work blocks”.
  • “Async-by-default”, “meetings by exception”.
  • “Response window of 24–48 hours” or a similar explicit policy.
  • “Decisions made through written proposals”.

When in doubt, search “[company name] async” or “[company name] handbook”. If they have a public document explaining how they communicate, read it. If they don’t, the silence is your answer.

What to do if a role looks good but isn’t async

Most jobs aren’t async-first. Sometimes you find a role that’s right in every other way – pay, field, level – but the company runs synchronously. You have three honest options.

The first is to take the role on its terms and make peace with the cost. For some readers, that’s not viable. For others, it’s the price of a job that’s otherwise excellent. Be honest with yourself about which.

The second is to negotiate before signing. The phrase that works in interview: “I deliver my best work in async conditions. What does that look like at [company]?” That reframes the conversation as a question about how the company already thinks about deep work. The answer tells you everything. Companies with no answer aren’t going to develop one for you, and then you’re back to option one: “Can I work with this?” Only you know the answer to that.

The third is to use the legal frameworks where they apply. The UK Equality Act 2010 covers reasonable adjustments. EU member states each have their own disability-rights provisions. If you have a recognised disability, working-pattern adjustments are within scope as adjustments. This works better in regulated sectors than in fast-growth start-ups, and it’s not a shortcut for a structural mismatch.

Disability-confident hiring in Europe in 2026

The async question is one piece of a broader disability-and-remote-work conversation:

  • Evenbreak is the UK’s specialist disability jobs platform. It vets employers and lists genuinely accessible roles. Worth bookmarking.
  • The UK Disability Confident scheme is a kitemark, not a guarantee. Level 3 employers commit to offering interviews to disabled candidates who meet minimum criteria. Useful as a filter, not as proof.
  • The European Accessibility Act (EAA), in force since June 2025, is reshaping how products and services across the EU account for disability. It also creates demand for accessibility-aware roles (UX research, content design, compliance) that lend themselves to async work.
  • Reasonable adjustments in the UK – and equivalent provisions in EU member states – cover both equipment and working arrangements. Document everything in writing. Verbal agreements collapse under management changes.
  • EU member states’ frameworks vary widely. Spain’s IMSERSO, Germany’s SBV (severely-disabled representative), France’s RQTH framework – each has its own logic. RWE doesn’t give legal advice; we’d point you to specialist organisations in your country.

The deeper point: a workplace that supports async tends to support disabled workers. Not perfectly, not always, but structurally. The companies that build for one tend to build for the other.

FAQ

Is async-first the same as part-time? No. Async-first companies typically hire full-time. The hours are the same. The expectation is that you choose when to do them.

Will async-first work pay less? Usually no. The companies named above pay in line with full-time-equivalent benchmarks for their sector. Some (GitLab, Buffer) publish their salary bands openly. The market is competitive.

Can I get an async accommodation inside a synchronous company? Sometimes, particularly in regulated sectors and larger employers. The legal frameworks (UK Equality Act, EU member-state equivalents) cover working-pattern adjustments. It’s harder than choosing an async-first company in the first place.

How do I know if a company is genuinely async without joining it? Read their public handbook or culture document. If they don’t have one, look at Glassdoor reviews specifically for words like “Slack”, “meetings”, “always on”. If you have a contact, ask one direct question: “What’s the longest you’ve gone without responding to a Slack message?”

What if I need async because of caring responsibilities, not a recognised disability? The legal route is narrower (UK has flexible-working request rights from day one of employment as of 2024), but the principle holds. Start with the structural async employers. They’ll be friendlier in the negotiation.

Are there async roles for non-tech people? Yes. Customer support, content writing, marketing, finance, operations, HR. The companies named above hire across all of these. Async-first isn’t a tech thing. It’s a writing-discipline thing.

Want help finding roles like these?

Diana hand-picks European remote roles every week for Connected, our curated weekly job club. The async-first and accessibility-aware roles get flagged specifically. It’s how we save you the LinkedIn-filter-roulette.

Related reading on RWE: non-tech remote careers in Europe, remote work over 40, how to spot remote work scams.