Straight answer: you find remote software engineering jobs as a career switcher by building a small public portfolio of real shipped work, applying directly to remote-first companies under 200 people rather than big-name tech firms, and accepting that your first paid coding job will likely not be remote or well paid. The remote bit usually comes with your second job, not your first.
The bit nobody tells career switchers
I’ve watched three people close to me try this switch in the last four years: a former warehouse shift manager, an ex-primary school teacher, and someone who’d spent a decade in retail management. All three finished a coding bootcamp. All three wanted remote from day one. None of them got it.
The uncomfortable truth is that companies hiring remote engineers are usually hiring people they don’t need to train, watch, or babysit. A brand new career switcher needs feedback, pairing sessions, someone glancing over their shoulder when they’re stuck for three hours on a bug that should take twenty minutes. That’s much easier and cheaper to do in person. So the market quietly sorts itself: junior and career-switch roles skew office or hybrid, and fully remote roles skew toward people with two or more years of shipped, production experience.
Mark, the warehouse manager I mentioned, applied to just over 300 jobs over eleven months. He got 4 interviews. His first job was in-office, three days a week, at a twelve person agency in Leeds, for twenty seven thousand pounds. Eighteen months later, once he had real commits behind him and a reference from that job, he moved to a fully remote role at a SaaS company for forty eight thousand. The pattern held for the other two people I know as well: office or hybrid first, remote second. If you go in expecting remote from job one, you’ll waste months applying to roles you’re structurally unlikely to get, and you’ll burn morale you need for the long haul.
Build proof before you build a CV
Certificates from bootcamps or online courses tell a hiring manager almost nothing now. Everyone doing this switch has one. What separates candidates is evidence that you can build something and get it working end to end.
- Ship one project that solves a real problem for a real person, not a to-do list clone. A booking tool for a friend’s small salon, a stock tracker for a local shop, a Slack bot that pulls data from an API someone uses.
- Deploy it. A live link matters more than a folder of code sitting on your laptop.
- Write a short readme explaining what problem it solves, what you’d do differently now, and what broke along the way. Hiring managers read this more carefully than your CV.
- Contribute to one open source repo, even a small documentation fix or a bug patch. It shows you can work inside someone else’s codebase, which is the actual job.
This takes most people three to six months of consistent evening and weekend work, roughly ten to fifteen hours a week. That’s the real timeline. Anyone promising job-ready in six weeks is selling you a bootcamp, not a career.
Where remote engineering roles get posted
LinkedIn is where everyone looks and where competition is fiercest, often 200 plus applicants within a day on anything decent. Spread your search wider. Job boards built specifically for remote work, like We Work Remotely and Remote OK, tend to list roles from companies that are remote by design rather than companies posting a “remote considered” line as an afterthought. I’ve written a more detailed breakdown of exactly which boards and channels remote engineering roles show up on in this piece on where remote software engineering roles typically get advertised, and it’s worth reading before you set up any job alerts.
Company career pages matter more than people assume. Remote-first companies such as GitLab, Automattic, Zapier, Buffer, and Doist post directly on their own sites and often skip the big boards entirely because they’re flooded with applicants already. Check ten to fifteen of these companies’ careers pages once a week rather than relying on an algorithm to surface them for you.
The Hacker News “Who is hiring” thread, posted on the first working day of each month, is underused by career switchers. It’s unpolished and text-heavy, which puts most people off, but the roles listed there skew toward smaller, engineering-led companies that are open to non-traditional backgrounds.
Big brand names are tempting because they feel safer, but they’re a slower route for a first job. If you’re set on that path anyway, I’ve broken down realistic timelines and expectations in how to find remote jobs at large companies like Amazon without wasting six months, and separately looked honestly at what’s real and what’s oversold about Amazon’s remote roles, because the gap between what’s advertised and what’s available is bigger than people expect.
Apply like a numbers game, because it is one
Career switchers often apply to fifteen or twenty jobs, hear nothing, and conclude the plan doesn’t work. It’s not the plan, it’s the volume. Mark’s 300 applications for 4 interviews is roughly a 1.3 percent conversion rate, which is normal, not a sign he was doing it wrong. Set a weekly target, ten to fifteen tailored applications, not fifty generic ones, and track them in a simple spreadsheet: company, role, date applied, source, response. After six weeks you’ll have real data on which sources are converting for you, and you should put more time into those and drop the ones giving you nothing.
Tailor the CV to the job description every single time, pulling the exact language they use for tools and responsibilities. Applicant tracking systems and busy recruiters both reward this. It adds ten minutes per application and roughly doubles response rates in my experience watching people go through this.
Direct outreach beats the application form
This is the step most people skip because it feels uncomfortable. Find the engineering manager or a developer already working at a company you like on LinkedIn, send a short, specific message: what you’ve built, why their product interests you, and a direct link to your portfolio project. No essay, five sentences maximum. This won’t always get a reply, but when it does, it usually skips the CV screening stage entirely because a human is now vouching for you internally.
This same logic applies to people coming from customer-facing or support backgrounds who assume remote tech roles are out of reach. I’ve seen it work for people moving out of phone-based jobs too, and the mechanics are almost identical to what’s covered in how call centre workers move into fully remote roles, which is worth a read if you’re coming from a support or operations background rather than retail or teaching.
Consider freelance as your side door in
If applications aren’t converting, freelance platforms can get you paid coding experience faster than waiting for a full-time offer, even if the pay is modest at first. Sites like Upwork have largely replaced the old oDesk model, and understanding how that shift happened helps you avoid wasting time on the wrong platforms, which I cover in this piece on what oDesk was, what replaced it, and how to win work now. A handful of small paid projects, even at twenty or thirty pounds an hour to start, gives you client testimonials and real commits you can point to, which does more for your credibility than another certificate.
If you’re weighing freelance work against full-time remote employment generally, it’s worth understanding the actual pay ranges across different remote work types before you commit months to one path, and I’ve laid those out plainly in this breakdown of real remote work options and real pay.
What your first year of pay looks like
Set expectations here or you’ll feel like a failure when the offer lands. In the UK, a first junior developer role for a career switcher typically sits between twenty five and thirty two thousand pounds. In the US, entry-level roles for career changers land somewhere between sixty and seventy five thousand dollars, lower in smaller cities, higher in tech hubs, though those figures compress once you’re two or three years in and negotiating from a position of proven output rather than potential. Remote pay for the same seniority is often slightly lower than office-based roles in major cities, because companies price against a wider talent pool, not against London or San Francisco rent.
Skip the interview prep everyone else is doing
Most career switchers over-prepare for algorithm puzzles and under-prepare for the practical parts of the interview: explaining a decision you made in your portfolio project, walking through a bug you fixed, describing how you’d approach a problem you’ve never seen. Small remote-first companies, the ones hiring career switchers, tend to weight practical, conversational technical rounds far more heavily than whiteboard algorithm tests. Practise explaining your own code out loud, clearly, to someone non-technical. That skill gets underestimated and it’s exactly what remote teams need, since so much of remote engineering work happens through written and spoken explanation rather than in-person demonstration.
Frequently asked questions
How long does it realistically take to switch careers into remote software engineering?
Most people take twelve to eighteen months from starting to learn to landing a first paid coding role, and that first role is usually office-based or hybrid rather than remote. A fully remote role tends to follow twelve to twenty four months after that, once you have shipped, production experience behind you.
Do I need a computer science degree to get a remote software engineering job?
No. Plenty of remote-first companies, including GitLab and Automattic, have publicly hired engineers without a computer science degree, and hiring managers at smaller companies generally care far more about a working portfolio and clear communication than formal qualifications.
Should I apply to big tech companies or small startups first as a career switch?
Small companies under 200 people, especially remote-first ones, are a faster route for a first role because hiring is less standardised and a direct message to an engineering manager can move your application forward. Big tech companies tend to have longer, more rigid pipelines that favour candidates with prior professional coding experience.
Is freelancing a good way to break into remote software engineering?
Yes, as a bridge rather than a destination. Small paid freelance projects give you real client testimonials and commits far faster than waiting months for a full-time offer, and that experience directly strengthens your applications for permanent remote roles afterward.
Sources worth reading
Related reading: AI Meeting Notes: What They Get Right, What They Miss, and When I Switch Them Off and AI Notetakers on Client Calls: What They Record, Who Owns It, and When to Switch Them Off.
For the bigger picture, see my full guide to productivity.
