Writing a Remote Job Description That Filters Correctly

A remote posting reaches a far larger audience than an on-site one. That is the advantage and the problem: without specificity you receive hundreds of applications from people who cannot legally be employed, cannot work your hours, or will discover a mismatch at the offer stage.

The four facts that do the filtering

Where you can employ. Not "remote" — the actual list of countries or states. This is the single highest-value line in a remote posting and the one most often missing. Candidates who cannot be employed where they live should learn it in the posting, not in week three.

The overlap requirement. "Four hours overlap with Central European Time" is a real constraint that people can self-assess against. "Some overlap expected" is not.

Any in-person requirement. Quarterly gatherings, occasional client visits, an onboarding week. If travel is expected, say how often and roughly where. People with caring responsibilities or visa constraints need this before they invest in a process.

Compensation range. Increasingly a legal requirement in a growing number of jurisdictions, and independently the fastest way to stop wasting everyone's time. If pay varies by location, say how.

A posting with those four is clear. Without them, you are outsourcing your ambiguity to candidates.

Describe the job, not the culture

Most postings spend three paragraphs on values and one on the work. Candidates skim the values and read the work.

What will this person own? Not tasks — outcomes. What should be true in six months.

Who do they work with? Team size, who they report to, which functions they depend on.

What does a normal week look like? Roughly how much is meetings, how much is independent work, how much is reactive.

What is hard about it? A posting that names a genuine difficulty attracts people who want that difficulty and repels people who would leave when they found it. Both are wins.

Requirements that shrink your pool for nothing

Years of experience as a proxy for capability. It filters out career changers and people who developed quickly, and does not filter out anyone who accumulated years without learning.

Degree requirements where the work does not need one.

Long tool lists. "Experience with fourteen named platforms" describes nobody and deters people who could learn the fifteenth in a week.

"Must have remote experience." Working remotely is not a skill so specialised that it cannot be acquired. What you actually want is written communication and self-direction, which you can assess directly.

Each unnecessary requirement disproportionately deters candidates who already doubt they belong, which tends to mean the ones you are trying to reach.

Language that misleads

"Remote-first" with a mandatory office week is not remote-first, and candidates will notice at the offer stage.

"Flexible hours" alongside a calendar of fixed meetings.

"Unlimited holiday" where the actual norm is less than a statutory entitlement elsewhere. State the expected minimum.

"Fast-paced" and its relatives. These read as warnings, which is fine if intended.

Every gap between the posting and reality is discovered eventually, and the discovery costs more than the honest version would have.

Make it readable

Short paragraphs. No wall of bullet points. Under 700 words for most roles.

Say what the next steps are and how long they take. Candidates comparing several processes will favour the one that told them what to expect.