It is partially on the countries where one cannot just slap engineering on their job title as they feel like.

Where signing off contracts does have some implications beyond "it works on my computer".

Engineering is a professional activity, a legal title is just a moat, it doesn't mean that it is Engineering, just a protected profession of some sort.

In al seriousness, Engineering is about verifying systems to make sure their lifespans and failure modes are known, up front.

This has a legal dimension and a practical one. Legally you can make people liable for unreliable systems. But you can also be liable for failure to maintain properly, or failure to warn about impending calamity. Because it's all documented and verified.

Practical you can live worry free in earthquake and flooding proof buildings, trusting in the diligence of Engineers, and maintenance workers, because they and others have liability imposed on them.

For software this is only the case in a few sectors. For buildings in all cases. Not comparable.

When society depends on software is more than comparable.

Any life can be absurdly destroyed via malware, security exploits, accounting gone wrong, a database deleted in production,....

People also don't put up with faulty products, why should computing be an exception, shitty ship now fix later culture?

And above all, calling oneself "engineer" out of a bootcamp, has nothing to do with Engineering.