Over the course of my career I've held both the "developer and "engineer" titles in different parts of the US. While some of the differences are simply regional

Over the course of my career I've held both the "developer and "engineer" titles in different parts of the US. While some of the differences are simply regional, I have noticed one significant difference between being called an "engineer" versus a "developer". I've found the term to closely correlate with how the organization thinks about building software and how responsibilities and decision making around what to build are broken down. Companies that call programmers "engineers" often employ a number of other people to determine what to build. Product Managers, Business Analysts, UX specialists, etc are more commonly filing this role, while programmers simply write the code, test it, deploy, and fix it. Companies that call programmers "developers" usually have only limited supporting staff like Customer Support and Ops to supplement the actual programming work. Programmers are often experts in an industry (like Healthcare or Finance) and often determine what to build as well as actually building it. These responsibilities are sometimes clearly stated, but more often the decision making is going on behind the scenes.