I neither prescribed a particular ethical conclusion nor required consultation for my definition. There are lots of people who choose not to work in Defense because of the ethical considerations. There are others whose personal senses of ethics are not offended by the idea of making weapons, or at least are assuaged by the money. I would argue the same interplay between ethics and compensation is at work in e.g. Facebook and other surveillance firms. Quite obviously some people don't mind working for Facebook, even though I personally would find that repugnant.
What I'm not saying is that someone who works for Facebook "isn't an engineer" because I happen to disagree with their ethical choices. I'm saying that if you call yourself an engineer and you don't consider/ignore the ethical consequences of your work then you are an impostor.
The link to the topic at hand/reason I brought this up is that the 737 MAX issue (or the MCAS issue) isn't a technological problem so much as an ethical problem. Considering the technical faults in isolation ("putting the moralism and ethics in their own paragraph") is deliberately blinding one's self to the crux of the issue.
Even in bridge building, the balancing of human civilization's advantages against its environmental cost is a matter of public policy. Engineers may be consulted to assess environmental impact or to provide lower-impact options, but "should we have a bridge here or not" is ultimately a question for political leaders, not engineers.