Straight answer: you find remote developer jobs without an agency by going straight to company career pages and remote-only job boards, treating GitHub and open source contributions as your application, and sending short direct emails to engineering managers before a role is even posted. It takes longer to set up than firing your CV at a recruiter, but you keep the whole salary, you control the story, and you stop being one of forty identical candidates a recruiter is shopping around to five clients at once.
Why so many developers default to agencies in the first place
It’s the path of least resistance. You upload a CV to one recruiter, they submit it to eight companies without always telling you which ones, and it feels like progress because your inbox fills up. I’ve watched this play out with several developers I’ve coached through career pivots over the last few years, and the pattern is almost always the same: lots of activity, very little control.
Here’s the bit nobody says out loud. Agencies get paid a percentage of your first year salary, usually somewhere between 15% and 25%, and that fee comes out of what the company was willing to pay for the role, not from thin air. So when a recruiter tells you the budget is £65,000, there’s a decent chance the real budget was £75,000 to £80,000 and the difference is walking out the door to a recruitment firm in London or Manchester that did a keyword search on LinkedIn. That’s not a conspiracy, it’s just how the maths works, and it’s the single biggest reason to go direct when you can.
A real story: how one developer skipped recruiters completely
A developer I mentored, I’ll call him Ben because he’d rather not be named, spent four months applying through recruiters for remote backend roles and got two interviews from roughly 60 applications. He was frustrated, and honestly his CV wasn’t the problem, it was a solid CV. The problem was he was invisible in a pile of other CVs the recruiter was sending to the same five companies.
We changed the approach completely. Over six weeks he sent 47 direct, personalised emails to engineering managers and CTOs at companies that were fully remote or had a clear remote-first policy, all found through their own careers pages rather than a job board. Every email referenced something specific: a blog post the CTO had written, a bug he’d noticed in their public API docs, an open GitHub issue he’d gone in and fixed. Not “I’d love to work at your company,” but “I found this and fixed it, here’s the pull request.”
That got him 3 interviews and 1 offer, a fully remote mid-level role at a 30-person SaaS company paying £58,000, which was £4,000 more than the highest offer any recruiter had put in front of him because there was no fee eating into the budget. Six weeks, 47 emails, one job. That’s the real ratio nobody quotes when they tell you cold outreach “works.”
Step by step: the direct application method
This is the exact sequence I now walk people through, in order.
- Build a list of 30 target companies that already say “remote-first” or “distributed team” on their careers page, not “hybrid” or “remote considered.” That distinction matters more than most people realise.
- Check the company’s own careers page first, always, before any job board. Companies like GitLab, Automattic (the WordPress.com parent), Zapier, and Buffer post every open role on their own site and hire directly, no agency in the loop at any stage.
- Read their public engineering blog or handbook if they have one. GitLab publishes its entire hiring handbook publicly, including how it structures interviews. That’s a gift, use it to prepare answers that match how they evaluate people.
- Find the hiring manager, not HR, on LinkedIn. Look for “Engineering Manager,” “VP Engineering,” or “Head of Product” at that specific company.
- Send a short direct email or LinkedIn message referencing something concrete about their product, code, or a problem you can see and would fix. Three sentences, not three paragraphs.
- Apply through the official careers page too, on the same day, so there’s a paper trail if the manager forwards your message internally.
- Follow up once, after seven working days, not five times over five days. Once is confident. Five times is a red flag.
Where to look, beyond company pages
Some of the best remote-specific boards are run by teams who vet listings and don’t touch agency-submitted roles at all: We Work Remotely, Remote OK, Himalayas, Remotive, and Otta all lean heavily toward direct employer postings. Wellfound, still known to a lot of people by its old name AngelList Talent, is particularly good for startup roles where you can message the founder directly through the platform rather than going through anyone in between.
If you want a broader breakdown of which boards are worth your time versus which ones just recycle agency listings with a fresh coat of paint, I’ve written a full guide on how developers find remote coding jobs worth applying for that goes into the boards in more detail than I’ve got room for here.
One warning worth repeating: not every listing that says “remote” is what you think it is. I’ve seen postings marketed as fully remote that turn out to require two days a month in an office 200 miles away, or “remote” that quietly means remote within one specific country and nowhere else. Before you spend an evening tailoring a CV, it’s worth reading through how to tell remote and work-from-home listings apart so you’re not wasting hours on a role that was never truly remote to begin with.
Using GitHub and open source as your real CV
This is the part agencies can’t do for you, and it’s often the fastest route in if you’re earlier in your career. Contributing to open source projects that a company uses is a working audition. You’re not asking for a chance, you’re showing you can already do the job.
Practically: pick a project the target company depends on (their own open source tools if they have any, or a library listed in their public tech stack on Stack Share or their engineering blog), find an open issue tagged “good first issue” or “help wanted,” fix it, and submit a clean pull request with a clear description. Then, separately, mention that PR in your outreach email. It does the convincing for you.
If you’re newer to this and worried you have nothing to show yet because you’ve never worked remotely, that’s a solvable problem, not a disqualifier. I covered exactly how to build that proof from scratch in how to land a remote frontend developer role without prior remote experience, and the same principles apply whether you’re frontend, backend, or full stack.
The cold email that gets a reply
Structure matters more than length. Here’s roughly what Ben’s best-performing email looked like:
- Line 1: what specific thing you noticed (a bug, a feature gap, a blog post) and a one-line fix or opinion on it.
- Line 2: who you are, in one sentence, tied to that observation, not a generic bio.
- Line 3: a direct ask, “Are you hiring for backend engineers, and if so, is there someone I should speak to?”
No CV attached at this stage. That comes when they reply. Attaching it upfront makes the email feel like a mass application rather than a genuine note to a specific person, and hiring managers can tell the difference in about two seconds.
If drafting these from scratch feels slow, using AI to help you research a company’s recent posts, funding news, or engineering challenges before you write can cut the prep time down considerably, though the email itself should always sound like you, not like a template. I’ve put together a list of prompts worth using for research like this in where to find a solid list of ready-to-use ChatGPT prompts, along with which ones are a waste of time.
What hiring managers want, from the other side of the table
It helps to know what’s happening on the other end of that email, because I write for that audience too. Companies that hire developers directly, without an agency involved, are usually doing it because they’ve been burned by agency fees on a role that ended up being easy to fill anyway, or because they want someone who understands their specific stack rather than someone who ticked the right keywords on a search filter. When I’ve written about how businesses find remote DevOps talent for a growing team, the recurring theme from founders and engineering leads is that they’d rather see three strong direct applicants than thirty agency-submitted ones they have to filter through a stranger.
That’s useful to know because it changes how you should frame your outreach. You’re not asking for a favour, you’re offering to solve a filtering problem they already have.
When an agency still makes sense
I’m not going to pretend agencies are always the wrong move, because that wouldn’t be true. If you’re relocating to a country where you don’t have a network yet, if you’re targeting large enterprise clients that only hire contractors through approved vendor lists, or if you don’t have the time to do direct outreach on top of a full time job, a good specialist tech recruiter can be worth the trade-off. Some, particularly ones who specialise in a narrow niche like Elixir or embedded systems, know their client list well and won’t spray your CV everywhere. The direct route isn’t a moral position, it’s just the one that gives you the most control and the biggest share of your own salary, most of the time.
The one thing that trips people up
The uncomfortable part of this whole approach is patience. Direct outreach has a lower hit rate per hour spent than mass-applying through an agency’s pipeline, at least in the first few weeks. Ben’s 47 emails over 6 weeks felt slow and quiet compared to the flood of recruiter emails he’d been getting before, and there were entire weeks with zero replies. Most people quit right around week three, which is usually the week before the first real reply comes in. If you go direct, budget for that dip and keep sending anyway, because the boards and the direct emails compound, they don’t pay off in a straight line.
Frequently asked questions
Is it harder to find remote developer jobs without using a recruiter?
It takes more upfront effort because you’re doing the matching yourself instead of having a recruiter shortlist roles for you, but it isn’t harder in the sense of being less likely to work. Direct applicants often move faster through the process because there’s no middle person adding delays or filtering your message before it reaches the hiring manager.
What’s the best remote job board that isn’t full of agency listings?
We Work Remotely, Remote OK, Himalayas, and Wellfound consistently lean toward direct employer postings rather than agency-submitted ones. Company career pages are still the most reliable source, since anything posted there was written by the company itself with no third party involved.
How do I contact an engineering manager if I can’t find their email?
LinkedIn is usually the fastest route. Search the company name plus “Engineering Manager” or “Head of Engineering,” send a short connection request with a one-line note, and follow up with your message once they accept. Many companies also list team members on an “about” or “team” page, sometimes with emails in a consistent format you can guess from the CEO’s public email.
Do I need open source experience to find a remote developer job without an agency?
No, but it helps considerably, especially at junior to mid level where you don’t yet have a long track record to point to. A small, relevant contribution to a project the company uses often does more convincing than a paragraph on a CV, because it’s proof rather than a claim.
