Remote QA Engineer Jobs: SDET, Test Automation and Titles to Track
Looking for remote QA engineer jobs means dealing with a lot of titles for closely related work. QA Engineer, SDET, Test Automation Engineer, Quality Engineer and plain Tester can describe very different jobs, and the difference between manual and automated testing often matters more than the title itself. This guide explains what the common titles usually mean, how to read a QA posting, and how to set up a search that catches the variants.
QA titles and what they usually mean
| Title | What it usually means | Check in the posting |
|---|---|---|
| QA Engineer | Anything from manual testing to full automation | The ratio of manual to automated work |
| QA Analyst, Tester, Manual QA | Mostly manual: test cases, exploratory testing, regression | Whether any automation is expected |
| Test Automation / QA Automation Engineer | Writing and maintaining automated test suites | Framework and language |
| SDET (Software Development Engineer in Test) | A developer who builds test tooling and frameworks | How much production-level code you'll write |
| Quality Engineer | Automation plus quality process across a team | Whether you own the test strategy |
| Test Engineer | Often software testing; at hardware companies, physical devices | What is being tested |
None of these are fixed definitions. A "QA Engineer" at one company does exploratory testing in a mobile app; at another, the same title builds a Playwright suite in CI and never runs a test case by hand.
Manual vs automation
This is the question most QA candidates actually care about, so it's worth being direct.
Manual testing is real, skilled work: understanding the product, thinking about edge cases, writing clear bug reports, exploratory testing that finds what scripts miss. Manual QA is also a common entry point into tech, which means many people apply for these roles. Read search filters for junior IT roles if that's where you are.
Automation roles ask you to write code: UI tests in Playwright, Cypress or Selenium; API tests; test data setup; running suites in CI. Many postings titled plain "QA Engineer" ask for at least some automation, so check the requirements before assuming the role is manual.
Some teams have no dedicated QA at all, with developers testing their own code. In those companies, quality work appears under SDET or Software Engineer titles, if at all.
Moving from manual to automation
If you're a manual tester aiming for automation roles, a focused plan helps more than trying everything:
- Pick one language that matches the postings you want: JavaScript or TypeScript for web-heavy companies, Java or Python where the backend uses them.
- Learn one UI framework well, such as Playwright or Cypress, and one way of testing APIs.
- Learn enough Git and CI to run your tests on every push.
- Put a small, tidy test project on GitHub against a public demo app, with a README explaining your choices.
- Rewrite your CV so your manual experience reads as domain knowledge and test design, not as a list of executed test cases.
Our guide on tailoring a CV to a job posting covers step 5 in more detail.
What to check in a QA posting
Before you apply, look for:
- Which layer: UI, API, mobile, performance or data.
- Which language the tests are written in, and whether it matches the product's main language.
- Ownership: do you design the test strategy, or execute cases someone else wrote?
- Team setup: embedded in a product team, or a central QA team serving several?
- Release rhythm: continuous deployment changes what testing looks like compared with scheduled releases.
- Location: as with any remote job, read the location line first. "Remote - US" and time-zone overlap requirements settle a lot. See remote IT jobs open to Europe.
About the numbers
We took a September 2026 snapshot of the boards Hot Jobs checks, but QA wasn't among the roles we published counts for, so we have no figure to share here and won't guess one. What we can say is general: the companies on those boards are mostly software, infrastructure and fintech businesses, so it's reasonable to expect their QA postings to use engineering vocabulary, with words like "automation", "CI" and "quality" more than "test cases". Check each posting rather than relying on that.
Adjacent roles
If QA postings are scarce for you, a few nearby titles use the same skills:
- Technical Support Engineer: reproducing issues, reading logs, writing clear reports. Some people move between support and QA in both directions. See technical support jobs in tech.
- Release or Build Engineer: closer to CI/CD and DevOps.
- Mobile QA: if you've tested apps, mobile-specific QA roles are worth adding.
- Software Engineer: SDETs with strong coding skills sometimes move into general development roles.
How Hot Jobs matches QA titles
Matching is by keywords in the job title. The QA / Test role picks up titles containing QA, Quality Assurance, Test Engineer, Test Automation, SDET, Tester or Quality Engineer. Worth knowing:
- Spelled-out "Software Engineer in Test" doesn't contain those words, so it's caught only by Software Engineer (any), which is a much broader role.
- Security titles with "Tester" in them, such as Penetration Tester, can also appear under QA. Skip them if they're not for you.
- Leadership titles, such as QA Manager or Head of QA, are kept out of this role.
- Junior roles and internships are hidden unless you turn them on, which matters if you're looking for a first QA job.
Pick QA / Test, turn on junior roles if you need them, and choose where you can work. Hot Jobs checks 390+ company career pages every 30 minutes, plus two remote boards, and sends new matching postings to Telegram. €3, paid once. Connect the bot