SDET: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

Junior SDET — a rare position (usually the market starts via QA Automation, then career-progression into SDET). The Automation Middle/Senior → SDET Junior jump — mastering Backend-Middle-level programming + test-framework architecture + one observability stack. Senior SDET owns multi-team test framework + perf stack + chaos engineering. Staff SDET — organisation-wide test strategy + tooling decisions. Career flow: QA Automation Senior (2-3 years) → SDET Middle → SDET Senior → either Staff SDET / SDET Architect (deep technical), Engineering Manager (management), or Senior Backend (full switch into product engineering).

Top 5: ci/cd, cloud, java, python, agile. Web frameworks: knowledge of 2+ (Selenium 4, Playwright, Cypress — for choice per task). API testing: RestAssured (Java), Pytest + requests (Python), SuperTest (JS), contract testing via Pact. Mobile: Appium (bonus, not mandatory). Performance testing: one of JMeter (industrial standard), Gatling (DSL-based), k6 (modern JS-based, growing) — must for Senior SDET. Docker mastery + Kubernetes (Selenium Grid in k8s + Kubernetes test infrastructure). Cloud devices: BrowserStack + Sauce Labs + LambdaTest. Reporting: Allure + ReportPortal (advanced). Chaos engineering: Chaos Monkey, LitmusChaos for resilience testing. Observability: Datadog/Grafana/Prometheus integration in test pipelines.

Senior QA Automation — writes tests on existing frameworks. Focus: writing tests + maintaining test suite. Programming level: "confident middle". See QA Automation. SDET (this page) — writes TEST FRAMEWORKS + test infrastructure + perf stack. Focus: building tools that test the system. Programming level: Backend Middle/Senior. Backend Engineer — writes product code. Focus: features + business logic. Programming level: deepest. SDET = "backend engineer for the QA domain". Career switch SDET → Backend is possible in 3-6 months (programming level is the same; need to learn product thinking + domain). Backend → SDET — 1-3 months (programming + backend domain are a sufficient base; just learn QA techniques).

A Senior SDET designs a reusable test framework with the following components: 1) Layered architecture — separation of concerns (Test Cases / Page Objects / Business Layer / Driver Layer). 2) Data-driven testing — parametrised tests with external data sources (CSV/JSON/Excel/DB). 3) Page Object pattern (or Screenplay pattern for a modern stack) — UI abstraction. 4) API client layer — type-safe REST/GraphQL/gRPC clients (OpenAPI codegen, Pydantic for Python). 5) Test data management — fixtures, factories (factory_boy for Python, factory-bot for JS), database seeders. 6) Configuration management — env-based configs (DEV/STAGING/PROD test envs). 7) Reporting integration — Allure/ReportPortal with custom annotations + screenshots + videos. 8) CI integration — parallel execution, test result aggregation, flaky test detection. 9) Observability — metrics for test runs (duration, flakiness, coverage trends), integration with Datadog/Grafana. 10) Contract testing via Pact — verify API contracts between microservices. Architecture-decision docs (ADRs) — a Senior SDET responsibility.

Yes, 32% of SDET jobs are full-remote or hybrid. SDET work is cloud-based (test infra in Docker/Kubernetes, CI in the cloud). Outsourcing shops — almost always remote on US projects. Russian product companies — hybrid or remote after probation. Banks — hybrid/office due to compliance. International tech companies — full-remote. Relocant hubs: Poland (Warsaw/Krakow — SDET-friendly), Germany, Czechia, Serbia, Georgia. English — must for international remote with a premium +25-40% (the SDET community is predominantly English-speaking).

SDET — individual-contributor role with deep programming focus. Writes more code than they manage people. Career growth track: Junior SDET → Senior SDET → Staff SDET / SDET Architect (technical ladder). Test Automation Lead — managerial role. Manages 3-7 QA Automation Engineers + tech decisions for the team, but programs LESS than a Senior SDET. More like "Senior QA Automation + management skills". Career growth: Senior QA Automation → Test Automation Lead → QA Director → Director of Engineering. Pay: Senior SDET ≈ Test Automation Lead in Moscow, but SDET higher in international remote thanks to rare-skill premium. Career strategy: SDET if deep technical drive, Test Automation Lead if people-management interest. Both roles are legitimate Senior+ progression, neither better/worse.

QA Automation Senior experience is assumed (or Backend Middle with QA interest). Roadmap: 1) Deep programming in one language (Python or Java — pick per task) to Backend Middle level. Books: "Clean Code" Martin, "Effective Python" Slatkin or "Effective Java" Bloch. 2) Test framework architecture — study open-source test frameworks (pytest internals, JUnit 5 internals). Spring Test for Java. 3) Design patterns in QA — Page Object + Screenplay + Strategy + Factory. Book "Design Patterns for Test Automation" (section in "Software Test Automation" Fewster/Graham). 4) Multi-framework knowledge: Selenium 4 + Playwright + Cypress — know when to use which. 5) Performance testing: JMeter + Gatling + k6 — master one to advanced. Book "The Art of Application Performance Testing" Molyneaux. 6) Docker mastery + Kubernetes basics for test infra (Selenium Grid in k8s). 8) Contract testing: Pact for microservices API contracts. 9) Observability in tests: Datadog/Grafana/Prometheus integration. 10) Pet project: a full reusable test framework for an open-source app (e.g. SauceDemo) with custom data layer + page objects + API client + parallel execution + Allure + CI/CD. Courses: Otus "SDET", Karpov.Courses "SDET", Test Automation University (EN — free), Ministry of Testing (EN — community + courses). Books: "Software Test Automation" Fewster/Graham (classic), "The Art of Software Testing" Myers. QA Automation Senior → SDET Middle — 6-12 months.

428 active open SDET positions — a premium QA niche. Geography: Russia / Poland / remote. The real market is broader thanks to the huge international remote segment. Time to close a Senior SDET role — 6-10 weeks (longer than QA Automation due to specificity).

A Senior SDET owns the full test-engineering cycle + framework architecture. Programming mastery: Backend Middle/Senior level in one language (Python or Java or JS/TS or Kotlin or Go) — clean code patterns, design patterns, refactoring, code review. Test framework architecture: designing reusable framework (see answer above — 10 components), ADRs writing for framework decisions, multi-team framework adoption strategy. Multi-framework knowledge: Selenium 4 + Playwright + Cypress mastery (when which to use), API testing in multiple languages, mobile testing via Appium. Performance testing mastery: one of JMeter/Gatling/k6 at the level of "design load scenarios + analyse results + integrate in CI". Backend-level understanding of distributed-systems testing (race conditions, eventual consistency, network partitions). Test infrastructure: Selenium Grid in Kubernetes (Spark Operator-like for tests), test envs management (DEV/STAGING/PROD-like), cloud devices (BrowserStack/Sauce Labs/LambdaTest) advanced integration. CI/CD mastery: pipeline-as-code on multiple systems, parallel execution patterns, flaky test detection + auto-retry, test result aggregation. Contract testing: Pact for microservices API contracts (provider/consumer). Chaos engineering basics: Chaos Monkey, LitmusChaos for resilience testing. Observability in tests: Datadog/Grafana/Prometheus integration in test pipelines (metrics for test duration, flakiness, coverage trends). Soft: code review for multiple teams, mentoring SDETs and QA Automation engineers, technical writing (ADRs, framework documentation), communication with Backend/DevOps. English for Senior+ MUST — the SDET community is predominantly English-speaking.