How can you tell if a remote job is actually remote?

Check for a stated time-zone range and an explicit location policy in the posting itself rather than the job board's remote tag. Listings that say "remote" but name a single office city, or that require a set number of in-office days, are hybrid roles. Company career pages are more reliable than aggregators because the aggregator's remote tag is often applied automatically.

Are remote jobs harder to get than on-site jobs?

They attract a larger applicant pool because the candidate's location is not a filter, so the competition per posting is higher. The practical response is to apply earlier rather than to apply more; postings older than about two weeks have usually accumulated enough applicants that a late application is rarely read.

Where are the most reliable places to find remote jobs?

Company career pages hosted on applicant tracking systems such as Greenhouse, Lever, and Ashby are the most reliable, because those listings are published by the employer and removed when the role closes. Aggregators are useful for discovery but their listings go stale.

How to Find Remote Jobs That Actually Exist

Most advice about finding remote work stops at "here is a list of job boards." The harder problem is that a large share of what you find on those boards is not really available: the role is hybrid, the listing is months old, or the same posting has been syndicated across six sites and you apply to it twice.

This is a method for filtering that out.

Go to the source, not the aggregator

There is a meaningful difference between two kinds of listing, and it determines how much you should trust what you are reading.

A posting on a company's own career page is published by the employer through an applicant tracking system — usually Greenhouse, Lever, or Ashby. When the role is filled, it disappears. The description is the one the hiring manager approved.

A posting on an aggregator is a copy. It was correct when it was scraped. It may not have been checked since. Aggregators are genuinely useful for discovery, because you cannot know in advance which 400 companies to check, but treat them as an index rather than a source of truth. When an aggregator turns up something interesting, open the company's own careers page and confirm the role is still listed there before you spend an hour on the application.

Read the location policy, not the remote tag

The word "remote" on a job board is frequently applied by a script, not a person. What matters is what the posting itself says, and there are three things worth finding before you apply.

The first is a time-zone range. A genuinely distributed team will tell you the window they expect overlap in, because they have had to think about it. A posting that says "remote" with no mention of hours has often not thought about it, which usually means the team is in one place and you would be the exception.

The second is whether a city is named. "Remote (San Francisco)" is not a remote job. It is an in-office job that allows some working from home, and the compensation and expectations will reflect that.

The third is the phrase "remote-first" versus "remote-friendly." These are not synonyms. Remote-first means the company's default meeting and documentation culture assumes people are not in a room together. Remote-friendly means they will let you work from home and you will spend two years missing context that gets decided in hallways.

Apply early, not often

The single highest-leverage change most people can make is to shift effort from volume to speed.

Applications submitted in the first few days after a posting goes live are read by a human with an empty queue. Applications submitted three weeks later arrive after the shortlist exists. The content of your application matters less than this timing, which is uncomfortable but worth internalising.

Practically, this means checking for new postings on a schedule rather than doing a large search every few weeks. Ten minutes daily beats three hours on a Sunday, because the three hours on Sunday are spent on roles that were posted on Tuesday.

Decide what you are filtering for before you search

A search for "remote software engineer" returns thousands of results and is therefore useless. The filter has to come from you.

Before searching, write down the three constraints that would actually make you decline an offer. For most people these are some combination of compensation floor, time zone, and domain. Then search against those constraints rather than against the job title. Searching for the specific technology you want to work in, filtered to remote, returns a list short enough to read properly — and reading twenty listings properly is worth more than skimming four hundred.

A workable weekly routine

The method above reduces to a fairly small habit.

Check new listings daily, but briefly. Apply the same day to anything that clears your three constraints. Once a week, open the career pages of the ten companies you would most like to work for and check them directly, because those roles are sometimes filled through internal referral before they are ever syndicated. Keep a list of what you applied to and when, so that you stop re-applying to syndicated duplicates of the same posting.

None of this makes the search pleasant. It does make it shorter.