The short version: remote junior software engineering jobs exist but they are not on the front page of LinkedIn, they are inside small startups, agencies, and dev shops with under 50 people who cannot afford a six month onboarding process, and you find them by building one small proof of work instead of polishing a CV nobody reads. Big remote-first names like GitLab or Automattic almost never hire true juniors remotely. Smaller, less famous companies do, constantly, they just don’t shout about it.
Why this is harder than the career advice videos make it sound
I’ll say the thing most people writing about this topic won’t say plainly: remote-first companies generally prefer not to hire junior engineers at all. Not because they’re snobby, because remote onboarding is expensive in a way office onboarding isn’t. When a new hire sits three desks away, a senior engineer can glance over, catch a wrong assumption in ten seconds, and move on. When that same junior is in Manila and the senior is in Manchester, every one of those small corrections needs a Slack message, a screen share, a delay of hours across time zones. Companies know this costs money. So the job ads that say “remote, entry level” are often either poorly worded (meaning 2-3 years, which in tech is still junior) or they’re from a company small enough that the founder is doing the mentoring themselves.
That’s the uncomfortable bit nobody puts in the headline: you are not competing for the same jobs as someone with five years in. You’re competing for a much smaller, less visible pool, and the strategy has to be different, not just “apply more.”
Where the actual junior remote roles live
Forget the big remote job boards as your primary source. RemoteOK and We Work Remotely are fine for browsing but they’re flooded, a junior-friendly posting gets 300+ applicants in 48 hours because everyone reads the same three articles telling them to apply there. Here’s where I’ve seen real hires happen instead:
- Y Combinator’s Work at a Startup board. Early stage companies here often need someone cheap and hungry more than they need someone experienced, and a good chunk are fully remote by default because they’re two founders and no office.
- Agency and dev shop job pages, not their LinkedIn ads. Places like Toptal’s network, or smaller regional agencies (I know a 14-person Bristol based dev shop that has hired three juniors remotely in the past two years, none of them through a job board, all through a portfolio project sent cold).
- Open source contribution threads. Companies like Sentry and Prisma have hired contributors who fixed real bugs in their public repos before a job even existed. This sounds like advice for people who already code well, and it is, but it’s also the single most reliable way I’ve watched someone with under two years experience skip the CV pile entirely.
- Wellfound (the site that used to be AngelList Talent). Filter by remote and by “0-1 years” experience level, it exists as a filter for a reason.
If you’re coming from a completely different career, the mechanics differ slightly, and I’ve written a full walkthrough on how to find remote software engineering jobs as a career switch that covers the transition specifically, worth reading alongside this if that’s your starting point.
The Priya story
A woman I mentored briefly through a LinkedIn connection, I’ll call her Priya because she asked me not to use her real name, spent four months applying to remote junior developer roles after a coding bootcamp. Two hundred and eleven applications. Three interviews. Zero offers. She was doing everything the guides told her: tailored CV, cover letter, LeetCode practice most evenings.
What changed it wasn’t more applications. It was building one thing. She noticed a 12-person logistics startup in their job ad mention they were struggling with a specific dashboard reporting bug (they’d mentioned it on their engineering blog, not the job post itself). She built a small working fix to a public version of the same open-source library they used, wrote a short Loom video walking through it, and sent it directly to the CTO along with her application. She was hired six days later at 58,000 dollars a year, fully remote, based in Leeds while the company was headquartered in Austin.
The lesson isn’t “everyone should stalk a company’s blog.” It’s that one specific, visible piece of relevant work beats a hundred generic applications, every time, and it costs you a weekend instead of four months.
Step by step: what to do this month
- Pick three company sizes, not company names. Target companies with 10-60 employees. Anything over 200 that’s remote-first (GitLab, Zapier, Buffer, Doist) will want at least 2 years even for “junior” titles. Check their careers page headcount on LinkedIn before applying, it takes thirty seconds and saves you a wasted application.
- Build one small, ugly, functional project that solves a real problem, not a to-do list app. A Chrome extension that scrapes and reformats something tedious. A script that automates a task you personally find annoying. Recruiters have seen five hundred to-do apps this year alone.
- Apply to 15-20 roles a week, not 100. Quality over volume matters more here than almost anywhere else in job hunting. Spend the time you’d waste on application 80 through 100 on a five minute personalised note to the hiring manager instead.
- Use your CV as a filter test, not a masterpiece. Most junior CVs get 6-8 seconds of attention. If yours needs more than that to show relevant skill, it needs cutting, not adding to. If you’re not sure yours passes that test, this guide to resume templates for freshers with no experience has formats that are built around getting past that six second scan rather than looking impressive on paper.
- Track everything in a spreadsheet with three columns: applied, response, reason if rejected. After 30 applications, patterns show up. If you’re getting zero responses, it’s the CV or the targeting. If you’re getting interviews and no offers, it’s the interview itself, and that’s a different problem to fix.
What “junior friendly” means when a listing says it
Job ads lie by omission constantly. “Junior developer, remote” frequently means the company wants someone with 1-2 years commercial experience who they can pay less than a mid-level engineer, not someone straight out of a bootcamp with zero paid experience. I’ve read hundreds of these listings while researching for clients, and the tell is almost always in the required skills section: if it lists four or five specific frameworks plus “experience with CI/CD pipelines,” that’s not an entry level ask no matter what the title says.
The listings that are open to under-a-year experience tend to say things like “we’ll teach you our stack” or list soft requirements (communication, curiosity, ability to work async) above technical ones. That phrasing is a genuine signal, not fluff, because it tells you the company has already decided to invest in training and is filtering for trainability rather than existing skill.
There’s also a whole category of roles that sit next to engineering rather than inside it, QA automation, technical support engineering, developer relations, that hire with far less code experience and let you build the two years you need to move sideways into a straight engineering role later. It’s a slower path but a realistic one, and it’s worth being honest with yourself about whether you’d rather have a remote income now and a pivot in eighteen months, or another six months of unpaid job hunting chasing the title you want first.
The interview stage looks different when you’re junior
With fewer years behind you, interviewers aren’t testing depth, they’re testing whether you can be taught without draining their senior team’s time. That changes what you should prepare. Practice explaining your reasoning out loud while coding, not just getting to the right answer. I’ve watched hiring managers pass on a candidate who got the correct solution silently, and hire the one who talked through a wrong turn and corrected it, because that second person showed exactly what working with them async over Slack would feel like.
For a broader sense of what makes a listing worth your time versus a waste of an evening, this piece on how developers find remote coding jobs worth applying for is worth reading before you burn a week on applications to companies that were never going to call back. And if you specifically want a shortlist of the kind of roles built with juniors in mind rather than generic postings, there’s a dedicated rundown of remote software engineer jobs for juniors covering the titles and company types to search for directly.
What to do if the direct route stalls
Not everyone finds a remote junior role in three months, and that’s not a personal failing, the market is tighter for entry level remote roles now than it was in 2021 when every company was hiring flat out. If you’re at month four or five with nothing, two moves work better than doubling down on the same approach:
- Take a hybrid or onsite junior role for 12-18 months first. Once you have that experience on paper, remote roles open up dramatically because you’re no longer asking a company to take a bet on someone unproven, you’re asking them to let someone proven work from home, a much smaller ask.
- Contract or freelance small paid projects, even at low rates. A few hundred pounds building a simple site for a local business is still commercial experience you can put on a CV, and it’s often faster to get than a full-time offer.
Some people also find their way in through adjacent remote-heavy sectors first. Large companies with big remote operations, Amazon among them, sometimes run structured entry programmes that are worth understanding on their own terms before ruling out, and I’ve broken down how Amazon remote jobs really work and whether they’re worth your time separately since the process there is unlike a typical startup application.
A number worth sitting with
When I asked around three founders I know who’ve hired junior remote engineers in the past year, the average time from first application to offer for the successful candidate was 11 weeks, and the average number of applications they’d personally sent before that offer landed was 34, not 200. The ones who’d sent 200 with no result had almost all been applying to the same tier of well-known, oversubscribed remote-first company, not spreading across smaller ones. Targeting beats volume here, consistently.
Frequently asked questions
Can I get a remote software engineering job with one year of experience?
Yes, but mostly at companies under 60 employees, agencies, and startups rather than well-known remote-first names, and you’ll have far better luck applying with a small relevant project attached than a CV alone.
Do I need a computer science degree for remote junior developer jobs?
No, most small companies hiring remote juniors care far more about a working project and clear communication than a degree, though a small number of larger firms still list it as a preferred qualification.
Which companies hire junior developers remotely?
Small startups from Y Combinator’s Work at a Startup board, regional dev agencies with fewer than 60 staff, and open source adjacent companies like Sentry hire juniors remotely far more often than large remote-first firms such as GitLab or Automattic, which typically ask for 2 plus years even in junior titled roles.
How many job applications does it take to get a remote junior developer role?
Founders who’ve hired for these roles report an average of around 34 targeted applications leading to an offer, compared to over 200 untargeted applications leading to nothing, so focus on fit over volume.
Further reading
More on this here: contribute a guest article on startups.
