So if you're a young vibe-coder and you think you're going to get into an AI Engineering role, pro tips
- read your code
- learn to write tests.
See, everyone can now vibe code all kinds of projects but if your interviewer opens up one of your github projects and asks why you've got a function called isObject(), a blank stare isn't going to get you any points.
Now you might say that we don't need to know what the AI is writing any more and one can make the argument. I'd say you shouldn't be thinking like this till you can reliably build large systems.
And if you don't want to know what code is being written, you will need to have tests to verify the correctness of the program. Including performance tests, because a slow program is often the wrong program.
AI native engineering is about clearly defining outcomes and verifying they are correct. And you will have to verify them for every change in your system. Repeatedly. Automatically.
The AI can only ship features. Not breaking everything else is still your job. Knowing how the code does what it does is still your job.
If you can't do both of these things you're not going to make a compelling hire.
For the 100th time:
Youtubers do NOT want to help you or teach you anything.
They are entertainers who would do anything to get likes and views. That includes lying.