When I was working in process engineering I was trying to optimize the outputs from our industrial process on a day to day basis in this role broadly speaking I try to optimize the data extracted from the same industrial process.
Mostly I'm concerned with how can we extract data out of our plant, how do we represent and present that data (particularly to operators and technicians) and how can we better recognize and respond to underlying trends in the data.
Before I assumed the role (in 2011) my predecessor, who had a background as a statistician, was called a 'Process Statistician' so I assume my Manager changed the job title to reflect my background as an Engineer (Materials Engineering in my case).
In my world, which is industrial manufacturing there are scientific theories - fluid dynamics, thermodynamics, kinetics etc. which govern the fundamentals and limits of the process.
As an engineer your take this knowledge along with your own intuitive experience and work to ensure the reactor is operating at peak efficiency.
That is not to say programming isn't a difficult job that requires a lot of analytical and creative thinking similar to an engineer. The difference is in getting a degree in something that has 4-5 years of calculus based math, physics...etc classes. There is also a rigorous 8 hour test to get a license after 4 years on the job.
I guess the broad term of building something and doing analysis fits here, but I don't see any Data Engineers in practice. What I see are Data Scientists and Data Analysts. Of course I'm arguing over semantics here, but it is important to get the distinction correct.
Do you happen to have a reference for this? At first glance, it seems to be incorrect rather than nitpicky.
Anecdotally, I know plenty of people who do not have ABET accredited degrees and have "engineer" in their title in the US.
>To get a professional engineer's license, you must graduate from an ABET accredited program.
In some states you can take the FE and PE exam with a related non-ABET accredited degree and work experience based, and in some states you can take the exams with no degree based on experience only. For example, NY let's you substitute work experience for a degree. There's a table where you can see how much experience you need based on your degree (or lack of one).
>Unless you have a professional engineers license, you can't testify in court as an engineer
Courts determine what credentials qualify someone to testify as an expert witness, not state licensing boards.
In some states, testifying in court as an engineer does qualify as practicing engineering without a license, and the state licensing board could fine you after the fact. However, in other states testifying in court doesn’t necessarily qualify as practicing engineering.
(There are lots of other articles about that case, that one sums it up mostly in the url)
https://www.payscale.com/college-salary-report/majors-that-p...
Now, if you plan to work in structural or civil engineering or another field where accreditation is important, than yes, I would tend to agree that having an ABET accredited degree is important (as well as taking the PE exam for that field).
Fields where ABET accreditation isn't terribly important (computational finance, google, facebook, and so forth) often pay more than the fields where it is (mechanical, civil). My guess is that passing the PE for computer engineering wouldn't make a big difference in your compensation at a top tech company, I certainly don't know anyone at those companies who has bothered - though I certainly am willing to evidence to the contrary!
Of course there are also fields where everybody pursues a license such as civil.
If I were to call myself an engineer, it would be in a field that doesn't have a discipline-specific license in my state. I don't know if it means that I don't need a license, or what. So far it has never been an issue.