- What "QA testing job" means (there are two very different jobs hiding under one title)
- Where the real jobs get posted
- The uncomfortable truth nobody selling QA courses wants you to hear
- The certification that moves the needle
- A real example: how one contract tester turned a two-week gig into a permanent remote role
- What these jobs pay in 2026
- The step-by-step for someone starting from zero
- Why QA is a good backup plan if you're testing other remote job options too
- What to watch for when a "remote QA job" isn't real
- Frequently asked questions
- Sources worth reading
The short version: Real remote QA testing jobs come from three places, dedicated testing platforms like Testlio and Applause, software companies posting on LinkedIn and Indeed directly, and staffing agencies that fill contract QA roles for product launches. Manual testers earn roughly 15 to 25 dollars an hour on contract or 28,000 to 38,000 pounds a year in a UK salaried role, and automation testers earn double that. The trap most people fall into is confusing paid QA engineering work with "get paid to test apps" sites, which pay pennies and lead nowhere.
Related reading: How to Find Legitimate Remote Customer Service Jobs With Major Health .
Related reading: What Remote Roles Suit Software Engineers Who Want to Work From Home.
Related reading: skills needed remote data entry jobs.
What "QA testing job" means (there are two very different jobs hiding under one title)
When people search for remote quality assurance testing jobs, they usually mean one of two completely different things, and mixing them up wastes months.
The first is manual QA testing: clicking through a website or app, filing bug reports, checking that a new feature does what the ticket says. No coding required. This is the entry point, and it is real paid work, but it is also the job most likely to be short-term contract or project-based rather than a permanent salary.
The second is QA automation engineering: writing scripts in Selenium, Cypress, Playwright or Appium that test software automatically, thousands of times, without a human clicking anything. This is a proper engineering job, it pays significantly more, and it is far more stable because companies keep automation suites running for years, not just for one launch.
Know which one you're chasing before you start applying, because the search terms, the sites, and the pay are all different.
Where the real jobs get posted
Forget generic job search alone. Here's where remote QA roles surface:
- Testlio, Applause, and Global App Testing run crowdsourced test cycles for real companies like Spotify, Uber, and various fintech apps. You apply once, get vetted through a paid test, and then get invited to specific paid test cycles that can run from a few hours to a few weeks.
- LinkedIn, filtered by "remote" and job title "QA Engineer" or "QA Tester" is where in-house, salaried roles get posted directly by companies, not agencies. Set a job alert, because these fill fast, often within days.
- Indeed and We Work Remotely carry a mix of contract and permanent QA roles, and Indeed in particular is where smaller software shops post because it's cheaper than LinkedIn recruiter licenses.
- Upwork and Toptal for freelance QA, especially if you already have automation skills; Toptal vets hard but the day rates are noticeably better, often 40 to 70 dollars an hour for vetted testers.
- Specialist staffing agencies like Cognizant, Sogeti, and various UK-based IT recruiters (Nigel Frank, La Fosse) who specifically place contract QA testers for banks, retailers, and insurers running big system upgrades. These roles are almost always remote or hybrid now and pay well because the client is a regulated business that needs proper documentation.
If you're also open to other kinds of remote work while you build QA experience, it's worth comparing what's out there across categories; I've broken down the wider remote hiring market and real openings in more detail, because QA doesn't exist in isolation from the rest of the remote job market and the same companies hiring testers are often hiring for other roles too.
The uncomfortable truth nobody selling QA courses wants you to hear
Here it is: most "get paid to test apps" websites that show up when you Google this exact phrase are not QA jobs. UserTesting pays around 10 dollars for a 20-minute session, and you might get invited to one or two sessions a month if you're lucky. That's not a job, that's pocket money, and treating it as a career path is how people spend six months "testing apps" and end up with nothing that a real employer will look at on a CV.
The people who build a QA career do it by treating early gigs as evidence, not income. A structured, well-written bug report from a Testlio test cycle, one that includes steps to reproduce, expected versus actual result, severity, and a screenshot, is worth more on your CV than three months of random app-testing sessions, because it proves you can do the actual job: communicate a defect clearly enough that a developer can fix it without asking follow-up questions.
The certification that moves the needle
ISTQB Foundation Level is the one credential hiring managers in QA consistently recognise, in the UK, the US, and across Europe. The exam costs roughly 150 to 250 pounds depending on the training provider, it's a 40-question multiple choice test, and you can prepare for it in two to three weeks of evening study using free syllabus PDFs and practice question banks that are widely available online.
It won't get you a senior role on its own, but it does something specific: it gets your CV past the automated filters that many companies now run before a human ever looks at your application. I've seen recruiters admit outright that "ISTQB" as a keyword is one of the first things their applicant tracking system searches for on QA roles, automation or manual.
A real example: how one contract tester turned a two-week gig into a permanent remote role
A few years ago I was consulting for a small e-commerce platform that needed help finding a QA tester fast, ahead of a Black Friday launch. We posted the role on Indeed, expecting to wait weeks. Within four days we had 60 applications, most of them useless, generic CVs with no evidence of testing work at all.
One candidate stood out. She had no formal QA job history, but she'd attached three sample bug reports from a Testlio test cycle she'd done the month before, formatted, screenshots included. We hired her on a two-week contract at 20 pounds an hour to test the checkout flow. She found 14 bugs in the first week, including one that would have broken the discount code system during the actual sale. That contract turned into an ongoing part-time retainer, and eighteen months later she was doing full-time remote QA for two different clients simultaneously.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
The lesson isn't "get lucky." It's that a portfolio of two or three well-documented bug reports, even unpaid or from a practice site, beats a CV full of unrelated customer service jobs every single time in this field.
What these jobs pay in 2026
- Entry-level manual QA tester, remote contract: 15 to 22 dollars an hour in the US, 12 to 16 pounds an hour in the UK.
- Salaried manual QA tester, remote, UK: 26,000 to 34,000 pounds a year.
- QA automation engineer, remote, UK: 42,000 to 65,000 pounds a year depending on framework experience (Selenium and Cypress command the higher end).
- QA automation engineer, remote, US: 75,000 to 105,000 dollars a year.
- Freelance QA via Toptal or direct client relationships: 35 to 70 dollars an hour, though you'll usually need 2 to 3 years of demonstrable experience to get accepted onto Toptal's platform at all.
Pay varies enormously by industry too. Fintech, healthtech, and gaming companies tend to pay noticeably more than general e-commerce, because a bug in a payment flow or a game economy is expensive in a way a typo on a blog post never is.
The step-by-step for someone starting from zero
- Pick your lane. Manual or automation. If you can already code even a little, go straight for automation, the pay ceiling is much higher.
- Study for ISTQB Foundation Level over two to three weeks using free syllabus materials, then sit the exam.
- Do one paid or unpaid test cycle on Testlio or Applause and keep the bug reports you write, cleaned up and anonymised, as your portfolio.
- Build a simple portfolio page (a free Notion page works fine) with three to five sample bug reports, your ISTQB certificate, and any tools you know: Jira, TestRail, Postman, Selenium, whatever's true.
- Set job alerts on LinkedIn for "QA tester remote" and "QA engineer remote," and check Indeed daily for the first month, applications on QA roles get responses fast when they're a fit.
- Apply through staffing agencies too, not just direct, because agencies often have 2 to 3 QA roles open at once across different clients and will slot you in wherever fits.
- Expect your first paid role to be a contract, not permanent. Nearly every QA career I've watched start remotely began with a fixed-term contract that either ended or converted, rarely a permanent offer on day one.
Why QA is a good backup plan if you're testing other remote job options too
If you're job hunting broadly right now rather than committed specifically to QA, it's worth knowing how it stacks up against other remote categories. Data entry roles, which I've covered in detail in this breakdown of what data entry jobs pay, tend to cap out lower than QA and offer far less progression. Customer service and customer care roles, which I've written about separately for general remote customer service positions and specifically customer care remote jobs and their pay, are easier to get into with zero experience but plateau faster than QA does once you add automation skills. QA sits in a useful middle ground: the entry bar is a bit higher than customer service, but the ceiling, especially with automation, is considerably higher too.
And if none of the above quite fits, it's worth stepping back and looking at the wider landscape of work from home roles that pay well before committing months of study to any single path.
What to watch for when a "remote QA job" isn't real
A few red flags that show up constantly in this specific niche:
- Any posting that asks you to pay for "certification" or "training materials" before you can start work. Real employers and platforms never charge you to test their product.
- Postings promising "up to 40 dollars an hour testing apps in your spare time" with no company name attached. Legitimate crowdsourced testing platforms name themselves clearly.
- Interviews that skip any technical or practical exercise entirely. Even manual QA roles usually ask you to find bugs in a sample app or website as part of the process, because that's the actual job.
- Contracts that never specify pay per test cycle upfront. On platforms like Testlio, pay per cycle should be stated before you accept it, not negotiated afterwards.
Related: the fintech page.
Related: science: guidelines and how to pitch.
If you write about online safety, see my list of cybersecurity blogs that accept guest posts.
Frequently asked questions
Do I need a computer science degree to get a remote QA testing job?
No. Manual QA testing roles regularly hire people with no degree at all, provided they can demonstrate attention to detail and write clear bug reports; ISTQB Foundation and a small portfolio matter far more than a degree for entry-level roles.
How long does it take to land a first remote QA job?
Most people who follow a structured path, ISTQB study, one test cycle for portfolio evidence, then focused applications, land a first paid contract within 6 to 10 weeks. It can take longer if you're targeting permanent roles only rather than accepting contract work first.
Is automation testing better than manual testing for remote work?
Automation testing pays roughly double manual testing and tends to offer more stable, longer-term remote roles because automated test suites need ongoing maintenance, whereas manual testing contracts often end when a specific launch is finished.
Are sites like UserTesting a legitimate way to start a QA career?
They're a legitimate way to earn small amounts of extra money, roughly 10 dollars per 20-minute session, but they're not a career path and hiring managers don't count them as QA experience; use them at most for a portfolio sample, not as your main strategy.
