How to write a remote job post that gets applicants across countries

To write a remote job post that gets applicants across countries, state clearly where you can hire (eligible countries or regions), which hours people must overlap with in UTC, the salary band, how the team works day to day, and every interview step. Candidates abroad decide from those facts before they read anything else.

An office job post can leave much unsaid, because location answers many questions by default. A remote post cannot. Every unanswered question costs you applicants who would have been a fit, and brings in applicants you cannot hire. This guide covers what to include, in what order, and how to keep the post honest and readable.

Why remote posts fail

Most weak remote posts fail in the same few ways:

• "Remote" with no location rules. Candidates in countries you cannot employ in apply, and your team spends time rejecting them.
• No hours. People far outside your timezone apply, then drop out when they learn about daily calls at midnight.
• No salary. Strong candidates in markets with published pay skip the post. In several US states and other jurisdictions, publishing a range is also a legal requirement for postings that cover those locations.
• Office language. Phrases about free lunch, the office dog or "fast-paced in-person culture" tell remote candidates the role is not really remote.
• Vague process. Applicants abroad want to know how many calls they face and whether those calls fit their day.

Fixing these takes a few extra lines, not a longer post.

The structure that works

A clear remote post usually follows this order.

Put the location, hours and salary near the top. Remote candidates scan for them first.

Write a standard job title

Use a title people search for: "Senior Backend Engineer", "Product Designer", "Customer Support Specialist". Creative titles make a post harder to find and harder to compare.

Add the level in the title when you can. If you hire for two levels at once, say so in the post and publish a range that covers both, rather than one vague title.

Keep "remote" out of the title unless your board requires it. On a remote-only board such as RemoteBoard, every role is remote already, and filters handle region and timezone.

State eligible regions precisely

This is the most important line in a remote post. Say exactly where you can employ people.

Good examples:

• "Open to candidates living in the US or Canada."
• "Open to candidates in the EU, the UK and Switzerland."
• "Open worldwide. We hire through an employer of record where we have no entity, or as contractors where that is not available."

Weak examples:

• "Remote."
• "Remote, some restrictions apply."
• "Remote (US preferred)."

If the list of countries is long, give the regions and link to the full list on your careers page. If you hire worldwide as contractors, say so: some candidates prefer employment, and they deserve to know.

On RemoteBoard, the eligible regions you state become the region tags candidates filter by, such as Worldwide, Europe, US or specific countries.

Give the hours in UTC

State the hours you need in UTC, or as an overlap requirement. Examples:

• "We work across UTC-5 to UTC+2. You should be able to work within that range."
• "We need at least four hours of overlap with 14:00 to 22:00 UTC."
• "Fully async. One optional weekly meeting, recorded."

Avoid abbreviations alone. "EST" means different things to different readers, and daylight saving time shifts the offset twice a year. If you use a city or abbreviation, add the UTC equivalent.

If the role includes on-call duty or shifts, say so here, with how they are scheduled across time zones.

Publish the salary band

Give a range, the currency, and whether it is yearly, monthly or hourly. Say whether pay depends on location.

• "120,000 to 150,000 USD per year, base salary, same for all locations."
• "Base salary from 70,000 to 90,000 EUR per year for candidates in the EU. US range published on our careers page."

A published range saves time on both sides. It filters out candidates whose expectations are far apart, and it gives serious candidates a reason to apply. On RemoteBoard, ranges you publish are normalized to USD per year, so your job appears in salary-filtered searches and counts toward the salary data on our /salaries pages. Jobs without a range are still listed, but they are hidden from candidates who tick "salary shown only".

Mention benefits that matter to remote people: equipment, home office budget, coworking allowance, learning budget, paid leave, and how benefits work in countries where you employ through a third party.

Describe the work, not the perks

Explain what the person will do in their first few months and their first year. Name the problems, the systems and the people they will work with. Remote candidates cannot read the room in an office visit, so the post has to do that work.

Keep requirements honest. List what someone truly needs on day one, and put the rest under nice to have. Long lists of must-haves discourage capable people, especially those who tend to apply only when they match every line.

Explain how the team works

A short "how we work" paragraph tells candidates whether they will thrive. Cover:

• Communication. Written first, or mostly calls?
• Meetings. How many recurring ones, and when in UTC?
• Documentation. Where decisions are written down.
• Autonomy. How work is planned and how progress is shared.
• Gatherings. Whether there are team meetups, how often, and whether travel is paid.

Be honest. A team that meets live every morning should say so. The candidates who would hate it will not apply, and the ones who want it will.

List every interview step

Remote candidates often interview while working another job, possibly in a different timezone. Show the whole process:

1. Application review, with a reply within a stated number of days.
2. A short call with the hiring manager.
3. A take-home task or a live exercise, with the expected time.
4. A team interview.
5. A final conversation and offer.

Say whether interviews can be scheduled across time zones, and whether take-home tasks are paid. This one list can noticeably improve how many good candidates finish your process.

Keep the language inclusive and clear

Applicants read your post in many countries, often in their second or third language.

• Use short sentences and plain words.
• Avoid idioms, slang and inside jokes.
• Avoid gendered language and age signals such as "digital native".
• State that you welcome applicants from all backgrounds, and mean it in the process.

Rules for posts on RemoteBoard

Every post published directly on RemoteBoard must describe a real remote role. We do not accept posts that charge candidates any fee, pay-to-apply schemes, multi-level marketing or roles with misleading salary information. Posts that break these rules are removed.

Checklist before you publish

• [ ] Standard job title with level.
• [ ] Eligible countries or regions stated precisely.
• [ ] Hours or overlap stated in UTC, including on-call or shifts.
• [ ] Salary range with currency, period and location policy.
• [ ] Clear description of the work and honest requirements.
• [ ] Short paragraph on how the team works.
• [ ] Full interview process with time expectations.
• [ ] Plain, inclusive language.
• [ ] Apply link tested.

How RemoteBoard plans work

When your post is ready, you can post a remote job on RemoteBoard in two ways: write it in our editor, or paste your applicant tracking system board URL. We support Greenhouse, Lever and Ashby, and once connected, your remote roles sync automatically. New roles appear, closed roles disappear, and edits flow through without anyone copying text.

Employers pay a flat monthly plan, not a fee per post. Each plan has a limit on how many jobs can be active at the same time:

Yearly billing saves 50 percent. Every plan includes ATS sync, job stats and invoices with your company details. Featured slots pin a job at the top of matching pages for 30 days. Before you pay, the one-time ATS preview shows how your jobs will look as RemoteBoard cards.

See the full comparison on the pricing page, or go straight to post a remote job.