Most people looking for remote work start in the same place: they open a big job board, type "remote" into the search bar, and start applying to whatever comes up. This is the slowest possible way to find a job, and it's worth understanding why before you spend another weekend doing it.

A listing on a major board is visible to everyone at once. By the time you see it, so have several thousand other people, and the algorithm has already started throwing out resumes before a human reads them. You're not competing with the ten best-qualified people. You're competing with everyone who has a pulse and a LinkedIn account, and the filtering step that decides who gets seen has nothing to do with whether you'd be good at the job.

Where the real openings are

The roles that are easiest to get are the ones that never make it to a big board at all. Here's where they actually live:

  • Company career pages, checked directly. A role posted only on a company's own site gets a fraction of the applicants of the same role mirrored onto a major board. Pick fifteen companies you'd genuinely want to work for and check their careers page every week.
  • Niche and industry-specific boards. A general board has every job in every field. A board built for one industry — design, DevOps, translation, accounting — has a smaller pool of applicants who actually match the roles, which means your odds per application go up.
  • Referrals from people who don't know you well. Close friends rarely have open roles that fit you. Acquaintances — a former coworker, someone from a course you took — are more likely to know about an opening precisely because they move in different circles than you do.
  • Communities built around the work itself. Slack groups, Discord servers, and forums for a specific craft or tool often have a jobs channel that never gets posted anywhere public. These postings skew toward people who already trust the community, which quietly filters out a lot of the competition.

The goal isn't to apply to more jobs. It's to apply to jobs fewer other people can see.

Making the application actually land

Once you've found a listing that hasn't been seen by ten thousand people, the application itself matters more, not less. A few things consistently move the needle:

  • Address the actual problem in the posting. Most job descriptions describe a problem the team is trying to solve, buried somewhere in corporate language. Find it, and open your cover letter or note by naming it in plain words, then say what you'd do about it.
  • Show remote-specific evidence, not just skill. Anyone can claim to be self-directed. What convinces a hiring manager is a concrete example: a project you shipped without daily check-ins, a time zone gap you managed, a habit you have for staying visible on a team you rarely see in person.
  • Keep the resume format simple. Heavy formatting, tables, and graphics often break when a company's applicant tracking system parses your resume, which means a human never sees the version you designed. Plain text structure, clearly labeled sections, and real numbers beat visual polish almost every time.

What to do while you wait

A remote job search moves slower than an in-office one because there's no hallway conversation to speed things along — everything happens over email and async messages, which means more silence and more waiting. Two things help while you wait: keep a simple spreadsheet of every application with the date and next step, so you're not relying on memory to know who to follow up with, and follow up once, about a week after a typical response window closes, with something short and specific rather than a generic check-in.

None of this makes the search fast. It makes it more likely that the applications you do send are the ones that get read.