Where Companies Actually Post Remote Jobs

If you've been job hunting by checking LinkedIn and one or two remote boards, you're probably seeing about 30% of what's out there. That's not an exaggeration. Remote engineering jobs are posted across a fragmented patchwork of platforms, and no single site has a monopoly on listings.

The problem isn't that remote jobs are hard to find. It's that they're spread thin. A startup in Berlin posts on their career page and a European tech Slack group. A Series B company in Austin puts the role on LinkedIn, their site, and We Work Remotely. A distributed-first company might only post on their own careers page and expect word of mouth to do the rest.

If you're only looking in one or two places, you're systematically missing roles that would be a good fit. This article maps out where companies actually post remote engineering roles so you can cover more ground with less guessing.

Company career pages

Every company posts jobs on their own website first. This is always the most up-to-date and accurate source. If a role exists, it's on the career page. If it's been filled, the career page is usually the first place it gets taken down (though not always quickly enough).

The obvious problem: you can't manually check 50 or 100 company career pages every week. Nobody has time for that. Most developers pick 5-10 companies they're interested in and bookmark those pages, which means they miss everything else.

This is the main reason aggregators exist. Rather than checking career pages one by one, a good aggregator crawls thousands of them and presents all the results in one feed. More on that below.

But there's still value in directly following companies you're genuinely interested in. If you have a shortlist of 5-8 companies where you'd actually want to work, check their career pages directly. Some companies post roles on their own site days or even weeks before they appear on external boards.

LinkedIn: lots of listings, lots of noise

LinkedIn is the largest job board in the world and has the most remote developer listings by raw count. It's also one of the noisiest.

Problems developers run into on LinkedIn:

"Remote" doesn't always mean remote. Companies tag jobs as remote when they mean "remote two days a week" or "remote but you need to live within 50 miles of our office." LinkedIn's remote filter has improved, but it still catches hybrid roles regularly.

Recruiter spam is everywhere. A big chunk of "job postings" on LinkedIn are actually recruiter lead-generation campaigns. They post vague roles with wide salary ranges to collect resumes, then reach out months later with something only loosely related.

Stale listings stick around. LinkedIn has a financial incentive to show a large number of listings. Roles that were filled weeks ago often remain visible because nobody bothered to close them.

Duplicates inflate the market. The same role posted by the company, two different recruiters, and a staffing agency. You see it four times and it makes the market look bigger than it is.

Despite all this, LinkedIn is still worth checking because some companies only post there and on their own career page. The 2025 Stack Overflow Developer Survey found that LinkedIn remains the second most common way developers discover new roles, after direct company career pages.

The trick is to use LinkedIn as one source among several, not as your primary platform. And always verify the remote policy by checking the company's actual career page before investing time in an application.

Niche remote job boards

These are platforms built specifically for remote work. They tend to have better curation and stricter listing requirements than general boards.

We Work Remotely is one of the oldest and most established. Companies pay to post, which filters out low-quality listings. The volume skews toward US-friendly time zones, but you'll find roles across most regions.

RemoteOK is popular with startups, has a large volume, and publishes salary data more consistently than most boards.

Himalayas focuses on remote roles at companies with strong remote cultures. They vet companies more carefully, so the volume is lower but the quality tends to be higher.

Arc.dev (formerly Remote.io) specifically targets developers. Listings include technical details about the stack, and many roles come with salary transparency.

Wellfound (formerly AngelList Talent) is worth checking if you're interested in startups. Many early-stage and growth-stage companies post here, and remote roles are common since startups often can't afford office space in expensive markets.

The downside of niche boards is that you need to check each one individually, and there's overlap between them. A company that posts on We Work Remotely might also post on RemoteOK. You end up seeing the same role twice.

Job aggregators

Aggregators solve the fragmentation problem. Instead of manually checking a dozen platforms and career pages, an aggregator crawls all of them and puts the results in one place.

Good aggregation requires two things: broad coverage and deduplication. Coverage means the aggregator needs to crawl not just the major boards but also thousands of individual company career pages, startup platforms, regional boards, and niche communities. Deduplication means you should see each unique role exactly once, even if it was posted on five different platforms.

Remote Genie AI aggregates from over 20,000 sources daily, pulling in around 2,000 active remote positions. You can browse the full market from a single tab instead of maintaining bookmarks for fifteen sites. Combine that with stack and salary filtering and the first page of results is almost entirely relevant.

The difference between a good aggregator and a mediocre one comes down to freshness and deduplication. A mediocre one shows you the same role three times and includes listings from 60 days ago. A good one shows each role once and prioritizes recent postings.

Slack and Discord communities

Some of the best remote engineering roles never hit public job boards. They circulate through private channels first: Slack communities, Discord servers, company newsletters, direct referrals.

This isn't some secret underground market. It's just how smaller companies and well-connected teams prefer to hire. Posting on a job board means getting 200 applications, most of which are irrelevant. Posting in a curated community of Go developers or React engineers means getting 15 applications from people who actually use the stack.

Communities worth joining, depending on your stack:

Language and framework communities are the easiest starting point. Most popular languages have active Slack or Discord groups. The Gophers Slack, Reactiflux Discord, Python Discord, and Rust community Discord all have job channels where companies post regularly.

Regional tech communities help if you care about time zone overlap. If you're in Europe, communities like Berlin Startups or London Tech might surface roles specific to your region. Same goes for communities in Southeast Asia, Latin America, and other regions with growing remote markets.

Industry-specific groups can be surprisingly targeted. Fintech, healthtech, devtools, and other verticals often have their own communities. If you have a preference for the type of company you work at, these are worth the effort.

The work here is upfront: finding and joining the right communities. Once you're in, checking the job channel takes a few minutes per week. And because these listings come with community context (you can often see who posted it and ask questions), the information quality is higher than a blind job board listing.

Company newsletters and "hiring" pages

A growing number of companies publish hiring updates through newsletters, blog posts, or dedicated "we're hiring" pages that go beyond the standard career page. These often include more context about the team, the problems they're solving, and what the actual day-to-day looks like.

Companies with strong engineering brands (Stripe, Vercel, Linear, Fly.io) tend to write detailed role descriptions that read more like team introductions than standard job postings. If you follow their engineering blogs, you'll often hear about new roles before they appear on external boards.

This approach is more passive than active searching, but it's worth the minimal effort. If a company you admire posts a new role in their newsletter, you already have context about the team and the work. That context makes for a better application.

Referrals

According to LinkedIn's Workforce Report, referred candidates are hired at a significantly higher rate than cold applicants. This isn't surprising. A referral from a current employee gives the hiring manager a signal that keyword matching and resume scanning can't provide.

If you have connections at companies you're interested in, reach out directly. Not with "can you refer me?" but with "I noticed your team posted a backend role. I've been working with Go and PostgreSQL for four years. Would it make sense for me to apply?" This gives your contact enough information to make an honest judgment about fit, and it doesn't put them in an awkward position.

Building a referral network isn't something you do during a job search. It's something you maintain over time by contributing to open source, attending meetups, being active in communities, writing about your work. When you eventually need a referral, the connections are already there.

Putting it together: a multi-source setup

Checking every possible source individually is impractical. The goal is to cover the market with minimum daily effort.

Here's what a realistic setup looks like:

Pick one good aggregator as your primary source. Use it for daily search sessions, 20-30 minutes, with filters set for your stack, salary, and seniority. Remote Genie AI works well here because it pulls from 20,000+ sources and lets you filter across all those dimensions at once.

Add 1-2 niche boards as a secondary source. If your stack or industry has a specialized board, check it once or twice a week. This catches anything the aggregator might miss, though the overlap is usually high.

Join 2-3 relevant Slack or Discord communities and check their job channels weekly. Low effort, useful signal.

If you have 5-8 dream companies, check their career pages directly every week or two. Follow their engineering blogs. This is your most targeted channel.

Upload your CV to Remote Genie AI and let the AI matching work in the background. When new roles appear that match your profile, they'll be ranked at the top of your feed. This turns the search from something you do actively into something that also works while you're not looking.

Total weekly time commitment: about 2-3 hours, spread across a few sessions. That covers far more ground than spending 5 hours scrolling through a single board.

Conclusion

The reason most developers feel like their job search is inefficient isn't that they're bad at searching. It's that they're only seeing a fraction of the market. Remote engineering roles are scattered across career pages, general boards, niche platforms, communities, and referral networks. No single source has everything.

The fix: cover more sources with less effort. Use an aggregator as your base, supplement with a niche board and a couple of communities, keep a shortlist of companies you'd want to work at.

If you want the broadest coverage for the least effort, upload your CV on Remote Genie AI and set your filters. You'll get a single feed covering 20,000+ sources, ranked by how well each role matches your profile. That's a better starting point than any single job board.