Example · QA Engineer
60% of your week as a QA engineer is still yours.
AI now writes test cases and scripts. Knowing what a test really proves stays with you.
Make my planA typical week at the middle pace. Your plan uses your own tasks.
Is QA testing a dying career?
In a typical week at the middle pace, 33% of this work needs your judgment and 27% is work you do using AI. AI could do about 40%. 41% of your week is the part you were hired for, and it is the part a model does well: tests from a ticket, cases from acceptance criteria, the regression script, the bug write-up. If you have watched a test-generation pilot, you have seen it write dozens of tests in minutes.
Read more
The same pilots show what holds. A good share of the green tests prove nothing, and it takes a person who knows the product's domain to tell which ones. Your job now is deciding what is worth testing, telling a real defect from a business rule working as designed, and being the name on "go" the night before a release reaches customers. Many QA engineers already do all three, informally, and their title does not say so. Two of the three are usually the hardest parts of the week: the red pipeline that is not a real bug, and release night. This report helps you hold the pen in those rooms.
The week, task by task
Who does each hour of a typical 40-hour week.
See every task
Needs your judgment.
- Release verification and go/no-go evidence8%
- Test data design for domain edge cases (e.g. jurisdictions, mid-period changes)7%
- Deciding what to test: risk-based planning, design reviews7%
- Investigating customer issues referred by support6%
- + 1 smaller task3%
AI does the slow parts. You still own it.
- Flaky test repair and suite maintenance10%
- Exploratory testing of new features10%
- Bug triage: reproduce, rate severity, "is this a bug or is it the domain"8%
AI could do most of it.
- Writing new automated end-to-end tests (e.g. Playwright) from a ticket14%
- Scripted regression execution: the manual checklist not yet in code9%
- Writing manual test cases from acceptance criteria (e.g. TestRail)8%
- Bug write-ups: reproduction steps, screenshots, ticket hygiene6%
- + 1 smaller task4%
Why some tasks still need a person
"Is this a bug, or is that how the domain works?"
The answer lives in domain rules (tax rules, a customer's configuration) and years of watching what broke. A model can quote the rule, but it cannot know which edge case took down a release last year.
Knowing which edge cases break your product's core engine
A wrong calculation can look exactly like a right one until it reaches a customer. Your test data encodes where the bodies are buried, and usually nobody wrote that down.
Saying "go" on release night
Where your company is audited, the sign-off is evidence in a change-management control that customers' auditors rely on. Someone named has to be answerable for it. Often, informally, that is QA.
Finding the generated tests that tested the wrong thing
A green test that asserts nothing is the most expensive kind of mistake, because it hides the problem. The person who can read a test and say "this proves nothing" is the constraint on every test-generation tool.
Working a customer escalation from support
The customer's configuration, their calendar and the support rep's relationship are all undocumented. A model can form a guess, but it cannot call the customer's admin.
Good to know
What is hard about this field, and what you can do about it.
The hard truth
Testers earn less than the developers they work with.
QA pays well, but BLS data show it pays less than development and is growing more slowly. The median QA analyst earns about $30,000 less than the median developer.
Sources (2)
- Median pay in May 2025 was $104,300 for QA analysts and testers and $135,980 for software developers. BLS Occupational Outlook Handbook, Software developers, QA analysts and testers, 2026
- BLS projects 6% job growth for QA analysts and testers versus 10% for developers, 2025 to 2035. BLS Occupational Outlook Handbook, 2026
What's next for a QA engineer?
Plan A is the best move inside the work you do now.
Grow in the job you have
The main focus. Most weekly sessions build toward it.
- Each week
- 4 sessions
- Ready in
- About 5 weeks to your first risk assessment
Why it fits
Why you. If you already say "go" and already know which edge cases break, a record of catching domain bugs before customers do is standing nobody else at your level has. The gap between what you do and what your title says is smaller here than for your other moves.
The gap. Usually no written risk assessment exists. The sign-off is a checkbox, and nobody has named a QA-level owner, so it can be anybody.
The trade-off. You become the person blamed, in writing, when a release goes wrong. The stress stays the same, but you have more authority on paper. You will also ship fewer tests for a quarter, and someone will count.
2 other moves that fit
- Own the quality of machine-written testsReady in about 6 months
- The portable hedge: domain-correctness specialistReady in about 10 weeks to know your market
What's a plan B for QA testers?
Plan B is meant to be different from this job. It was picked because skills from this role carry over.
Get ready for a new kind of job
A second option. A newer job AI is creating that these skills already fit.
Deciding what a test actually proves is your daily work, and evaluating model outputs asks the same question of a new kind of system.
- Each week
- 1 session
- Outlook
- Hiring now
- Pay
- $230K to $270K a year (one posting)One Anthropic safety evaluations posting, 2026; AI lab pay runs well above most employers.
2 other options
- Agent simulation scenario designerWriting edge-case scenarios from real defect reports carries straight into designing test conversations that push an agent until it breaks.
- Domain AI red teamerHunting for the input that makes the release fail is close to red teaming, once you add a public write-up of your findings.
In your own plan you can switch to any of the 47 roles.
The 13 weeks
Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.
By week 13 you will have
AFor Plan A
- Two signed release risk assessments
- A review checklist for AI-written tests
- A memo asking to be the named release-risk owner
BAnd for Plan B
- A draft write-up of your AI test
- A published write-up of your AI test for your portfolio
- 1Measure your week
- 2Check the AI tool rules
- 3Study bugs that escaped
- 4Write a review checklist
You finish withA revised checklist and a count of disagreements
- 5Write a release risk assessment
- 6Try mutation testing
- 7Set a flakiness budget
- 8Write AI agent guidelines
You finish withThree things your suite does that Google advises against
- 9Second assessment and ask
- 10Check the outside market
- 11Gather your evidence
- 12Make your ask
- 13Choose your next step
You finish withOne application sent with your case study attached
Three courses from the plan
- ISTQB Certified Tester Foundation Level (CTFL) v4.0ISTQB via ASTQB / AT*SQA (US exam) · $229
Only if the postings you want ask for it. Some HR screens do. It teaches vocabulary more than judgment.
- ISTQB Certified Tester Advanced Level Test Automation Engineering (CTAL-TAE) v2.0ISTQB via AT*SQA · $249 when last seen; price not shown on the page today
No. It certifies the exposed half.
- ISTQB Certified Tester Test Automation Strategy (CT-TAS) v1.0ISTQB via AT*SQA · $199 when last seen; price not shown on the page today
Maybe, months 4–6, if “Own the quality of machine-written tests” lands and you want the strategy vocabulary.
Checked 2026-09-22.
The fuller picture
Risks beyond AI: highCost-center risk
Forget AI for a moment. QA is an engineering cost center and has been the first team cut in every efficiency wave since continuous delivery, because its output is invisible when it works. Yahoo eliminated its dedicated QA teams in 2014–15, before any of today's tools existed, and the 2022–23 tech layoffs did it again. We score this separately because blaming AI for it would get the remedy wrong.
Where this could be wrong
- Exploratory testing may be more exposed than we scored. Our capability score assumes agents explore breadth more than risk. If an agent seeded with your escaped-defect list finds real bugs in Week 3, that task becomes more exposed and owning the quality of machine-written tests becomes urgent.
- We assumed the release sign-off is yours informally. If a release manager already signs and you merely report, the release-risk move means joining the sign-off rather than owning it, and that task gives you less protection.
- The BLS decline may be a revision artifact. The 201,700 and 187,600 figures come from different projection vintages; the direction matches job boards, but the size is not a clean measurement.
- A senior SDET, a developer who writes test code, could claim the machine-written tests move fast. More experience and the pilot's prompts in hand make a stronger claim than yours. If they want it, focus on release-risk ownership and the domain specialist hedge.
Also matched: qa engineer, test engineer, software tester. Research checked 2026-09-22. Page updated .