The most common reason people apply for an SDET role is that they think the coding bar is lower. Every candidate account we could find says it is not.
Search sdet interview questions and you get Selenium trivia, framework-design essays, and a question about testing an elevator. What you do not get is the two things that decide whether you pass: how hard the coding round actually is, and why one of the biggest employers in the field abolished the job title while another renamed it out of existence — both keeping the work.
This guide covers both, and labels every claim by how well sourced it is.
Do SDET Interview Questions Have a Lower Coding Bar?
No. And this is the single most useful thing to know before you prepare.
Three independent candidate accounts, across two companies, say the coding bar matches the software engineer bar:
- A commenter on an Amazon SDET onsite thread who says they have sat many such loops: “…the bar for coding is same as SDE.”
- A Google test engineer describing their own loop: “Its basically same as sde interview except you will have at least two coding interviews that are different so 4 total coding for IC4 and under.”
- An Amazon SDET-1 report listing two LeetCode mediums and one LeetCode hard in a single round.
We looked specifically for the opposite claim — a candidate saying the coding was easier than a SWE loop. We could not find one. The closest thing to a complaint runs the other way: a Google candidate irritated at being given a hard LeetCode problem for what they considered a testing role.
So if you are preparing sdet interview questions by revising test-case design and framework architecture, you are preparing the round that is additional, not the round that eliminates most people.
Where the “Easier Path” Idea Came From
It is not baseless. It is just about fifteen years out of date, and the history is genuinely interesting.
Microsoft abolished the title in 2014
Microsoft ran a large, formally separate SDET job family for years. It formally retired the role in mid-2014, folding testers into a single Software Engineer track — “combined engineering” — after web teams had already been dropping it team by team. One team lead described it as consolidating the dev and test organisations into one engineering org.
The reversal is the part nobody writes about. Microsoft has posted the title again since: an Azure Storage requisition headed “Software Engineer 2- (SDET)” asked for experience in unit, integration, end-to-end, fault injection, performance, scale and long-haul testing. That listing has since closed, so read it as evidence the title came back — not as an opening you can apply to.
So the title was abolished as a company-wide job family and returned as a team-level specialisation. Those are different things, and it matters for how you read a Microsoft job ad.
Google renamed the role in 2016
Google’s own testing blog documents this directly. In March 2016 it let its Software Engineers in Test choose a new title, and 91% picked “Software Engineer, Tools & Infrastructure” — SETI. The SET title went away by vote; Google’s separate Test Engineer title stayed.
Candidate reports suggest the absorption continued: engineers in these roles often just write “Software Engineer” on LinkedIn, and ordinary SWEs now rotate through engineering-productivity teams to do the work.
The work never disappeared anywhere. Microsoft’s own SDET requisition is unambiguously a testing requisition. What changed was the label and the org chart — which is exactly why sdet interview questions now carry a SWE-level coding bar rather than a lower one.
What SDET Interview Questions Actually Cover, Round by Round
Round shapes vary by employer more than most guides admit, so the sdet interview questions you face at one company predict the next one poorly. Here is what candidates report, with the caveat that each of these is a small number of accounts.
Amazon — the most consistently described loop: two coding rounds, one design-and-code round, one behavioural round, and one test strategy round. Candidates single out Leadership Principles as heavily weighted and easy to underestimate. Reported coding topics skew to strings, arrays, maths, stacks and maps rather than linked lists.
Google — four coding rounds at IC4 and below, per a self-identified insider, with system design described as “not really a thing” at that level.
Apple — explicitly team-dependent. One candidate: “It’s completely team-dependent. Every team has its own hiring standards, processes, and interview questions.” Some teams reportedly ask exact LeetCode questions; others ask practical problems drawn from the job description, such as parsing a log file to retrieve specific error messages.
A November 2025 Glassdoor report on Apple’s SDET page describes one medium coding question plus thirty QA-fundamentals multiple-choice questions at roughly a minute each.
Two examples of actual sdet interview questions, each resting on a single Glassdoor report we could not re-locate on a stable link: a Sumo Logic candidate got “Container With Most Water” plus test cases for a WhatsApp story and a file upload; an Apple candidate got string compression and decompression plus generics. Treat both as illustrative of the shape rather than as a question bank.
The Round That Is Genuinely Different
A dedicated test-design round is the one thing that reliably separates sdet interview questions from a standard software engineering loop. Multiple candidate accounts, across Amazon, Google and Sumo Logic, describe it as a distinct stage rather than a follow-up inside the coding round.
What it looks like in practice, from reported accounts: given a feature or a system, produce a test strategy. Candidates describe being asked for test cases for an e-commerce recommendation system, for a file upload, for a messaging feature.
This round rewards structure over volume. Interviewers are looking for whether you partition the problem — happy path, boundaries, failure modes, concurrency, data integrity, security — not whether you can list forty cases.
What Every Competing Guide Drills That Nobody Asks
Two things are worth correcting, because they consume most of the preparation time these guides recommend.
The tool trivia gap
Job adverts for these roles demand Selenium, Playwright, Cypress, RestAssured. Prep guides therefore drill tool-specific trivia. But across the candidate reports we gathered, tool-specific gating almost never appeared. The one instance we found was an older report from India involving a Selenium task requiring a JavaScript executor — a single account, and not a recent one.
The reported loops are coding, test strategy, and behavioural. The requisition and the interview are testing different things, and most guides to sdet interview questions have not noticed the gap.
The elevator question is thirteen years old
“How would you test an elevator?” appears on nearly every page ranking for this term, presented as a current SDET question.
The most-cited Glassdoor entry for it carries answers dated 2013 and lists the role as Software Development Engineer — a developer role, not SDET. A second Microsoft entry for the same question is filed under Software Development Engineer In Test (SDET) I, with one answer dated July 2015.
So it was genuinely asked in SDET loops at some point. But every retrievable report of it is now a decade old, and it is presented across these pages as current. It is a fine thinking exercise. It is not evidence of what anyone asks in 2026.
Two Things We Could Not Establish
Both matter, and both are being asserted confidently elsewhere.
Whether the role is growing or shrinking. The sources contradict each other. A March 2026 jobs report from TestDino states that “the SDET title is growing fastest” — but TestDino sells a Playwright reporting platform, so it has a commercial interest in that answer.
ITJobsWatch, measuring UK postings in the six months to 21 August 2026, shows the median SDET salary at £55,000, down 18.5% year on year, with the title falling 75 places in its rankings. Those figures are as at 21 August 2026; ITJobsWatch recomputes daily.
Both can be partly true — more postings at lower pay. But the UK sample is small and unstable enough (129 postings in 2024, 31 in 2025, 74 in 2026) that we would not trend it confidently.
Whether AI is showing up in these interviews. Prep content asserts heavily that AI test generation is now examined. We searched specifically for candidate accounts of it. We found zero. Every result was prep-blog or vendor material.
One job advert lists “AI-enabled testing” as a desired skill, which is evidence about job adverts, not interviews. If someone tells you AI questions are standard in sdet interview questions today, ask them for a candidate report.
Preparing for SDET Interview Questions, Weighted by What Eliminates People
Allocate time across sdet interview questions in proportion to the evidence, not to what the guides emphasise.
Most of it goes to data structures and algorithms. Same bar as SWE, multiple rounds, and it is where candidates report being cut. Strings, arrays, hash maps and stacks come up more than exotic structures.
Then test strategy, practised out loud. Take a feature you use daily and talk through a structured strategy in ten minutes. The skill being assessed is partitioning, not recall.
Then behavioural, especially at Amazon, where Leadership Principles carry real weight and candidates repeatedly report underestimating them.
Tool syntax comes last. Know your framework well enough to discuss trade-offs. Memorising Selenium method signatures is preparation for a round that, on the available evidence, is rarely run.
And ask the recruiter what the loop contains. Apple’s own candidates say it is entirely team-dependent. That single question resolves more than any question list.
Frequently Asked Questions
Is SDET an easier route into big tech than SWE?
Not on the coding bar. Amazon and Google candidates both describe it as equivalent to the software engineer bar, and no account we found reported it being lower. The loop is different, not easier.
What do sdet interview questions cover that a SWE loop does not?
One extra stage: a dedicated test-design or test-strategy round, run separately from the coding rounds. Everything else overlaps heavily.
Do I need LeetCode for an SDET interview?
Yes. LeetCode-style problems appear in reported loops at Amazon, Google, Apple and Sumo Logic. Medium is the common level, with hards reported.
Is SDET the same as QA engineer or test engineer?
Often, yes. Practitioners describe the titles as used interchangeably between employers — the heart of the role tends not to change even when the label does. Read the requisition rather than the title.
Does the loop include system design?
It depends on the employer, and reports conflict. A Qualtrics candidate describes an explicit test-automation-plus-system-design round; a Google insider says system design is not really a factor at IC4 and below.
How does SDET pay compare with SWE?
Reported as lower than SWE but on the engineering payroll rather than a separate QA band. Individual figures circulating on forums are self-reported and unauditable.
Will these sdet interview questions ask about AI testing tools?
We found no candidate reports of it as of August 2026, despite widespread claims to the contrary. Job adverts mention it more than interviews appear to.
Before You Start Revising
The useful reframe is this. The sdet interview questions ahead of you are not a lighter version of a software engineering loop with testing bolted on.
They are a software engineering loop with an extra round, at the same coding bar, for slightly less money — and at two of the largest employers in the field, under a title that was formally abolished and quietly returned.
Google documented its own half of that story at the time. Its testing blog post announcing the move from QA to engineering productivity is worth ten minutes, and we could not find a competing guide on this topic that cites it.
If you are weighing SDET against the adjacent role, our guide to qa engineer interview questions covers what that title is worth and whether coding is required. And for how other job titles mislead in the same way, see systems engineer interview questions, where one title covers six unrelated jobs. For the wider map of how loops differ by job, start from interview questions by role.
