Straight answer: remote software engineering roles get posted on a mix of dedicated remote job boards (We Work Remotely, RemoteOK, Wellfound), general boards with a remote filter (LinkedIn, Indeed), and company career pages, but the best ones often get filled through referrals and talent pools before an ad ever goes public. If you’re only checking one channel, you’re seeing a fraction of what’s out there, and you’re competing with everyone else who’s also only checking that one channel.
The job boards built specifically for remote work
Start here, because this is where remote-first companies go when they want remote-first candidates. These aren’t general boards with a “remote” tickbox bolted on. They were built for this from day one.
- We Work Remotely is the oldest and biggest of the dedicated ones. It’s been running since 2011 and gets several million visits a month, mostly from developers, designers, and marketers looking specifically for remote work. Listings cost the employer money to post, which weeds out a chunk of the fake or ghost listings you get on free boards.
- RemoteOK is run by Pieter Levels, one person, and it’s blunt about salary ranges in a way most boards aren’t. You’ll see actual pay bands next to the job title, not “competitive salary.”
- Wellfound (formerly AngelList Talent) skews startup and skews equity-heavy. If you want a Series A or B company that’s fully distributed, this is where a lot of them post first.
- Himalayas and Remotive are smaller but worth checking weekly. They both let you filter by timezone requirement, which matters more than most people realise, because a lot of “remote” roles secretly mean “remote, but you must overlap 9am to 5pm Pacific.”
None of these get anywhere near the traffic of LinkedIn or Indeed, and that’s exactly the point. Fewer eyeballs, less competition, more signal.
General job boards, filtered hard
LinkedIn and Indeed still carry the largest raw volume of remote software engineering postings anywhere, simply because every company from Amazon to a five-person agency posts there by default. LinkedIn’s remote filter is decent but sloppy, plenty of “hybrid, 2 days in Austin” roles slip through tagged as remote because a recruiter ticked the wrong box. I’ve covered this in the piece on jobs remote on Indeed, and the short version is the same problem shows up there: the filter is a suggestion, not a guarantee.
Amazon is a good example of a company that posts remote software engineering roles alongside a lot of listings that only look remote until you read the fine print. I went through this in detail in does Amazon offer remote job opportunities, and the honest pattern is that Amazon’s remote engineering roles exist and pay well, but they’re a small slice of total openings and get thousands of applicants within days.
The practical fix on any general board: sort by date posted, not relevance, and only look at anything under 48 hours old. After that, the applicant pool balloons and your CV is buried on page 40 of an ATS that a human may never scroll to.
Company career pages, gone straight to the source
This is the channel most job seekers skip, and it’s a mistake. Fully remote companies like GitLab, Automattic, Zapier, and Doist run public career pages that list open engineering roles months before those roles ever get reposted to a third-party board, if they get reposted at all. GitLab has published its entire handbook and hiring process publicly for years, which means you can read exactly how their engineering interviews work before you even apply.
If there’s a specific remote company you’d love to work for, bookmark their careers page and check it weekly. Set a phone reminder if you have to. Most people never do this, which is exactly why it works.
A quick story from my own inbox
A developer I mentored last year, I’ll call her Priya, spent three months applying through LinkedIn. Forty-odd applications, two callbacks, zero offers. Then she switched tack: she picked five fully remote companies she’d want to work at, checked their career pages directly, and applied within a day of a role going live on Automattic’s site. She had a first-round interview within a week and an offer six weeks later. Same skills, same CV, completely different result, because she stopped competing on volume boards and started going straight to the source before the crowd arrived.
Developer-specific channels most people forget
Hacker News runs a monthly “Who is Hiring” thread, posted on the first weekday of each month, that regularly pulls in 600 to 900 comments from companies hiring, a large share of them remote. It’s unpolished, it’s just a comment thread, but it’s a channel most recruiters and non-technical job seekers never touch, which means less competition for anyone who does.
Dev.to and Indie Hackers both run job boards aimed at smaller, often bootstrapped, companies. These pay less glamorous salaries sometimes, but they’re a good source for early-stage remote roles with real ownership, not just a seat on a huge team.
Toptal, Turing, and Crossover are worth knowing about too, not as job boards exactly but as staffing platforms that place remote engineers with vetted companies. They take a cut, the pay per hour is usually lower than a direct hire because of that cut, but they can get you into remote work fast if you’re starting from zero remote experience and need a track record.
The uncomfortable part nobody likes admitting
Here’s the bit that gets left out of most “where to find remote jobs” lists: a meaningful share of the best remote engineering roles never get advertised publicly at all, or they get advertised as a formality after someone’s already been informally lined up. Hiring managers at remote-first companies keep a mental shortlist from their network, past contractors, conference contacts, people who commented usefully on their open-source repo. The public job ad often goes out because HR requires it for compliance or pay transparency reasons, not because the hiring manager is starting from a blank slate.
That’s not cynicism, it’s just how hiring works once a company has been remote for a while and has a network to draw on. It means the job board hunt is necessary but not sufficient. If you want the roles that never make it to a board at all, you need to be visible somewhere before you need a job, contributing to open-source projects, answering questions in relevant Slack or Discord communities, writing about your work. I’ve watched this play out with clients who complain the boards are “all fake,” when really the roles they wanted were filled through a network they weren’t part of yet.
Where the paid aggregators fit in
Sites like FlexJobs charge a subscription to access a curated list, and the pitch is that they screen out scams. I wrote a full breakdown of whether that’s worth paying for in FlexJobs remote jobs, what you need to know before you pay for access, and the short version is that the curation has some value if you’re new to remote job hunting and want to skip the obvious scam listings, but almost everything on there also exists somewhere free if you’re willing to look.
A simple weekly routine that covers the ground
Rather than doom-scrolling one board for two hours, spread the search:
- Monday: check the career pages of five to ten specific remote companies you’d want to join
- Tuesday: scan We Work Remotely and RemoteOK, sorted by newest
- Wednesday: check the Hacker News “Who is Hiring” thread if it’s the right week, and Wellfound
- Thursday: LinkedIn and Indeed, filtered to posted-in-last-24-hours, remote only
- Friday: one hour on networking, commenting on a relevant GitHub issue, replying to someone’s post, showing up somewhere a hiring manager might see you before you ever apply anywhere
That last one feels the least productive in the moment and is usually the highest-value hour of the week. It’s also the one everyone skips because it doesn’t feel like “applying.”
What all this means for pay expectations
Where a role gets advertised often correlates with what it pays. Roles sourced through Toptal or Turing tend to land lower per hour because of the platform’s cut. Roles found directly on a company’s own careers page, especially at venture-backed or established remote-first companies, tend to sit closer to market rate because there’s no middleman taking a slice. I’ve broken down actual figures by seniority and region in what remote software developer jobs really pay in 2026, and the range is wide enough, from around $45,000 for a junior role at a smaller distributed startup to $180,000-plus for a senior engineer at a well-funded US company hiring internationally, that the channel you found the job through is a genuine clue to what you should expect before you even open the salary field.
If software engineering specifically isn’t your only interest and you’re weighing up the wider landscape of remote roles, the broader picture of remote work from home jobs and what pays is worth a read too, because the sourcing patterns above, dedicated boards, company pages, and quiet networks, hold true well beyond engineering.
Frequently asked questions
What is the single best site for finding remote software engineering jobs?
There isn’t one single best site. We Work Remotely and RemoteOK carry the highest volume of remote listings, but company career pages and developer-specific channels like Hacker News’s monthly hiring thread often surface roles days or weeks before they show up anywhere else.
Do most remote software engineering roles get posted on LinkedIn?
A large number do, because nearly every company defaults to posting there, but LinkedIn’s remote filter is unreliable and the volume of applicants per posting is much higher than on smaller dedicated remote boards, which makes it a noisy but not useless channel.
Are remote job boards that charge a fee worth it?
Paid boards like FlexJobs can save time by filtering out obvious scams, which matters if you’re new to the remote job search, but most of the roles listed there also appear for free elsewhere if you’re willing to check multiple sources yourself.
Why do some remote roles never appear on any job board?
Because hiring managers at established remote companies often fill roles through their existing network or a shortlist of past contacts before, or instead of, running a public search, and the job ad sometimes only goes live as a formality after someone is already informally in the running.
Sources worth reading
Related reading: Healthcare Innovation: The Critical Role of Software Development and The role of an AI software development company in modernizing legacy systems.
