Recently I spoke to someone who wanted to know what they should call themselves seeing as they never learned software development, formally or otherwise, but that's not stopping them from releasing AI-powered Python projects in GitHub. I suggested Project Manager, but they took offense to that because (I think) they wanted to hear Software Engineer in order to apply to those jobs. My counter-argument was that, legal rules aside, a S.E. should be able to differentiate good code from bad, but my suggestion wasn't super well received.
The point being: I'm always amazed at the cross-purpose impulse of arguing "the title is not important" while, simultaneously, really wanting to use the title.
Member of Technical Staff, Applied AI
You could have suggested “prompt engineer”. As in “engineering by prompting”. :)
Software engineers keep software on the tracks like train engineers keep the train on the tracks. Nobody thinks the train engineer built the train...
As a software engineer (CS degree and ~10 years of pre-AI experience), I'd feel uncomfortable saying I was a Project Manager