I will just reiterate what I posted before about using the term "engineering."
https://news.ycombinator.com/item?id=44855157#44860128
It's about time that there should be a distinguished difference between an engineer who went through engineering school and another who went to a bootcamp/computer science/etc. Not only is it confusing for people like me whenever I see the word engineering - the first thing that comes to my mind are engineering topics, only to find it's just full stack, JavaScript, prompt "engineering" jobs- but it also disturbs the market for both seekers and employers. When an employer posts a "systems engineering" job and gets bombarded with people who had some JS and DevOps work, meanwhile the employer is after systems with hardware and the like, you are making it worse for both sides. And this kind of "relaxed" approach is only in engineering professions for some reason; even as a plumber you need an apprenticeship, let alone being a lawyer, nurse, or doctor.
I agree that the term 'Engineer' has lost all meaning in the software/IT world. I studied CS at a UK uni which was a subject in the engineering school. I then worked with engineers on multidisciplinary projects (mechanical, electrical, chemical) and am a qualified CAD engineer.
When people start advertising for roles my 'mobile engineer' for someone who makes iphone apps it just makes me feel a bit sad. It genuinely cheapens the term.
I imagine 'architects' also get p1ssed off for the same reason tbh. There's probably loads of real architects who see an 'architect' and say 'he's not a bloody architect! I went to architecture school for SEVEN YEARS!!! He's an idiot with a 1 month AWS certificate!'
Why is IT so bad at trying to steal others' glory!?
I expect an employer can escape that by asking for a professional engineer whow can sign and stamp for their work, and has some malpractice insurance.