Electricians might be temporarily safe from AI but EEs are knowledge workers too.
"This is wrong, fix it" + recompile, can happen twenty times in ten minutes, but "we discovered the layout is wrong, fix it" is precluded by the cost and time of a new board spin.
AI + text (code) seems like a good match but (E)CAD seems a lot harder to interface AI with. If I'm wrong, I'd like to share that with the EEs on my team, though.
I'm sure it'll happen -- if you can defeat the world Go champion you can certainly route traces -- but so far it seems to be an exception to the bitter lesson, where proprietary hand-tuned algorithms are still on top. Given the lack of large quantities of PCB CAD files that can be appropriated for training, it might be one of those things that has to be self-learned by the AI, again reminiscent of how Alpha Zero worked.
It's being worked on, and as the other commenter said, it's a data problem not a fundamental limitation. That's what's scary to me.
That said the SOTA tools in this space still suck, so it's not here yet :)
For personal stuff? Sure.
But I certainly get why people get burned out on corporate programming. It's either tedious busywork following orders designed by architects whose last time writing code was 30 years ago and they never learned anything ever since, waterfall with glaring issues that the lowest rungs are supposed to magically make go away because upper management doesn't want to reset like they're supposed to, or it's "agile" in its various abominations. There's barely any time, budget or possibility left for actually experimenting a bit or for actually crafting out stuff that works. It's all output, output, output, and being micromanaged by Jira or whatever only adds to the dissatisfaction.
Personally, I left the field for good - I'm heading towards electrical engineering. Good luck coding a robot pulling physical wires.