Example · SDET / Test Automation Engineer
Let an agent into your test repo and the page objects write themselves. Whether the nightly is actually red still lands on you.
25 of your 40 hours still need you
- 11 stay yours
- 14 faster with AI
- 15 tools could take
A typical week at the middle pace. Your plan uses your own tasks.
Is test automation a dying career?
By our task-by-task count, 25 of a typical 40-hour week as an SDET still need a person. Tools could already take about 15 hours. New tests from a spec, page objects and fixtures, the pipeline config and the load-test script make up 39% of your week. Models already do this work well, and it is the part you were hired for.
Read more
If you have let an agent loose on your test code, you have seen it. It writes clean page objects in minutes.
The same experiment shows what holds. Some generated tests assert a bug into place because the spec was wrong. Some "fix" a flaky test by adding a retry. Catching both takes a person who knows how the system fails. Your job now is deciding whether red is real, deciding what a release gate should block, and reading a performance result against a system you understand. You already do all three, and your title says "engineer in test" as if the test were the point. For many SDETs, two of the three are the hardest parts of the week: the early-morning red pipeline and the request to make it faster. This report helps you put your name on the decisions you already make.
The hard truth
AI speeds delivery, but stability is lagging behind.
Teams using more AI tend to ship faster, and their releases tend to be less stable. Closing that gap is your skill set.
Sources (2)
- AI adoption is now linked to higher delivery throughput but still to lower delivery stability. Google Cloud, 2025 DORA Report, 2025-09
- 30% of nearly 5,000 tech professionals report little or no trust in AI-generated code. Google Cloud, 2025 DORA Report, 2025-09
What stays yours
"Is the nightly red because of a bug, the test, or the environment?"
The answer lives in the history of what broke, which services share a database, and which squad shipped late. A model can read the log, but it does not know that one service always times out on the first run after a schema migration.
Reading a load-test result and saying "that p95 is real" about the slowest 5% of requests
A performance drop looks the same whether the code regressed or the perf environment was under-provisioned that night. Calling it wrong either way costs a release or an outage. The judgment needs the environment's history and the business's tolerance, and neither is written down.
Deciding what the merge gate blocks
Where your company is audited, the merge-blocking pipeline is evidence in a change-management control. Someone has to be answerable for what it checks and what it waives. Often, informally, that is the SDET.
Knowing a generated test asserts the wrong behavior
A green test that locks in a bug is the most expensive kind of mistake, because it looks like coverage. The person who reads a test against what the system should do, rather than what the spec said, is the constraint on every test-generation tool.
Telling a service team their contract change will break a consumer before they deploy
Contract tests catch the break. Knowing which consumer matters, who owns it and whether the break is acceptable this sprint is organizational knowledge.
What's next for an SDET?
Plan A is your best move inside the work you do now. Most sessions in the 13-week plan build toward it.
- A
Become the named release-gate owner
Why it fits
Why you. If you already make the call when the nightly is red, a record of telling real failures from noise is standing nobody else on your team has. The gap between what you do and what your title says is the smallest of the three moves.
The gap. Usually no written gate standard exists, and waivers happen in chat. Nobody has named an owner at your level, so it can be anybody, including "pipeline green."
The trade-off. You become the person blamed, in writing, when a waived threshold becomes an outage. The stress stays the same, but you have more authority on paper. You will also ship fewer tests and less framework code for a quarter, and someone will count.
Other moves that fit
These are also good bets in this field. Read them if Plan A doesn't suit you.
Own performance risk decisions
Why it fits
Why you. "Is that p95 real," meaning is the slowest 5% of requests truly slower, is the question people already bring you. The script is exposed, but the judgment behind the threshold is work AI is unlikely to take over, and often nobody else reads the perf environment's history.
The gap. Thresholds were set once and never revisited. No SLO (service level objective, the agreed performance target) is written down with a business owner's name, and perf results go to a channel nobody reads.
The trade-off. It is narrower than the release-gate move and depends on the company caring about performance. Where the product is a dashboard and latency costs nothing, this move is a hobby. It also competes with a site reliability (SRE) team if you have one.
The portable hedge: test-infrastructure engineer with a public ledger
Why it fits
Why you. Taking a suite from a flaky, slow gate to a trusted one is worth money at every company with a pipeline, and it is measurable. Flaky rate, gate time and escaped defects are three numbers you can take anywhere.
The gap. You have no public artifact yet and no idea what the market pays for "quality platform" or "developer productivity" seats.
The trade-off. Leaving resets the asset this report says protects you. Your first year anywhere new is your most exposed: system context starts at zero and test-writing is all anyone can measure.
What's a plan B for test automation engineers?
Plan B is a job AI is creating that these skills already fit. One session a week in the plan trains you for it, so it is ready if your job shrinks or you want a change.
BPlan B, picked for this role
AI evaluation specialist
Your nightly suites already tell real failures from flaky ones, and building eval harnesses for AI features uses that same judgment and tooling.
Other options
Agent reliability and quality engineer
Owning whether the build is actually red is reliability work, and a shipped agent test harness plus a few more years opens this senior door.
Agent simulation scenario designer
Scripting scenarios that drive a system through every path is what agent simulation needs, with conversations in place of page objects.
In your own plan you can switch to any of the 47 roles.
The first two weeks
The first 2 of 13 weeks. Three sessions a week: 45 minutes on Monday, 60 on Wednesday and 90 on Friday. In Weeks 5 and 9 the Friday session is a release, so move those weeks to match your release calendar. Every session ends in something written or a number. You also do one 40-minute Plan B session a week. By week 13 you'll have a signed release gate standard with a waiver log, a quarantine policy for flaky tests, and a one-page memo asking to own the gate.
- Week 1: Measure your week
What you do
- AKeep a time log for one week and compare it with the task list in this report.
- AGo through the last thirty nightly test runs. Count failures, real bugs, flaky tests and environment problems.
- AReopen a batch of agent-written test pull requests (PRs), or generate some on a public repo. Sort each one as proves something, tautological (always passes), asserts the wrong behavior, or hides flakiness.
- BTake Anthropic's AI Capabilities and Limitations course. Write one test idea for each limit it covers.
- Week 2: Check the AI tool policy
What you do
- AAsk your manager in writing what agents may touch, such as test code, CI (continuous integration) config, the perf environment or staging, and who decided.
- AFind who owns the change management control, such as SOC 2, a common security audit, if you are audited. Ask for last year's control description.
- ACompare the control text with what really happens when the nightly run is red. Write one page on the difference.
- BDo the verification section of Claude Code in Action, Anthropic's course on its coding agent. Have the agent add tests to a small open-source repo, then review them.
Three courses from the plan
Checked 2026-10-11.
- ISTQB Certified Tester Foundation Level (CTFL) v4.0ISTQB via AT*SQA (US exam) · $229
Only if the postings you want ask for it. It is the prerequisite for every other ISTQB paper.
- ISTQB Advanced Level Test Automation Engineering (CTAL-TAE) v2.0ISTQB via AT*SQA · $249
No. It certifies the exposed half, and a senior SDET usually already owns the architecture.
- ISTQB Test Automation Strategy (CT-TAS) v1.0ISTQB via AT*SQA · $249
Maybe after Week 12 if Plan A lands and you want the vocabulary for a strategy document.
Risks beyond AI: highCost-center risk
This risk does not come from AI. Test automation is an engineering cost center and gets cut when engineering wants to look lean, because a green pipeline is invisible and a red one looks like your fault. Yahoo pushed to eliminate its separate QA function between mid-2014 and early 2015, before any of today's tools existed, and the 2022 to 2023 tech layoffs hit QA and platform teams again. Under the moderate scenario this risk is about the same size as the AI one for you, and the remedy for each is different.
Where this could be wrong
- Flaky triage may be more exposed than we scored. Our capability score assumes agents classify well and root-cause badly. If a triage agent fed your thirty-run history correctly labels the environment failures in Week 1, that task becomes more exposed and owning the release gate becomes urgent.
- We assumed the gate call is yours informally. If a senior SDET or a release manager already decides and you report, the release-gate move means joining the decision rather than owning it, and that task gives you less protection.
- Your company may not care about performance. The performance move assumes a product where latency costs money. If performance results have gone unread for a year, that move is a hobby and the plan is the release gate and the hedge.
- A senior SDET could claim the release gate fast. More experience and the framework in hand make a stronger claim than yours. If they want the gate, focus on performance risk and the hedge.
Also matched: sdet, test automation engineer, software development engineer in test. Research checked 2026-10-11. Page updated .