It's evolving into engineering. Look at a real engineer (the ones who need to get certified). What do they do? They review plans and calculations. They verify the plan complies with relevant engineering standards. They verify the solution is safe and fit for its intended purpose. They stamp it and accept legal and professional responsibility for whatever happens.
There's going to be less 'hacking' and more verifying that you've got E2E encryption and meet the privacy standards required... or justifying that this problem does not require E2E.
I can see that happening. Just like there is a distinction between a pilot and a flight attendant, or a doctor and a nurse, there could be stratification between a "professional software engineer" that is more of an oversight/responsibility role than hands on, that supervises a bunch of vibe coding / AI slop and makes sure nothing bad happens.
Now, the "product manager", "product owner" and "scrum master" roles have been created, so that developers are more like interchangeable / replaceable cogs in the machine.
This all works well for quickly adding new buttons to existing apps, but its pretty useless for innovating new products or architectures, especially since inevitably no one person ends up with a good understanding over the overall product or architecture.