Even if you're a bona fide engineer, but not enrolled in the order, calling yourself one opens the floodgates of hell where spaghetti coders do the same and get hired by retarded HR departments to take the lead on some mission-critical software.
I like this. I am a self-learned developer. When my peers call themselves engineers, I spit my coffee.
Ehhhh. If you try to stamp and sign structural engineering documents as an engineer, and then a bridge collapses, you're open to litigation. I don't think anyone has been (successfully?) sued for declaring themeselves as Software Engineers in Canada. There are no damages.
Interestingly, you can call yourself an "SE," and its fine (according the professional engineering associations), but companies in YVR actively recruit "software engineers" (e.g. Electronic Arts)
It seems as though the US prioritizes shit-developers/wannabe-engineers over experienced Canadian developers. Which kind of makes sense, in that you feed your own before feeding your neighbour.
So I really doubt that H1B flooding is a thing. Open to debate though.
http://www.nytimes.com/2015/11/11/us/large-companies-game-h-...
"Many of the visas are given out through a lottery, and a small number of giant global outsourcing companies had flooded the system with applications, significantly increasing their chances of success. While he had one application in last year’s lottery and lost, one of the outsourcing companies applied for at least 14,000."
A quick fix would be to award H1B based on salary instead of lottery.
I do cringe, though, at the extreme overuse of the term in software; I have two parents who are legit PEs in the US and drilled the distinction in with me.
At the very least, it should be reserved for someone with a broad theoretical and practical background who solves more complicated problems ... but you know how title inflation goes.
We do it because it works...