The 2026 SDET Interview Master Guide: 12 Domains, Real-World Scenarios, and What Interviewers Actually Test Now

The 3 AM Interview Prep That Changed Everything

Maya had spent three weeks drilling Selenium XPath patterns. She memorized implicit vs. explicit waits. She could recite POM structure in her sleep. But five minutes into the technical screen, the interviewer asked: “Walk me through how you’d approach testing a self-healing locator system with AI fallback logic.”

She froze. That wasn’t in any of the 2023 SDET guides she’d studied. The conversation pivoted to system design—how many WebDriver instances could scale to 500 parallel tests? Then it shifted to behavioral territory: “A developer just rejected your bug report claiming it’s ‘browser variance.’ How do you escalate?”

Maya had prepped for 2020-era SDET interviews. She wasn’t ready for 2026.

This isn’t a story about one interview gone wrong. Across dozens of companies—from mid-market SaaS to Fortune 500 tech firms—the SDET role has fundamentally transformed. Interviewers aren’t just testing whether you can write a Selenium script anymore. They’re evaluating across 12 distinct domains, many of which didn’t exist in standard SDET prep materials two years ago.

The candidates who get offers? They’ve mapped this terrain. They know what’s being tested in each domain and why. They prepare strategically instead of scrambling through generic tutorials the night before.

Why SDET Interviews Changed: The 2026 Landscape

Five years ago, an SDET interview was predictable. You’d get asked about Selenium, maybe some Java coding questions, possibly a bit about CI/CD pipeline basics. That was it.

But automation testing doesn’t exist in isolation anymore. Modern SDETs don’t just write tests—they architect systems, debug AI-powered testing platforms, make go/no-go release decisions, and collaborate with developers in sprint ceremonies. The role has expanded upward and outward.

Companies realized they need SDETs who understand not just automation but system design, not just Selenium but strategic test prioritization, not just code but organizational dynamics. Interview panels changed. So did the questions.

The 12 Domains: Your Complete Interview Map

Domain 1: Core Software Testing Theory

What it covers: STLC phases, SDLC models (V-Model, Agile, Waterfall), verification vs. validation, test levels (unit, integration, system, UAT), and quality gates.

Sample question: “We’re transitioning from Waterfall to Agile. How does the STLC change? What testing activities happen in a 2-week sprint vs. a 6-month Waterfall cycle?”

What they’re really testing: Can you articulate the trade-offs? Do you understand that Agile testing is continuous and overlapping, not sequential? Mention regression test packs, early testing in design phases, and shift-left principles.

Domain 2: Test Case Design Techniques

What it covers: Boundary value analysis, equivalence partitioning, decision table testing, state transition testing, and error guessing.

Sample question: “You’re testing a login form where the username must be 3-20 characters and alphanumeric-only. Design test cases using boundary value analysis and equivalence partitioning.”

What they’re really testing: Can you identify boundaries (2, 3, 20, 21 characters)? Do you recognize valid vs. invalid partitions? Mentioning SQL injection or script injection attempts shows security awareness.

Domain 3: Selenium Deep Dive

What it covers: XPath (absolute vs. relative), CSS selectors, waits (implicit, explicit, fluent), WebDriver architecture, and action chains.

Sample question: “Write an XPath for a button inside a dynamic table where the row is identified by a user’s email. Why would you avoid absolute XPath?”

// Good: Relative XPath using meaningful attributes
//button[@aria-label="Submit"]
//tr[td[contains(text(), 'john@example.com')]]/td/button[@class='edit']

// Bad: Absolute XPath — brittle, breaks with layout changes
/html/body/div[1]/form/div[5]/button

Domain 4: Playwright-Specific Questions

What it covers: Auto-waiting, browser contexts, network interception, tracing, and API testing capabilities built into Playwright.

Sample question: “Describe Playwright’s auto-waiting mechanism. How does it differ from Selenium’s explicit waits? When would you use API testing in Playwright vs. browser-based testing?”

// Playwright auto-waits for actionability
await page.click('button[aria-label="Submit"]');
// Waits for: visible, enabled, stable position

// Browser context for test isolation
const context = await browser.newContext();
const page = await context.newPage();
// Separate cookies, storage, network per context

Domain 5: API Testing

What it covers: REST fundamentals, authentication (JWT, OAuth, API keys), request/response validation, contract testing, and tools like RestAssured and Postman.

Sample question: “You need to set up 100 test users for an end-to-end test. Would you do this via UI or API? Write a test that validates a POST request returns 201 with an id field.”

// Java + RestAssured
given()
  .header("Authorization", "Bearer " + token)
  .contentType(ContentType.JSON)
  .body(new User("john", "doe@example.com"))
.when()
  .post("/api/users")
.then()
  .statusCode(201)
  .body("id", notNullValue())
  .body("email", equalTo("doe@example.com"));

Domain 6: Java/Python Essentials

What it covers: OOP (inheritance, polymorphism, encapsulation), collections, exception handling, string manipulation, and functional programming basics.

Sample question: “Write a function that reads a CSV, extracts email addresses, removes duplicates, and returns them sorted alphabetically.”

// Java example
public Set<String> extractEmailsFromCSV(String filePath) throws IOException {
    Set<String> emails = new TreeSet<>(); // Sorted, no duplicates
    try (BufferedReader reader = new BufferedReader(new FileReader(filePath))) {
        String line;
        while ((line = reader.readLine()) != null) {
            String email = line.split(",")[1].trim();
            emails.add(email);
        }
    }
    return emails;
}

Domain 7: SQL & Database Testing

What it covers: SELECT queries, JOINs, subqueries, aggregation, and data validation queries.

Sample question: “Write a query to find all users who made a purchase in the last 30 days but haven’t received their shipping notification.”

SELECT u.user_id, u.email, o.order_id
FROM users u
INNER JOIN orders o ON u.user_id = o.user_id
LEFT JOIN shipments s ON o.order_id = s.order_id
WHERE o.created_at >= DATE_SUB(NOW(), INTERVAL 30 DAY)
  AND s.order_id IS NULL;

Domain 8: Framework Design

What it covers: Page Object Model (POM), BDD with Cucumber, hybrid frameworks, data-driven and keyword-driven frameworks.

Sample question: “Design a test framework for an e-commerce site. Should you use POM, BDD, or hybrid? How would you structure test data?”

What they’re really testing: Can you explain when BDD adds value vs. when it’s overhead? Do you think about base pages, shared utilities, and inheritance hierarchy?

Domain 9: CI/CD Integration

What it covers: Jenkins pipelines, GitHub Actions, test parallelization, result reporting, and artifact management.

Sample question: “Design a CI/CD pipeline that runs 500 Selenium tests. How would you parallelize them? What happens if one test fails?”

Domain 10: Agile/Scrum in QA Context

What it covers: Sprint planning for QA, definition of done, test estimation, defect triage, and release decision-making.

Sample question: “In sprint planning, the product owner says we need to test a complex new feature in 2 days. Your team has bandwidth for 3 days of work. How do you respond?”

Domain 11: AI in Testing (New in 2026)

What it covers: Self-healing locators, AI-generated test cases, visual regression with AI, and understanding when AI helps vs. when it’s hype.

Sample question: “A vendor pitches an AI test generation tool claiming it can write tests 10x faster. Describe how you’d evaluate this claim. What metrics would you track?”

What they’re really testing: Can you think critically about hype? Do you understand that AI test generation is good for baseline coverage but weak on critical paths?

Domain 12: Behavioral/Situational Questions

Sample question: “You find a critical bug two hours before release. The developer says it’s ‘too minor to fix now.’ You disagree strongly. Walk me through your approach.”

What they’re really testing: Do you escalate without ego? Can you present evidence clearly? Can you propose compromises (hotfix post-release, feature flag)? This separates junior from senior SDETs.

A Word on Scope: Not All Companies Test All 12

A seed-stage startup with 15 engineers won’t ask about CI/CD pipeline parallelization. They’ll focus on Domains 3, 5, 6, and 8. A Fortune 500 finance company? They’ll test all 12 domains rigorously.

Strategy: Read the job description carefully. If it mentions “CI/CD pipeline,” prepare Domains 1, 9, and 10. If it says “startup,” lean on Domains 3-6. Then prepare broadly because surprises happen.

Your 4-Week SDET Interview Prep Plan

Week 1 — Foundations: Domains 1, 2, 10. Core testing theory, test case design techniques, Agile/Scrum context. Write summaries, design test cases for 3 real-world examples, and prepare sprint planning answers.

Week 2 — Technical Core: Domains 3, 4, 5, 6. Selenium deep dive (write 10 robust XPath selectors), Playwright basics (3 tests with auto-wait), API testing (5 RestAssured tests), and Java/Python coding (5 medium-difficulty problems).

Week 3 — Infrastructure & Design: Domains 7, 8, 9. SQL queries (10 with increasing complexity), framework design (sketch a POM framework for e-commerce), and CI/CD pipeline design (build or study a Jenkins/GitHub Actions pipeline).

Week 4 — Modern Skills & Mocks: Domains 11, 12. AI in testing (read 3 articles, write critical analysis), behavioral prep (8 STAR-formatted answers), and 2 full mock interviews (60-90 minutes each).

Frequently Asked Questions

Should I memorize framework-specific syntax or focus on concepts?

Focus on concepts. Interviewers care that you understand why we use Page Objects, not that you can write POM boilerplate from memory. Learn the “why” deeply; syntax is secondary.

Do I need to know both Selenium and Playwright?

Yes. Selenium dominates the market, but Playwright is growing fast. You don’t need equal depth in both, but know their strengths, weaknesses, and when to use each.

What if I get a question I don’t know the answer to?

Say so, then think aloud. “I haven’t worked with contract testing before, but I’d approach it like this…” This shows problem-solving and intellectual honesty. Bluffing is transparent and disqualifying.

How long does serious SDET interview prep take?

Four weeks of focused preparation (1-2 hours daily) covers all 12 domains. Most candidates fail because they study for 2 days. The 4-week plan is designed for working professionals who can dedicate evenings and weekends.

The Bottom Line

SDET interviews in 2026 are deep and broad. But they’re also predictable — if you know what to expect. You now have the 12-domain map, sample questions, and a 4-week plan.

Preparation is the differentiator. The candidate who maps 12 domains and does mock interviews walks in confident. The candidate who skims articles the night before fumbles on live coding.

Execute this plan. Code deliberately. Do mock interviews until you’re bored with your own answers. Offers follow preparation, not luck.

References

• Selenium Official Documentation — WebDriver API reference and best practices
• Playwright Documentation — Auto-waiting, browser contexts, and API testing guides
• RestAssured GitHub Wiki — Java REST API testing with examples
• ISTQB CTFL — Official testing theory certification materials
• Cucumber Official Documentation — BDD framework guide
• Mode Analytics SQL Tutorial — Interactive SQL practice
• Jenkins Pipeline Syntax — CI/CD pipeline documentation
• Agile Testing Quadrants (Lisa Crispin) — Test types in Agile
• Contract Testing with Pact — API contract-driven testing
• Applitools AI Testing Blog — Self-healing locators and visual AI testing