How to Write a Remote Job Post
What to include in a remote job post so candidates can tell the role is real, the hours are clear, and the application is worth their time.
She Works Remotely · Published September 22, 2026 · Last reviewed September 22, 2026
Candidates decide in a minute whether a remote post is real. They look for the company name, the work, the hours, the pay if you have it, and a normal way to apply. A post that hides those facts attracts people who did not read it and repels people who did.
Write the post as if you will have to answer it in an interview. If you cannot describe the first month of work, the listing is not ready.
Who this guide is for
Employers and hiring managers posting a remote role on She Works Remotely
Founders writing their first job post without a recruiting team
Name the work and the setup
The title should be a job a person can recognize: "Customer support specialist" beats "Remote rockstar." Say whether the role is fully remote, which timezones must overlap, and whether it is full-time, part-time, or contract.
Company name and a sentence on what the company does
The tasks for the first 30 days, in plain language
Timezone or overlap hours, and employment type
The application path: on She Works Remotely, or a link you control
Pay range if you have one. "Competitive" tells candidates nothing
Make the requirements a filter, not a wish list
List what the person must already be able to do. Separate tools they can learn. A long list of nice-to-haves makes qualified people skip the role, especially people returning to work or changing fields.
Must-have: the skill the job fails without
Should-have: useful, not blocking
Do not require a degree unless the work legally needs one
Do not ask for free work samples that take hours. A short existing sample is enough
Tell people how you hire
Say how many conversations to expect and who they will meet. Say you will not ask for money, equipment purchases, or a private messaging app as the only way to apply. Those patterns are how scams present themselves, and serious candidates are watching for them.
Where the application goes
What the first conversation covers
How long you try to reply
How a candidate can ask a question
Practical examples
A support role that is easy to trust
Title: Customer support specialist (remote, Americas hours). The body lists email and chat coverage, 9–5 ET, a published salary range, and an application on the company site. The requirements are writing clearly, using a help desk, and reliable internet. "Bonus" is a second language, not a blocker.
A post that will be ignored
Title: Remote ninja. No company name. "Competitive pay." Apply by messaging a personal account. Candidates who know how to avoid scams will leave. You will spend time on everyone else.
SWR recommendations
Post the role with a real description. Listings under a short stub are not indexed
Read the candidate application checklist so your form asks for what you will actually use
Look at a public category such as remote customer support to see the context candidates browse
Checklist
Job title is a recognizable role
Company name is visible
First-month tasks are specific
Remote setup, timezone, and employment type are stated
Pay is a range or honestly marked as shared later in the process
Requirements are split into must-have and nice-to-have
Apply path is a normal form or your own site
You are not asking for payment or a private-chat-only process
Mistakes to avoid
Writing the post for everyone and therefore for no one
Hiding the company until after someone sends a resume
Using "remote" for a job that requires a specific city three days a week
Pasting a generic template that does not mention your product
FAQ
Do we have to publish salary?
Publish it when you can. Candidates use it to decide whether to apply. If you cannot publish it yet, say when you will share the range, and share it before a final interview.
How long should the description be?
Long enough to explain the work, the hours, and how to apply. A few short paragraphs and a list beat a page of culture adjectives. Very short posts with almost no description are a poor experience and are kept out of search indexing on She Works Remotely.
Related SWR tools
Related guides
She Works Remotely
Platform editorial
Written by the people building She Works Remotely. These guides explain remote job search, resumes, and interviews, and how to use SWR’s own tools. We do not invent experts, employers, testimonials, or statistics.