AI scales the breadth. You set the depth.
The work is shifting. The scarce skill is no longer typing code as fast as possible, but directing agents and verifying their work. Whoever masters that suddenly does far more on their own. Think of the boilerplate that has to be written, or the tests you otherwise keep putting off. The time you win back goes to the questions that demand human insight.
To do that, it helps to follow training so you too can judge where an agent fits best, and which tools you are better off giving it or not. The trouble with agents is that they often sound certain in their answers, whether right or wrong. Being aware of that and steering for it is what separates using an agent from deploying one. Give an agent free rein over your system (read: accept all) and the consequences can hit hard. The difference between an agent that moves you forward and one that does damage is not luck but craftsmanship: it shows in scoping the agent well and always verifying. That craftsmanship is what you learn in these trainings.
Along the way you learn a structured way of working, and a handhold in the sprawl of new AI concepts. You do not need to memorize every term; you learn an approach that holds up while the tools change fast.
For quality engineers this is a logical step. Verification is your craft. In a world full of agents, you become the layer that makes their work reliably deployable. Your role does not disappear; it only grows more important.