How to become an SDET and land a remote role
By the QAAnywhere team · Published November 8, 2026
What an SDET does
A software development engineer in test (SDET) is a software engineer whose product is the testing itself. Where a QA analyst mostly designs and runs tests, and a test automation engineer mostly writes automated checks, an SDET builds the systems that make testing possible: frameworks, test data services, tooling, CI pipelines, and the occasional fix in the product code when a test exposes a bug.
In practice the titles overlap, and different companies use them differently. A useful rule of thumb: if the job description talks about code reviews, design documents and framework architecture, it is an SDET role whatever it is called. If it talks about test cases, regression cycles and bug reports, it is closer to QA analysis, even when the title says SDET.
What remote SDET listings ask for
On 8 November 2026 there were 25 remote SDET roles on QAAnywhere, out of 254 QA and testing roles in total (the November hiring report counted 20 of 261). Reading the 15 that include a full description gives a clear picture:
- Experience. Where a number of years was stated, it ranged from 3 to 8, and 5 was the most common. 13 of the 25 roles were explicitly senior and one was principal level. One was titled "SDET I", which at most companies is the entry level; none were labelled junior.
- CI/CD. 12 of the 15 asked for experience running tests in a pipeline (GitHub Actions, GitLab CI, Jenkins).
- API testing. 9 of 15 mentioned APIs. SDETs are expected to test below the UI, not only through it.
- Containers and cloud. About a third mentioned Docker or Kubernetes, and about a third a cloud platform (AWS, Azure or GCP).
- Tools. Playwright was the most named browser tool, followed by Selenium and Cypress; pytest and REST Assured appeared for API work.
- Where you can work from. 19 of the 25 were limited to a single country and the other 6 did not say. None was open worldwide. Before applying, check the location line; the guide on what "remote" means in a QA listing covers how.
- Pay. Only 3 of the 25 stated a salary, all in US dollars, with ranges between about $104,000 and $180,000 a year. That is too few to call a market rate, but it shows SDET roles are paid as engineering roles.
The skills, in the order to learn them
1. One programming language, properly
Pick the language your target companies use: Java, TypeScript or Python cover most listings. "Properly" means you can write a small program from scratch without a tutorial: classes and functions, collections, error handling, reading files and JSON, and writing unit tests for your own code. SDET interviews include real coding rounds.
2. Testing below the UI
UI tests are slow and fragile, so an SDET's first instinct is to push checks down to the API or unit level. Learn HTTP properly (methods, status codes, headers, authentication), and learn to write API tests in code, not only in a GUI client.
A small API test in Python with pytest and requests:
import requests
BASE = "https://api.example.test"
def test_created_order_can_be_fetched(auth_token):
headers = {"Authorization": f"Bearer {auth_token}"}
created = requests.post(f"{BASE}/orders", json={"sku": "BOOK-1", "qty": 2}, headers=headers, timeout=10)
assert created.status_code == 201
order_id = created.json()["id"]
fetched = requests.get(f"{BASE}/orders/{order_id}", headers=headers, timeout=10)
assert fetched.status_code == 200
assert fetched.json()["qty"] == 2
The auth_token fixture lives in a conftest.py and fetches a token once per test session. That small detail, sharing setup through fixtures instead of copying it into every test, is exactly the kind of thing reviewers notice.
3. One browser automation tool
Learn one well rather than three badly. Playwright is the most requested at the moment; the Playwright, Selenium and Cypress comparison covers how they differ. Whatever you choose, practise locating elements by role and label, and never use fixed sleeps.
4. CI, containers and a little infrastructure
Put your test suite in a GitHub repository and make it run on every push with GitHub Actions. Then run the system under test in Docker so the pipeline starts from a clean state each time. You do not need to be a DevOps engineer, but you need to be comfortable reading a pipeline file and a Dockerfile, because a broken test environment is usually the SDET's problem first.
5. Test design and reliability
This is what separates SDETs from people who know a tool. Be able to explain:
- which checks belong at the unit, API and UI levels, and why;
- how you would make a flaky test reliable (find the race, control the test data, isolate state) rather than retrying it;
- how to keep a suite fast as it grows (parallel runs, test data created through APIs, tagging smoke versus full runs).
Three realistic paths in
From manual QA. Your advantage is test design and product knowledge, which many developers lack. Your gap is code. Automate the regression checks you already run by hand, at your current job if possible: real tests against a real product are worth more than any course certificate. Expect it to take a year or more of steady practice before SDET interviews feel comfortable.
From test automation. You already write tests; the step up is engineering around them. Take ownership of the framework, the CI pipeline or the test data setup. Start reviewing developers' pull requests for testability. When your work shows up in other people's code, you are doing SDET work.
From software development. You have the coding skills; you need the testing mindset. Learn test design techniques (boundary values, equivalence classes, state transitions), learn why end-to-end suites become slow and flaky, and be ready to explain why you want a testing-focused role. Interviewers will ask, and "it is easier than development" is the wrong answer.
How remote SDET interviews work
The structure varies, but most remote SDET loops include some of these:
- Recruiter screen. Location, work authorisation, salary range, notice period. Have clear answers ready.
- Coding round. Usually an easy-to-medium problem in your chosen language: strings, arrays, maps. Talk while you code; on a video call, silence reads as being stuck.
- Test design. "How would you test this login page / payment API / file upload?" Structure your answer: clarify requirements, list risks, then pick test levels and cases. Mention negative cases, security and accessibility without being asked.
- Framework or system design. "Design a test framework for a microservices product." Talk about layers (API clients, data builders, test cases), configuration per environment, reporting and how the suite runs in CI.
- Take-home task. Common for remote roles. Treat it like production work: a README explaining how to run it, clear structure, and a note on what you would add with more time.
Showing your work remotely
Remote hiring managers cannot watch you work, so they rely on what you have written. A public repository with a small, well-structured test suite (API and UI tests, a CI workflow, a clear README) does more than a long skills list. On your CV, describe outcomes with numbers you can explain: suite run time reduced, flaky tests removed, bugs caught before release.
The roles below are the newest remote SDET openings on QAAnywhere. Check each one's location line first; most are tied to one country.