How to Write a Remote Job Description That Converts

Most job descriptions are written to protect the company. The good ones are written for the candidate. That single flip is why some posts collect qualified applications all month and others, sometimes for the exact same role, sit in silence.

Think of it this way: your listing is a landing page. It has one conversion goal, which is a relevant candidate clicking apply. Every line either moves toward that goal or against it. Here is the structure we would use every time.

Lead with the actual work

The first paragraph should describe the work, not the company's founding myth. Candidates read the first three lines on a phone, usually between other things, and decide whether to keep going. "You will own our onboarding flow, ship weekly and work directly with the design lead" gives them something to want. "We are a rapidly growing company at the intersection of innovation and passion" gives them a reason to close the tab.

Company background has its place: two or three honest sentences, further down. What the candidate does matters more than who you are, at least at the moment they are deciding to apply.

Say the salary. Yes, the real one.

Nothing else on this page moves the needle as much. Posts with a clear number get more applications, and more importantly they get the right applications. You stop hearing from people who need double, and you start hearing from people who read the number and still came.

If the range is wide, say what moves a candidate to the top of it. "€55k to €70k, the top of the range needs production experience with TypeScript at scale" is more persuasive than any adjective.

There is a second benefit people miss: salary transparency changes the tone of every later conversation. Nobody negotiates from a place of manufactured ignorance, and offers stop collapsing at the last step because expectations were misaligned from day one.

Be honest about the annoying parts

Every role has a downside and pretending otherwise just delays the discovery. Time zone coverage, on call weeks, the messy legacy system nobody is proud of, quarterly office trips. Name them plainly.

The paradox is that honesty raises your apply rate from the people you actually want. Senior candidates read candour as a signal of a healthy culture, because it is. Companies that hide the hard parts usually manage that way too.

Describe a real day

One short paragraph, written like a diary entry: "Your morning starts around 9 with a code review and the standup note. Before lunch you usually ship something. Afternoons are for deeper work, one meeting at most. Twice a week you pair with the product engineer on whatever is blocking support."

That paragraph does the work of ten bullet points, because it lets the candidate test themselves against the job. Do I want this day? Can I do this day? The self selection alone will save you a week of screening.

The outline we would copy

1. One line hook: the role, the level, the pay band.
2. The mission of the role: what this person owns and why it matters.
3. A real day, in two or three sentences.
4. Must haves, five maximum. Separate from nice to haves.
5. Pay, benefits, location rules and required hours.
6. The hiring process, with timelines. How many calls, what you send back, how long it takes.
7. Two honest sentences about the company.
8. A single, obvious way to apply.

Number six matters more than you think. Remote candidates are burned by processes that vanish for weeks. Publishing your steps and your timeline is a competitive advantage against every company that does not.

Words to cut immediately

• "Rockstar", "ninja", "wizard". Nobody with five years of experience self identifies this way.
• "Fast paced environment". Says nothing, scares parents and carers.
• "We are a family". It is a job. Good jobs with honest terms attract adults.
• "Wear many hats". Sometimes true, but phrase it concretely: "you will own marketing and the website until we hire a second marketer".
• "Competitive salary". It reads as an omission, because it is.

Quick answers

How long should a remote job description be? Around 400 to 700 words. Long enough to answer the real questions, short enough to read on a phone without a contents bar.

Should I include the hiring process in the post? Yes, with timelines. It lifts apply rates from serious candidates and reduces the "just checking in" emails that eat your week.

Can I reuse one description across several boards? Mostly yes, but adjust the first paragraph and the title per board. Different audiences skim differently, and the first three lines decide everything.

Once the description is ready, the next step is distribution. Start with how to post a remote job, check our listing guidelines so your post sails through review, then publish it here. If your live post is quiet instead, the fix list in why your job post got no applicants covers the usual suspects.