How Can You Tell If a Quality Assurance Remote Job Listing Is Genuine?

The short version: a genuine QA remote job listing names the actual software or product you'll be testing, describes a real interview process with a technical step, and never asks you to buy equipment before you start. If the pay looks too high for the stated experience level, or the company won't tell you who you'd report to, walk away. I've helped candidates pick through dozens of these listings, and the fake ones almost always fail on the same three or four points.

Start with the job title, not the description

Real QA remote roles have specific, almost boring titles: QA Analyst, QA Engineer, Manual Tester, SDET (Software Development Engineer in Test), or QA Automation Engineer. If a listing says "Quality Assurance Specialist Needed, No Experience Required, £45 an Hour, Work 2 Hours a Day," that is not a QA job. That is a scam wearing a QA costume.

Genuine QA pay in the UK sits between £24,000 and £45,000 a year for manual testers with one to four years' experience, rising to £55,000 to £70,000 for senior automation engineers or SDETs with strong scripting skills in Python, Java, or JavaScript. In the US, entry level manual QA remote roles typically run $45,000 to $60,000, with automation and SDET roles at $85,000 to $120,000. Anything advertising £30 to £50 an hour for zero experience and two hours a day is not quality assurance. It's a task-mill or worse.

Check whether the product is named

Every real QA job I've ever seen names the thing you're testing, even loosely. "You'll be testing our checkout flow." "You'll test our mobile banking app across iOS and Android." "You'll be regression testing our SaaS dashboard before each sprint release." Even a vague industry ("we build logistics software for warehouses") is fine, because that's how real hiring managers write job ads: from the inside, describing an actual problem.

Fake listings describe the role in adjectives, not nouns. "You'll ensure top-tier quality across our innovative digital ecosystem." That sentence could describe anything, which means it describes nothing. I once reviewed a listing for a client who was three interviews deep before realising the company had never once named the product she'd be testing. When she finally asked directly, "what software am I testing," the recruiter said "I'll have to check and get back to you." She never heard from them again. That's the tell: a real hiring manager knows the product by heart because they use it every day.

Look at who's hiring

Search the company name plus "Glassdoor" and plus "Companies House" if it's UK-based, or the state's Secretary of State business search if it's US-based. A company that's been trading two years with 40 employees and a real product page is a different animal to a company that registered three months ago with a one-page website and a stock photo of people laughing at laptops.

I check three things every time, and this takes about ten minutes:

• Does the company have a LinkedIn page with actual employees tagged as working there, not just the recruiter posting the job.
• Does the domain in the email address match the company's real website domain exactly, not a lookalike (qacareers-hiring.com instead of the actual company.com).
• Is there a product, app store listing, or client list you can independently verify existed before this week.

If any of those three come back empty, that's not automatically a scam, some new startups are thin on paper, but it means you dig further before giving out anything personal.

The interview process tells you almost everything

Real QA hiring, even remote, almost always includes a practical step. That might be a take-home test plan for a hypothetical feature, a bug-finding exercise on a demo site, a live screen-share where you're asked to find defects in an app, or a short technical chat about how you'd approach regression testing a login flow. Companies want to see how you think before they hire you to break things on purpose, because that's the entire job.

If the "interview" is a fifteen-minute chat over text message, or a single call that never touches on testing methodology, bug tracking tools (Jira, TestRail, Zephyr), or how you'd write a bug report, that's a strong signal nobody involved does QA work. I've sat in on mock interviews with people who'd been offered a QA role after one WhatsApp conversation. No test case. No sample bug report request. No mention of a single tool. That's not hiring, that's recruitment theatre.

Here's the uncomfortable part nobody likes saying out loud: a lot of legitimate-sounding remote QA listings are posted by real staffing agencies who are themselves fishing, not for scam purposes, but to build a candidate database they can shop around to clients who may or may not have an actual open role yet. You can pass every single check above, get a warm, professional interview, and still end up sitting on a "we'll be in touch" for four months because the role was speculative from the start. That's not a scam. It's just the grim reality of how a chunk of the remote hiring market works, and it's the part most advice columns skip because it doesn't have a tidy villain.

Money should only ever flow one direction

This one is non-negotiable: you should never pay for training, software licences, a "certification," a background check, or equipment before you've been formally hired with a contract. Real companies either provide a laptop, pay a stipend for you to use your own, or simply require you to have a computer that meets a stated spec, which they list plainly (8GB RAM minimum, a specific OS version, a stable connection of at least 25 Mbps).

Watch for listings that mention "a small refundable deposit for your test licence" or "a one-time £150 training fee for our QA certification, refunded from your first paycheck." That refund almost never arrives. This exact scam pattern shows up across remote roles generally, not just QA, and it's worth reading how it plays out in other fields too. If you've looked at remote customer service roles or call centre transitions into remote work, you'll recognise the same upfront-fee trick wearing a different job title.

Where you find the listing matters more than people admit

Job boards are not equally policed. LinkedIn and Indeed have reporting systems and remove obvious fakes reasonably fast, though not instantly. Niche remote-specific boards like We Work Remotely, Remote OK, and FlexJobs vet listings before publishing, which cuts down on volume of scams considerably, though it's worth knowing exactly what you're paying for before you commit to a subscription board, and I've broken that down separately in what you need to know before paying for FlexJobs access.

Facebook groups, random WhatsApp forwards, and unsolicited texts claiming to offer QA work are where the fakes cluster hardest, because there's no gatekeeper and no reputation to lose. If a QA job "opportunity" reaches you through a text message from a number you don't recognise, treat that as a near-automatic red flag regardless of how professional the follow-up email looks.

A real example of the checklist working

A client of mine, a career-changer coming out of a QA bootcamp with no professional experience yet, found two listings the same week. Both said "remote QA tester, entry level." Listing one named the product (a property management SaaS tool), listed the exact tools used (Jira, Selenium for future growth, manual testing for now), stated a salary range of £26,000 to £29,000, and the first interview step was a 45 minute call including a shared screen exercise finding five deliberately planted bugs on a demo page.

Listing two offered £22 an hour, "flexible hours, work whenever," no product named, a Gmail address for HR contact rather than a company domain, and the "interview" was a single text conversation ending with "you're hired, just complete this £80 background check payment to your assigned account manager to receive your equipment."

She applied to both. Listing one led to a real second interview and eventually a job offer at £27,500. Listing two never replied again once she asked, politely, for the company's registered business address.

What genuine listings almost always include

• A named or clearly implied product, not just industry buzzwords.
• A stated or reasonably inferable salary band, not a suspiciously round hourly rate with no experience required.
• Mention of specific tools: Jira, TestRail, Selenium, Cypress, Postman, BrowserStack, Zephyr, qTest.
• A multi-step interview process with at least one practical or technical element.
• A company domain email address matching a real, checkable website.
• Clear reporting structure ("you'll report to the QA Lead" or "you'll join a team of six testers").

None of this guarantees a job offer, and it won't speed up an underlying skills gap if you're brand new to testing. But it will save you the specific waste of weeks spent chasing a listing that was never real in the first place, and it'll sharpen your eye for the same patterns if you're job hunting more broadly across remote hiring listings generally, where the fake-to-real ratio is worse than most people assume.

If you want the full set, start at the Remote Jobs and Work From Home: 47 Guides to Real Jobs, Pay and Spotting Scams.

Frequently asked questions

Can a QA remote job be genuine even if the company is brand new?

Yes. Startups hire remote QA testers before their public profile catches up, so a thin LinkedIn page isn't proof of a scam on its own. Check the founder's own LinkedIn history, look for a registered company number, and ask directly in the interview what product you'd be testing. A real hiring manager answers that question in one sentence without hesitating.

Is it normal for a QA job listing not to state a salary?

It's common but not ideal. Many legitimate listings, especially from UK companies and staffing agencies, leave salary as "competitive" or "DOE" (dependent on experience) rather than stating a figure, which is a separate issue from being a scam. The red flag isn't a missing number, it's an unusually high number attached to zero required experience and no interview process.

What should I do if I've already given personal information to a fake QA listing?

Stop all further contact immediately, freeze or monitor your bank accounts if you shared financial details, and report the listing to the platform it appeared on plus, in the UK, to Action Fraud, or the FTC's reportfraud.ftc.gov in the US. Change any passwords you may have reused, and don't send any further payment even if they claim it's needed to "unlock" a refund.

Do legitimate QA remote jobs ever ask for a paid trial period?

Some do ask for a short, unpaid test task, usually under two hours, such as writing a test plan or finding bugs on a demo page, and that's normal industry practice. What's not normal is being asked to pay the company anything, or being asked to work multiple unpaid days under the label of a "trial," which several labour authorities including the UK's ACAS consider a misuse of unpaid work trials.

Useful references

• the ONS data on homeworking in the UK