SDET AI Interview Questions: Automation and Agents with Answers

SDET interviews test how you build and defend systems. These SDET AI interview questions go beyond “Have you used Copilot?” into design choices, code review, agents and CI. Each answer shows how a strong candidate reasons. Use the project you built in this course as your evidence, and be ready to change its code on the spot.

📖 What You’ll Learn

How SDET interviews assess AI skills
Questions on AI-generated automation
Questions on agents and MCP
How to handle a live coding round

💡 What SDET AI Interview Questions Test

Explain Like I’m 5: Showing How You Fixed the Bike

Imagine: Anyone can say they fixed a bike. An expert explains why the chain slipped and how they know that it is fixed.

What it really means: Interviewers look for reasoning, not tool names.

In testing: Explain why you made a design decision.

Area	They are checking
AI-assisted coding	Do you review what is generated?
Framework design	Can you keep a suite maintainable?
Agents and MCP	Do you understand the risks?
CI and reliability	Can you run this at scale?
Live coding	Can you think without relying on an assistant?

🔍 Questions on AI-Generated Automation

Explain Like I’m 5: Checking the Robot’s Homework

Imagine: The robot finished quickly, but the teacher still checks whether each answer is right.

What it really means: Fast code still needs an expert review.

In testing: Check that assertions test the real behaviour.

What do you check in a Playwright test written by AI?

I check locators against the real page, the meaningfulness of assertions, fixed sleeps, hard-coded data and whether the test fails when the feature breaks. I actually break the feature to confirm this.

How do you stop AI from producing brittle tests?

I give it real page evidence and our conventions, then enforce those rules using lint and validation. I prefer role-based locators and web-first assertions.

How do you use AI to investigate a flaky test?

I give it the trace, logs and error, then ask for hypotheses with evidence. I confirm the cause myself and avoid hiding the problem with retries. The method is in Flaky Test Diagnosis with AI.

AI-generated tests all pass. Are you satisfied?

No. Passing shows only that they ran. I would run mutation-style checks by breaking the behaviour, then review traceability to the requirements.

How would you review a large AI-generated pull request?

I would ask for it to be split. A huge diff cannot be reviewed well, so I would check the tests and risky areas first.

🧩 Questions on Agents and MCP

What is the difference between a workflow and an agent?

In a workflow, code decides the order of steps. In an agent, the model chooses the next step within limits. I use a workflow when the order is known.

How do you test an LLM-based component without paying for a model?

I place the model behind an interface and use a mock with scripted responses. That lets me test good, malformed and hostile outputs repeatably.

What is MCP, and what are its risks?

MCP is a standard way for AI applications to discover and call tools. The risks include poisoned tool descriptions, excessive permissions and changed tools. I use allowlists and pin versions, as covered in MCP Security for Testers.

How do you make self-healing safe?

Only test defects get a patch, the patch must be small, assertions cannot change and a person approves it. Healing an expected result can hide a real bug. See Self-Healing Tests with AI.

How do you prevent an agent from running dangerous commands?

It can only request tools from a fixed list. Commands use fixed arguments with no shell, a time limit and a limited environment.

🛠️ Questions on CI and Reliability

Would you put LLM calls in your merge pipeline?

Not as a blocking check at first. They add cost and variation. I keep mock-based tests in the main pipeline and run model evaluations separately.

How do you measure an AI test generator?

I measure scenario validity, acceptance rate, defects found, review time and cost. A high pass rate alone proves very little.

Be ready to code without AI

Many companies ask for live coding with no assistant. Practise writing a Playwright test and a small TypeScript function by hand.

📌 Handling a Live Coding Round

Explain Like I’m 5: Thinking Out Loud

Imagine: When a teacher can hear your thinking, they can help you and give credit for your method.

What it really means: Explain your reasoning as you work.

In testing: Say what you are checking and why.

Repeat the problem in your own words.
Ask about edge cases.
Start with the simplest working version.
Talk through what you are doing.
Test it and explain what you would add.

🌍 Real-Life Example: The Mutation Moment

A candidate shows an AI-generated test, then breaks the login button on purpose. The test still passes, and the candidate explains why that is a problem and fixes the assertion. That three-minute demonstration says more than any list of tools.

🧪 Try It Yourself

Answer five questions aloud, without notes.
Break a feature and see whether your test notices.
Write a Playwright test without any AI help.
Explain one design decision from your agent.
Run the mock interview prompt below.

📋 Ready-to-Copy Prompt

You are a senior SDET interviewing me for an automation role.

Here is my project's README: [paste with no secrets]

Ask me one technical question at a time about my design decisions, code
quality, agents and CI. Challenge my answers with follow-up questions.

After five questions, tell me which answers sounded memorised and where I
need stronger evidence.

⚠️ Common Mistakes

Treating a passing test as proof of quality
Being unable to code without an assistant
Describing agents with no mention of limits
Giving tool lists instead of decisions
Not knowing your own project’s weak points

🎯 Key Takeaways

Explain why you made each decision.
Prove that tests fail when they should.
Know the risks of agents and MCP.
Practise coding without AI help.

🎤 Interview Questions

1. Design a test strategy for code that is mostly AI-generated.

Model answer: I would raise the bar on review, use contract and behaviour tests, add mutation-style checks and require people to confirm expected results. I would track escaped defects.

2. A model upgrade changed your agent’s behaviour. What do you do?

Model answer: I would roll back if needed, run the evaluation pack against both versions, study the differences and release only when the gate passes.

3. How do you handle secrets in test automation?

Model answer: I use a secret store, synthetic accounts and restricted environments. Generated tests may read only named variables, and logs are redacted.

4. When would you not use AI for automation?

Model answer: For stable deterministic scripts, safety-critical checks without review or any work with forbidden data. Plain code is often the better choice.

5. What was the hardest bug in your agent project?

Model answer: I describe a real one, how a test or review revealed it, how I fixed it and which new check now prevents it.

📝 Assignment

Pick three questions from this page and write full answers using your own project. Then do a 45-minute live coding practice with no AI assistance, and review where you got stuck.

❓ FAQ

Can I use Copilot in a coding interview?

Only if the interviewer says that you can. Ask at the start, and follow the rules that they give.

What if I built the project with AI help?

That is fine if you are open about it and can explain and change every part of it.

🚀 Next Steps

Well done on finishing this lesson. Complete the assignment, then continue with LLM Testing Interview Questions: RAG, Evaluation and Safety.