Remote Job Description: How to Write One That Gets Real Candidates

A remote job description should do one job: make the wrong candidates self-select out before they apply. That means seven things stated plainly near the top, the salary range, the timezone or state requirement, the level, the reporting line, the core hours, the tools, and what the first 90 days look like. Everything else is decoration.

Most postings get this backwards. They open with three paragraphs about company culture, list fourteen bullet points of responsibilities that could describe any role at any company, and never say what it pays or where you have to be. Then the hiring manager wonders why 400 people applied and six were relevant.

Why remote job descriptions need to be written differently

When a role is on-site, geography does most of the filtering for you. Only people who can reach the office apply, they already know roughly what the local market pays, and the commute constraint quietly screens out anyone for whom the job does not fit their life.

Remove the office and all of that filtering disappears. Your posting is now visible to everyone in the country, or the world, and the description is the only filter left. If it is vague, you get volume. Volume is not a win: at two minutes per application, 400 applicants costs a hiring manager more than 13 hours before a single interview happens.

So the goal is not to attract as many applicants as possible. It is to attract the smallest number of genuinely qualified, genuinely available people, and to lose everyone else in the first thirty seconds of reading.

The seven things to state before the fold

Put these near the top, before any culture copy. Every one of them is a filter.

• Salary range. A real range, not "competitive". This is the single most effective filter you have, and in several states it is legally required anyway.
• Location requirement. Fully remote worldwide, remote within the US, remote in specific states, or remote within a timezone band. Say which. "Remote" alone is the most common cause of a wasted first call.
• Core hours. If you need four hours of overlap with Eastern time, that is a hard requirement and belongs at the top, not in paragraph nine.
• Level and reporting line. Who this person reports to and how many people they manage, if any. Senior means nothing across companies; a reporting line is concrete.
• Employment type. Full-time W-2, part-time, or 1099 contract. Candidates filter hard on this and the difference in take-home pay is large.
• The stack. The three or four tools this person will live in daily.
• What success looks like at 90 days. Two or three sentences. This is what separates a description someone remembers from one they skim.

Write responsibilities as outcomes, not verbs

Compare these two lines for the same job:

Manage the customer support queue and respond to inbound tickets in a timely manner.

Own a queue of roughly 120 tickets a week, hold first response under two hours, and cut our repeat-contact rate from 22 percent by rewriting the top ten help articles.

The first is unfalsifiable and describes ten thousand jobs. The second tells a good candidate exactly whether they have done this before, and tells a weak one that they have not. It also does something a generic bullet cannot: it makes the person reading it picture the work.

Four to six of those beats fourteen generic bullets every time. If you cannot write a responsibility as a measurable outcome, ask whether it is actually a responsibility or just a task that arrives sometimes.

Requirements: separate must-have from nice-to-have, then cut both

Long requirement lists are expensive in a specific and well-documented way. Candidates who match every bullet apply confidently; candidates who match most of them, particularly women and career changers, often do not apply at all. Since the second group contains a lot of your best hires, an inflated list costs you the exact people you wanted.

The fix is mechanical. Write the requirements, then delete anything that a competent person could learn in the first month. Then split what remains into two short lists and label them honestly. Three to five must-haves is normal. If you have nine, you are describing two jobs, or a person who already has the job somewhere better.

Drop degree requirements unless the role legally needs one. For most remote roles they filter on background rather than capability, and a portfolio, a work sample or a documented process improvement predicts performance far better.

What to say about pay, and why the range has to be real

Pay transparency laws in Colorado, California, New York, Washington, Illinois and a growing list of others require a good-faith salary range on postings open to residents of those states. Because a fully remote US role is by definition open to residents of those states, in practice a remote posting needs a range whether or not your own state requires one.

Beyond compliance, the range is your best filter. It removes candidates who need more, which saves you both a wasted process, and it removes the negotiating theater where you spend three interviews discovering a gap you could have found in paragraph one.

Two practical notes. Publish a range you would actually pay across, not a band so wide it is meaningless. And state your geographic pay policy plainly: whether the range is national, or adjusted by location. Candidates will ask on the first call regardless, so answering it in the posting saves the call.

A remote job description template you can copy

Use this structure and fill it in. It reads short because it should be.

1. Title, and only the title. No internal jargon, no roman numerals nobody outside the company understands. Use the title candidates search for.
2. One paragraph on the company. What you sell, to whom, how large the team is, and that you are remote-first. Three sentences.
3. The facts block. Salary range, location or timezone requirement, employment type, reporting line, core hours. Bulleted, scannable.
4. What you will own. Four to six outcome-shaped bullets with numbers in them.
5. What we need you to have done before. Three to five must-haves, then a short nice-to-have list, clearly labeled.
6. Your first 90 days. A short paragraph describing week one, month one, and what done looks like at ninety days.
7. How hiring works. The number of stages, who the candidate meets, whether there is a paid exercise, and the expected timeline. Publishing this is rare enough that it is a genuine advantage.

Common mistakes that cost you good applicants

Calling a hybrid role remote. This is the fastest way to burn goodwill and it shows up in reviews. If the role requires two days in an office, it is hybrid; say so and you will still find people, just not the same people.

Hiding a hard state restriction at the bottom. If you can only employ in twelve states, that belongs in the facts block. Candidates who read it in paragraph eleven, after writing a cover letter, remember the company for the wrong reasons.

Asking for "a rockstar who wears many hats". In a remote role, ambiguity about scope is not charming, it is a warning sign, because there is no hallway in which to renegotiate the job later.

Writing the description and then posting it in the wrong place. A well-written description on a general board still returns mostly noise, because the audience is not filtered. The description and the channel do different halves of the same job. Our breakdown of what it costs to post a remote job covers which channel fits which role, and the comparison of LinkedIn vs Indeed for remote jobs covers the two giants specifically.

After the posting: expect to source, not just wait

For competitive roles, a good description plus the right board fills the top of your pipeline, not all of it. The candidates you most want are usually employed and not reading job boards this week, so the second half of the work is going to them directly. That is a different discipline: building a short list of people who have done the exact thing, then researching each one properly and writing outreach they will actually reply to rather than blasting a template at two hundred profiles.

The description still does the heavy lifting there, because it is what you send when someone replies asking what the role is. A posting that states the pay, the constraint and the ninety day outcome converts a lukewarm reply into a first call. A vague one does not.

Frequently asked questions

How long should a remote job description be? Between 300 and 700 words for most roles. Long enough to state pay, location, level, outcomes and process; short enough that a strong candidate reads all of it. Postings past about 900 words see meaningful drop-off, and the extra length is almost always generic culture copy rather than information.

Do I have to include a salary range in a remote job posting? In practice, yes. Pay transparency laws in Colorado, California, New York, Washington and others require a good-faith range on roles open to their residents, and a fully remote US role is open to them by default. Beyond the legal question, the range is the most effective filter in the posting.

Should the job description say fully remote or remote-first? Say fully remote if there is no office requirement at all, and state the geographic limit alongside it, for example "fully remote, US only, must overlap 9am to 1pm Eastern". Remote-first describes how a company operates, which is worth saying too, but it is not a substitute for the concrete constraint.

How do I write a job description that does not attract unqualified applicants? Put the three hardest constraints at the top: the salary range, the location or timezone requirement, and two or three specific things the person must have already done, written with numbers. Vagueness attracts volume, specificity attracts fit. Cutting the requirement list to five real must-haves also helps, because inflated lists deter strong candidates more than weak ones.

When the description is ready, put it in front of an audience that matches the role. Plans and pricing are on remote job posting sites, the step by step is in how to post a remote job, and the wider case for hiring remotely is on hire remote workers.