Your remote job posting is lying to candidates

Five lines that cost you good hires before they apply.

If you’re hiring remotely and your job post still has these lines in it, you’re filtering out great candidates before they even apply. Not on purpose. Just by copying what everyone else does.

First one: “Must be available during HQ business hours.”

You’ve hired someone to work nights. That’s it. That’s what you’re saying. If your HQ is in San Francisco and your hire is in Warsaw, you’re asking them to start their day at 5pm. That’s not a timezone overlap. That’s a night shift. Call it what it is or fix it before you post.

Next: “Competitive salary.”

This phrase is useless everywhere. For international hires it’s actually harmful. A competitive salary in Lagos and a competitive salary in Zurich are not the same number. Not even close. When you leave the number out, international candidates either assume the worst and don’t apply, or they apply, get to the offer stage, and everyone wastes weeks. Put a range. It’s not that complicated.

“We’re like a family here.”

I know this one feels warm. It’s meant to signal culture. But what it actually signals to experienced remote workers is this: this company runs on vibes and proximity, not documentation. Remote teams run on written processes, async communication, and clear expectations. Family culture usually means the opposite of that. It means hallway conversations, gut decisions, and you needing to be physically present to actually matter.

Then there’s “occasional travel required.”

Fine. Travel happens. But occasional means nothing. Is it once a year for a team offsite? Is it quarterly? Is it every time there’s a client meeting? I’ve seen people take remote jobs, relocate their lives, and then discover occasional meant six weeks a year in a country they didn’t plan on visiting. Define it or don’t include it.

The fifth one is the one that annoys me most: “Must be legally eligible to work in [country].”

This line makes sense if you’re hiring for an in-office role. It makes zero sense on a fully remote job post.

Think about what work authorization requirements actually exist for - physical employment relationships. If you’re in the US and you hire someone to sit in your office, yes, they need to be authorized to work in the US. That’s how it works.

But if the job is fully remote and you’re open to hiring internationally, this requirement is self-imposed and optional. An Employer of Record handles exactly this. The EOR becomes the legal employer in the candidate’s country. You manage the work. They handle compliance, payroll, and local employment law. Your candidate doesn’t need to be eligible to work in your country because they’re not working in your country.

That one line - probably added by legal years ago and never revisited - is quietly eliminating candidates who are perfectly hireable. Strong engineers. Experienced operators. People who would do the job well. Gone before you even see their resume.

The math doesn’t work. You post a remote role. You say you’re open to global applicants. Then you require work authorization for a country the person will never physically work in. You’ve contradicted yourself and most candidates won’t bother to ask why.

The pattern I keep noticing is that remote job posts are written by people who’ve never worked remotely, based on templates written for office jobs, reviewed by legal teams focused on domestic hiring. Nobody stops to ask whether the requirements still make sense for the role.

Some of these five things are just sloppy writing. A couple of them are genuinely losing you candidates. The last one is doing both.