Key findings
- 358 public SDET postings in the snapshot; 55% mid-level, 42% senior or lead, 3% junior.
- Most-named tools in SDET postings: Playwright (61%), Docker (37%), REST Assured (37%), Selenium (28%) and Python (24%).
- Where a number of years is stated (251 postings), the median ask is 5 years.
- Postings ask about tools; interviews test whether you can reason with them. Expect to write code in at least one round.
01The five stages
There is no standard SDET interview, but most processes follow the same arc. The table is PassRidge's guidance from how employers describe the role, not a measured average. Format and length differ by company.
| Stage | What it tests | How to prepare |
|---|---|---|
| 1. Recruiter screen | Motivation, level, pay range, location and notice | Know your last two projects in numbers: suite size, run time, flake rate |
| 2. Coding round | A small problem in your main language: strings, arrays, parsing a response, a test helper | Practise in the language on your CV; talk through your approach |
| 3. Test design | Given a feature or API, list risks and cases; choose what to automate | Use a repeatable structure: inputs, states, errors, performance, security |
| 4. Framework or system design | Design a framework for a service or app; CI, parallel runs, reporting, test data | Be ready to draw the architecture and justify every tool choice |
| 5. Team conversation | Collaboration, bug triage, quality ownership, how you handle a flaky test | Prepare two stories where your tests caught or missed something |
02What the postings ask for
Across 358 public SDET postings, these tools appear most often. Share of SDET postings naming the tool, next to the same share for QA automation postings (n=1,023):
| Tool | SDET | QA automation |
|---|---|---|
| Playwright | 61% | 57% |
| Docker | 37% | 7% |
| REST Assured | 37% | 7% |
| Selenium | 28% | 61% |
| Python | 24% | 22% |
| Cypress | 13% | 42% |
| Postman | 13% | 20% |
| Jenkins | 13% | 10% |
Playwright leads the SDET list at 61%. REST Assured appears in 37% of SDET postings, and REST Assured is a Java library, so API-level tests in Java are a regular part of the work. Read the automation tools analysis for the full tool picture.
03A four-week plan
- Week 1: refresh one language to interview level. Solve 15 small problems out loud. Re-read your own suite code.
- Week 2: practise test design on three real products. Write a one-page strategy for an API and a web flow.
- Week 3: build or review a small framework end to end: config, fixtures, parallel runs, CI, a report. Know why each piece exists.
- Week 4: mock interviews. Record yourself. Prepare questions for the team: ownership of quality, flaky-test policy, release cadence.
Use the Interview Vault for questions by role and tool, and the QA Level Test to see where you stand. Compare roles in SDET vs QA automation engineer.
04Common mistakes
Mistakes that cost candidates offers, in PassRidge Research's experience of the process:
- Listing tools without saying what you built with them.
- Writing tests that pass but cannot be read by someone else.
- Talking only about UI tests when the role is mostly API and services.
- No view on flaky tests, test data or runtime. Have one.
- Not asking about pay range, level and expectations until the offer. Ask in stage 1.
05Method and limits
Sample: 3,863 public postings harvested 20 Oct 2026 from employer career pages and public job feeds. Listings are postings, not people or confirmed openings: one role open in several cities counts several times (2,417 distinct titles across 3,863 postings). PassRidge talent-pipeline roles (149) are excluded from every statistic.
The stage table is guidance from PassRidge Research, drawn from how employers describe the role. It is not a statistic. Tool shares use the SDET role group (358 postings).
The method for roles, tools and pay is documented on our salary methodology page. Spot an error? Write to [email protected].
Go deeper
Sources
- PassRidge public listing snapshot, 20 Oct 2026