Look, 'software developers' are, to a large part, engineering software. They're making a machine, an engine designed for a specific purpose.
Someone at Subway engineered all those sandwhiches. Someone at the bar engineered all those drinks. A software engineer's engine, code execution, running on processors and memory is a loose metaphor for a literal engine. I argue that programmers are certainly engineers, metaphorically speaking. A parent, however, is an engineer in the literal sense, if you accept that a human body is a literal engine in that it converts power to motion, does W ork as in W = F * d . Some code, I have no doubt, can do W=fd. Those programmers are literal engineers, but others are metaphorical.
Some type Bash commands, but never call it programming, and believe most who script would only describe it as such to one who never heard the term "scripting," because it is literally programming, but simpler and perhaps rudimentary compared to the big programming projects... there are other language examples. Many scripters are programming at the level of software engineering projects. But we all agree without ever raising a vote that scripters are not quite programmers, even though they absolutely are. Graphic Designers were once artists, and then there was WWW and suddenly page/site designers are developers.
At the end of the day, it is protected speech.