You already automate a role. A test automation engineer writing tests for QuickBooks simulates the bookkeeper. Every scenario the bookkeeper performs, you perform with Playwright, in the test environment, before the release. You log in as the bookkeeper and close the month.
Now add the brain. A large language model connected to Playwright through MCP can use the tool to use the tool: the model never touches QuickBooks, it tells Playwright what to click, and Playwright clicks it. What is preventing that agent from doing the exact bookkeeping process in production? Nothing, except the harness, the guardrails that make its outcome deterministic enough to trust. And who has been building guardrails around exactly these scenarios for years? You have. A test that passes on Monday and fails on Tuesday is flaky, you have spent years hunting flakiness, and an agent that lies once in a while is a flaky test with a brain. The harness is what you write anyway: the agent may only touch the pages you allow, every number it pulls must match a line it can point to, and whatever fails the check goes to a person, never into the books.
Microsoft, which makes Playwright, wrote the job down in October 2025: three agents, a planner that explores the app and produces the plan, a generator that turns the plan into tests, a healer that runs them and repairs what breaks. Planner, generator, healer. That is a test automation engineer, in three words.
Klarna automated the role of seven hundred people and, fifteen months later, was hiring people again. Gartner expects more than forty percent of agent projects to be canceled by the end of next year, for cost, value and risk.
Klarna's agent did the work of seven hundred people. Then Klarna hired people back. What was missing?
The owner. Klarna's chief executive said cost had been too predominant a factor, and what you end up having is lower quality. Nobody owned the quality. That is the whole job, and it is the job you already have: somebody who evaluates what the agent did, harnesses what it may do, and improves it when it lies. Software quality assurance becomes agent quality assurance. How many agents do you have? What do they do? How do you evaluate whether they're hallucinating or not? My agent works better than yours, more consistently, with less token. Then I am better than you. If you can save me $900,000 on tokens and do the same job, I don't have problem to pay you $200,000. Either you get automated or you automate others. Those are the two choices this economy will give you.