SDET: market
Data as of November 19, 2026: 426 open SDET jobs, 35% remote among jobs that state a work format; median advertised salary $10,166/mo (from 58 postings that state a salary). Source: Zorky, updated daily.
SDET (Software Development Engineer in Test) — a premium QA role at the intersection of Automation and Backend Engineering. Writes TEST FRAMEWORKS (not just tests), test infrastructure, performance test stack. Programming level = Backend Middle/Senior. Role family: SDET (general — test-framework architecture + infrastructure), Senior SDET (multi-team test framework + performance optimisation), Staff SDET/SDET Architect (test strategy for the whole organisation), SDET Tech Lead (team leadership + framework decisions), Performance SDET (load testing + observability + scalability tests). Top stack: ci/cd, cloud, agile, java, aws. Among jobs with a stated work format, 35% are remote.
Data as of:
Key numbers for the SDET market: open jobs, median salary, observed talent pool and remote share.
The SDET market currently has 426 open roles, 368 of them freshly observed. Median salary $10,166/mo.
Among jobs with a stated work format, 35% are remote. SDET work is cloud-based. Outsourcing shops — almost always remote. Russian banks — hybrid/office. International tech companies — full-remote.
⚠ salary known for 58 of 426 jobs; remote share from 354 with a stated format; 368 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many SDET postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 10 |
| 2026-06-08 | 14 |
| 2026-06-15 | 9 |
| 2026-06-22 | 30 |
| 2026-06-29 | 39 |
| 2026-07-06 | 68 |
| 2026-07-13 | 72 |
| 2026-07-20 | 51 |
| 2026-07-27 | 22 |
| 2026-08-03 | 33 |
| 2026-08-10 | 35 |
| 2026-08-17 | 35 |
| 2026-08-24 | 22 |
| 2026-08-31 | 25 |
| 2026-09-07 | 33 |
| 2026-09-14 | 34 |
| 2026-09-21 | 91 |
| 2026-09-28 | 54 |
| 2026-10-05 | 63 |
| 2026-10-12 | 175 |
| 2026-10-19 | 95 |
| 2026-10-26 | 77 |
| 2026-11-02 | 109 |
| 2026-11-09 | 87 |
Active sources per week
Sources over the period: 122. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 7 |
| 2026-06-08 | 8 |
| 2026-06-15 | 4 |
| 2026-06-22 | 14 |
| 2026-06-29 | 19 |
| 2026-07-06 | 15 |
| 2026-07-13 | 23 |
| 2026-07-20 | 27 |
| 2026-07-27 | 13 |
| 2026-08-03 | 21 |
| 2026-08-10 | 14 |
| 2026-08-17 | 22 |
| 2026-08-24 | 13 |
| 2026-08-31 | 16 |
| 2026-09-07 | 15 |
| 2026-09-14 | 15 |
| 2026-09-21 | 26 |
| 2026-09-28 | 22 |
| 2026-10-05 | 23 |
| 2026-10-12 | 29 |
| 2026-10-19 | 37 |
| 2026-10-26 | 28 |
| 2026-11-02 | 30 |
| 2026-11-09 | 29 |
New sources connected: Jun 22 +10 · Jun 29 +12 · Jul 13 +11 · Jul 20 +13 · all weeks (22) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +5 | 14 |
| Jun 15 | +1 | 9 |
| Jun 22 | +10 | 30 |
| Jun 29 | +12 | 39 |
| Jul 6 | +8 | 68 |
| Jul 13 | +11 | 72 |
| Jul 20 | +13 | 51 |
| Jul 27 | +1 | 22 |
| Aug 3 | +8 | 33 |
| Aug 10 | +3 | 35 |
| Aug 17 | +2 | 35 |
| Aug 31 | +2 | 25 |
| Sep 7 | +2 | 33 |
| Sep 14 | +2 | 34 |
| Sep 21 | +6 | 91 |
| Sep 28 | +7 | 54 |
| Oct 5 | +1 | 63 |
| Oct 12 | +6 | 175 |
| Oct 19 | +7 | 95 |
| Oct 26 | +4 | 77 |
| Nov 2 | +2 | 109 |
| Nov 9 | +2 | 87 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 10 | 7 |
| 2026-06-08 | 14 | 8 |
| 2026-06-15 | 9 | 4 |
| 2026-06-22 | 30 | 14 |
| 2026-06-29 | 39 | 19 |
| 2026-07-06 | 68 | 15 |
| 2026-07-13 | 72 | 23 |
| 2026-07-20 | 51 | 27 |
| 2026-07-27 | 22 | 13 |
| 2026-08-03 | 33 | 21 |
| 2026-08-10 | 35 | 14 |
| 2026-08-17 | 35 | 22 |
| 2026-08-24 | 22 | 13 |
| 2026-08-31 | 25 | 16 |
| 2026-09-07 | 33 | 15 |
| 2026-09-14 | 34 | 15 |
| 2026-09-21 | 91 | 26 |
| 2026-09-28 | 54 | 22 |
| 2026-10-05 | 63 | 23 |
| 2026-10-12 | 175 | 29 |
| 2026-10-19 | 95 | 37 |
| 2026-10-26 | 77 | 28 |
| 2026-11-02 | 109 | 30 |
| 2026-11-09 | 87 | 29 |
Salaries over time
Median SDET salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-10-12 | 9,270 | 12 |
| 2026-10-19 | 7,500 | 22 |
| 2026-10-26 | 11,041 | 18 |
| 2026-11-02 | 10,373 | 14 |
| 2026-11-09 | 10,125 | 16 |
The series starts on Oct 12: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | — |
| 2026-10-05 | — |
| 2026-10-12 | 9,270 |
| 2026-10-19 | 7,500 |
| 2026-10-26 | 11,041 |
| 2026-11-02 | 10,373 |
| 2026-11-09 | 10,125 |
Remote work over time
Share of SDET postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-08 | 38.5 |
| 2026-06-15 | — |
| 2026-06-22 | 30.8 |
| 2026-06-29 | 31.2 |
| 2026-07-06 | 51.1 |
| 2026-07-13 | 50 |
| 2026-07-20 | 54.5 |
| 2026-07-27 | 75 |
| 2026-08-03 | 52 |
| 2026-08-10 | 32.3 |
| 2026-08-17 | 41.4 |
| 2026-08-24 | 65 |
| 2026-08-31 | 40.9 |
| 2026-09-07 | 26.7 |
| 2026-09-14 | 32.3 |
| 2026-09-21 | 31.1 |
| 2026-09-28 | 48.9 |
| 2026-10-05 | 62.3 |
| 2026-10-12 | 32.1 |
| 2026-10-19 | 39 |
| 2026-10-26 | 54.8 |
| 2026-11-02 | 30.4 |
| 2026-11-09 | 34.8 |
The series starts on Jun 8: there is no data before that.
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | 38.5 |
| 2026-06-15 | — |
| 2026-06-22 | 30.8 |
| 2026-06-29 | 31.2 |
| 2026-07-06 | 51.1 |
| 2026-07-13 | 50 |
| 2026-07-20 | 54.5 |
| 2026-07-27 | 75 |
| 2026-08-03 | 52 |
| 2026-08-10 | 32.3 |
| 2026-08-17 | 41.4 |
| 2026-08-24 | 65 |
| 2026-08-31 | 40.9 |
| 2026-09-07 | 26.7 |
| 2026-09-14 | 32.3 |
| 2026-09-21 | 31.1 |
| 2026-09-28 | 48.9 |
| 2026-10-05 | 62.3 |
| 2026-10-12 | 32.1 |
| 2026-10-19 | 39 |
| 2026-10-26 | 54.8 |
| 2026-11-02 | 30.4 |
| 2026-11-09 | 34.8 |
Technologies over time
How the share of SDET postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | Java | Python |
|---|---|---|---|
| 2026-08-17 | 25 | 20.8 | 12.5 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | 34.8 | 39.1 | 17.4 |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 40.4 | 23.1 | 25 |
| 2026-09-28 | 42.1 | 39.5 | 31.6 |
| 2026-10-05 | 43.1 | 31.4 | 33.3 |
| 2026-10-12 | 40.5 | 27.6 | 26.7 |
| 2026-10-19 | 45.9 | 28.4 | 50 |
| 2026-10-26 | 39.3 | 27.9 | 34.4 |
| 2026-11-02 | 47.2 | 41.6 | 40.4 |
| 2026-11-09 | 52.7 | 41.9 | 51.4 |
The series starts on Aug 17: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | Java | AWS | Python | Playwright |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | 25 | 20.8 | 0 | 12.5 | 20.8 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | 34.8 | 39.1 | 13 | 17.4 | 13 |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 40.4 | 23.1 | 11.5 | 25 | 7.7 |
| 2026-09-28 | 42.1 | 39.5 | 10.5 | 31.6 | 15.8 |
| 2026-10-05 | 43.1 | 31.4 | 35.3 | 33.3 | 41.2 |
| 2026-10-12 | 40.5 | 27.6 | 15.5 | 26.7 | 31 |
| 2026-10-19 | 45.9 | 28.4 | 25.7 | 50 | 47.3 |
| 2026-10-26 | 39.3 | 27.9 | 21.3 | 34.4 | 37.7 |
| 2026-11-02 | 47.2 | 41.6 | 29.2 | 40.4 | 29.2 |
| 2026-11-09 | 52.7 | 41.9 | 37.8 | 51.4 | 41.9 |
Countries over time
How the share of SDET postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | India | Poland |
|---|---|---|---|
| 2026-06-22 | 21.4 | 14.3 | 46.4 |
| 2026-06-29 | 17.6 | 23.5 | 11.8 |
| 2026-07-06 | 16.1 | 30.4 | 1.8 |
| 2026-07-13 | 14.3 | 31.7 | 9.5 |
| 2026-07-20 | 31.8 | 9.1 | 11.4 |
| 2026-07-27 | — | — | — |
| 2026-08-03 | 23.1 | 15.4 | 0 |
| 2026-08-10 | 39.1 | 30.4 | 13 |
| 2026-08-17 | 12 | 28 | 8 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | 32.3 | 9.7 | 0 |
| 2026-09-14 | 19.2 | 26.9 | 15.4 |
| 2026-09-21 | 25 | 26.3 | 3.9 |
| 2026-09-28 | 37 | 28.3 | 0 |
| 2026-10-05 | 33.9 | 16.1 | 17.9 |
| 2026-10-12 | 31.4 | 25.6 | 5 |
| 2026-10-19 | 27.6 | 13.2 | 6.6 |
| 2026-10-26 | 32.8 | 31 | 6.9 |
| 2026-11-02 | 25 | 29.5 | 11.4 |
| 2026-11-09 | 25.8 | 25.8 | 6.1 |
The series starts on Jun 22: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | India | Poland | Canada | Russia |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | 21.4 | 14.3 | 46.4 | 3.6 | 0 |
| 2026-06-29 | 17.6 | 23.5 | 11.8 | 0 | 14.7 |
| 2026-07-06 | 16.1 | 30.4 | 1.8 | 0 | 0 |
| 2026-07-13 | 14.3 | 31.7 | 9.5 | 12.7 | 14.3 |
| 2026-07-20 | 31.8 | 9.1 | 11.4 | 2.3 | 27.3 |
| 2026-07-27 | — | — | — | — | — |
| 2026-08-03 | 23.1 | 15.4 | 0 | 3.8 | 34.6 |
| 2026-08-10 | 39.1 | 30.4 | 13 | 8.7 | 0 |
| 2026-08-17 | 12 | 28 | 8 | 12 | 16 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | 32.3 | 9.7 | 0 | 3.2 | 12.9 |
| 2026-09-14 | 19.2 | 26.9 | 15.4 | 11.5 | 0 |
| 2026-09-21 | 25 | 26.3 | 3.9 | 17.1 | 7.9 |
| 2026-09-28 | 37 | 28.3 | 0 | 8.7 | 2.2 |
| 2026-10-05 | 33.9 | 16.1 | 17.9 | 1.8 | 10.7 |
| 2026-10-12 | 31.4 | 25.6 | 5 | 5 | 1.7 |
| 2026-10-19 | 27.6 | 13.2 | 6.6 | 14.5 | 1.3 |
| 2026-10-26 | 32.8 | 31 | 6.9 | 12.1 | 0 |
| 2026-11-02 | 25 | 29.5 | 11.4 | 10.2 | 4.5 |
| 2026-11-09 | 25.8 | 25.8 | 6.1 | 15.2 | 1.5 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just SDET.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open SDET jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 426 |
| Open demand | 426 |
| Observed supply | — not published |
SDET — premium QA niche forming a steady flow. Trend 2026: rising demand for performance SDET thanks to cloud-native systems, contract testing adoption.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in SDET jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 1 |
| $2–3k | 0 |
| $3–4k | 2 |
| $4–5k | 1 |
| $5–6k | 3 |
| $6–7k | 5 |
| $7–8k | 2 |
| $8–9k | 8 |
| $9–10k | 4 |
| $10–12k | 11 |
| $12–15k | 10 |
| $15–20k | 11 |
| $20k+ | 0 |
- usable for the calculation: 58 (13.6%)
- stated but not converted to USD/month: 58 (13.6%)
- not stated: 310 (72.8%)
One in ten postings offers under $5,765, one in ten over $16,918. Half of the postings offer between $8,125 and $13,424. Sample: 58.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 1 |
| $2–3k | 2,000 | 3,000 | 0 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 1 |
| $5–6k | 5,000 | 6,000 | 3 |
| $6–7k | 6,000 | 7,000 | 5 |
| $7–8k | 7,000 | 8,000 | 2 |
| $8–9k | 8,000 | 9,000 | 8 |
| $9–10k | 9,000 | 10,000 | 4 |
| $10–12k | 10,000 | 12,000 | 11 |
| $12–15k | 12,000 | 15,000 | 10 |
| $15–20k | 15,000 | 20,000 | 11 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open SDET jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 102 | 30.1% |
| India | 101 | 29.8% |
| Canada | 37 | 10.9% |
| Poland | 18 | 5.3% |
| United Kingdom | 16 | 4.7% |
| Russia | 7 | 2.1% |
| Mexico | 5 | 1.5% |
| Ireland | 5 | 1.5% |
| Philippines | 4 | 1.2% |
| Vietnam | 3 | 0.9% |
| Other countries | 41 | 12.1% |
The leader by SDET job count is the US (102 positions). Poland — SDET-friendly EU.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 102 |
| IN | 101 |
| CA | 37 |
| PL | 18 |
| GB | 16 |
| RU | 7 |
| MX | 5 |
| IE | 5 |
| PH | 4 |
| VN | 3 |
Which technologies are most often required in the same job as SDET.
Used together with
Share — how many of the 426 jobs in the SDET market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top SDET stack 2026: Backend-level programming language (Python/Java/JS-TS/Kotlin/Go — pick one deeply), web frameworks (Selenium 4 + Playwright + Cypress — know 2+), API testing (RestAssured/Pytest+requests/SuperTest + Pact for contract), performance (JMeter/Gatling/k6 — must for Senior), Docker + Kubernetes (test infra), CI/CD mastery, BrowserStack/Sauce Labs/LambdaTest, Allure/ReportPortal advanced, chaos engineering (Chaos Monkey/LitmusChaos).
Common pairs: Python + Selenium + Pytest, Java + Selenium + JUnit + Allure, TypeScript + Playwright + Jest, Docker + Selenium Grid + Kubernetes, JMeter + Gatling + k6 (performance). Learning roadmap: QA Automation Senior → deep programming → test framework architecture → multi-framework knowledge → performance testing → contract testing → chaos engineering.
Chart data
| Name | Count |
|---|---|
| cloud | 164 |
| java | 123 |
| aws | 99 |
| python | 94 |
| playwright | 86 |
| javascript | 84 |
| jenkins | 77 |
| docker | 73 |
| azure | 63 |
| selenium | 60 |
| c# | 58 |
| cypress | 55 |
How many SDET jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 161 |
| principal | 28 |
| lead | 24 |
| middle | 20 |
| junior | 7 |
Junior SDET — a rarity (typical entry via QA Automation Senior). Career flow: QA Automation Senior (2-3 years) → SDET Middle → Senior → Staff SDET / Engineering Manager / Senior Backend (full switch).
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 161 |
| principal | 28 |
| lead | 24 |
| middle | 20 |
| junior | 7 |
Who hires the most for SDET and how concentrated demand is among the largest companies.
Employers
Demand is spread across 287 employers. The largest accounts for 2.3%, the top ten for 14.0%; the remaining 86.0% is long tail.
| share | value |
|---|---|
| top-1 | 2.3% |
| top-3 | 5.9% |
| top-10 | 14.0% |
| long tail | 86.0% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects SDET jobs from.
Where Zorky sees this market
Observed across 52 sources; the largest accounts for 20.4% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 298 | 0.6995 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 99 | 0.2324 |
| telegram | Telegram | Telegram | 27 | 0.0634 |
| community | сообщества и публичные профили | community & public profiles | 2 | 0.0047 |
The newest SDET jobs from company career sites.
Recent openings
- Senior Software Development Engineer in Test - Akamai Inference Cloud (Remote/Po · PL
- Senior Performance QA Engineer / SDET (PC Live-Service) · RU
- Associate SDET (Software Development Engineer in Test) · US · $8,125
- JAVA SDET Consultant · US
- Senior Java SDET Engineer · US
- Mid Level Software Development Engineer in Test | Middle | IC
- Senior Software Development Engineer in Test - […] Identity Governance · CA · $8,777
- Staff Software Development Engineer in Test · US
Latest open SDET jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
SDET — the highest-paying QA role, approaching Senior Backend thanks to programming + distributed-systems testing expertise. Comparison with automation/manual — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- 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
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: QA / Testing
Related specializations
Inside SDET: SDET (general — test framework architecture + infrastructure), Senior SDET (multi-team framework + performance), Staff SDET / SDET Architect (organisation-wide test strategy), SDET Tech Lead (team leadership + framework decisions), Performance SDET (load testing + observability). Comparison with automation/manual — in the bar below.
Frequently asked questions
The most common questions about SDET: pay, SDET vs Automation vs Backend Engineer, test framework architecture, difference from Test Automation Lead, remote, how to start (6-12 months after Automation Senior), Senior skills. Answers recompute automatically.
What does an SDET Junior, Middle, Senior, or Lead earn?
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).
What stack does an SDET most often need?
Top 5: ci/cd, cloud, agile, java, aws. 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.
SDET vs Senior QA Automation vs Backend Engineer — what's the difference?
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).
What test-framework architectures does an SDET design?
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.
What share of jobs are remote?
Among jobs with a stated work format, 35% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is SDET different from Test Automation Lead?
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.
Where to start in SDET in 2026?
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.
How many open jobs are in this sample?
The published sample contains 426 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior SDET need?
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.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.