What job title are you working under?

Here it says
"R&D Engineering, Software & Control"

It more or less covers the main ingredients of my day to day job, which in reality is overlapping with just about everything anybody does in the company that I work for. And then some.
 
This brings up a question that I have.. .sometimes wondered but never been to hung up on. Maybe this is a good place for an answer.

I have been in this general field of work for seventeen years. I have a technical degree but no college degree. I build PLC programs from scratch, design and build the machines from scratch (not always, say 40% of the time). Retrofit and upgrade old machines to current safety standards. I can turn a wrench as good as any and have better than average troubleshooting skills. A acquired my current job with no interview, just based on known subcontracting work that I had done.

What would I call myself, my wife says A***OLE but that does not fit the resume profile. I have always said Industrial Electrician. What is your opinions?
 
I see a lot of replies, but we have recently hired PLC programmers on Indeed using the following titles:

Automation Controls Technician
Controls Engineer
Instrumentation & Controls Engineer
PLC Controls Tech
 
I'd recommend Controls Engineer. Controls engineers do entire automated systems and all the stuff and junk that goes along with it.
Currently I'm titled Electrical Engineer but I'm technically one calc2 class away from an electrical engineering degree. I also don't work on high voltage systems which is what I think of as an Electrical Engineer.
If you're looking for someone that only calibrates sensors go with Technician.
also +1 on salary range and location. Location is probably most important.
Last unemployment run I went on I applied to a ton of positions only to find out they're located in American Somoa or a crack neighborhood in California and paid 8.00 an hour. Also specify terms. Office or travel job. Work from home possible or in office every day.

I drove two hours to an interview under the impression that the job was 100% travel in another state only to find out it was an office job in a city with a travel requirement. Wish I had that gas money back.They were ready to hire me till I found out at the end of the interview I'd have a 4 hour commute every day.
 
Last edited:
I'd recommend Controls Engineer.
I think that is misleading if one is just programming PLCs.

To me a controls engineer knows control theory.
If just programming PLCs without knowledge of control theory I would prefer the title of automation engineer.

When I am asked I say engineer/owner. When they ask what I do I say solve problems.
 
I work for a medical device company, and we regularly post ads for employment trying to attract PLC programmers. The controls group at my company have a title of Engineering Technician. We advertise this title, but usually get people that are more mechanic than they are PLC programmers. To me, this title brings up an image of some sort of engineering helper, not a programmer. Out of curiosity, what are some of the forum member job titles at their place of business?

I've been around a few years now since my college days. Early on, for 9 years, I was a software engineer working on *very large* real-time military applications for the Navy. There were at least a couple hundred people on these projects (and sub-projects) if you include all levels of management down to the librarians. Since then, I've been writing software in the Industrial Process Control world (as an engineer). My experience is that any job title with "Technician", "Specialist", or "Associate" attached to it is a non-engineering position, which typically means 'no college degree required'. So that's why your company is getting all these non-engineer-type applicants. But apparently, that's what your company *wants*.

Translation (your company talking here): "We want people with practical experience who know what they're doing, but *don't* have an engineering degree because we don't want to pay the going rate for an engineer, AND because we *know* people without engineering degrees are less likely to leave because they typically have fewer offers to go elsewhere *for financial reasons that make sense*.

And as far as posting the salary. It's common *not* to do that because pay bands at most companies are SO wide. Tens of thousands of dollars is typical. But "technician" is codeword for "engineers need not apply"...
 
Last edited:
My title is Automation Specialist as well. I don't think you can call us just a programmer. We do soo much mpre than just programming.
 
Currently: Engineer
Previously: Engineering Associate, Engineering Technician, Engineering Aide, Electronics Technician

As been mentioned generally anything with an 'Engineer' label attached means four-year degree and commensurate pay. Anything with a 'Technician' label means a two-year degree.

In my experience, even when doing 'Engineer'-level work, anything with a 'technician' label paid considerably less. It also tells prospective employees that their skills are valued (oh that don't consider programming PLCs worthy to be a 'full' engineer). So, you're going to attract the wrong sort.

I know HR can be difficult to work with as they normally have their own set ways of doing things but I would advertise under the job description not job title. Titles are usually used by HR to set requirements, pay bands and other things but often say very little about what the person will be doing or expected to do.

If you're looking for "PLC programmers" why are they advertising for "engineering technicians?"
 
My title is "Automation & Electrical Designer."

The last two places I've worked wanted to put "Engineer" in my title, and I politely refused. Not because I don't do any engineering in my position, but because "Engineer" has a legally codified meaning, and I'm not a licensed PE.


SceneryDriver
 

Similar Topics

I know it's been asked before but as I get older it is becoming harder to give an accurate title to people that aren't in the 'trade' It was...
Replies
54
Views
12,836
Curious, What is your background ? seems that many Electricians I know, aren't really PLC programmers. They have an understanding for...
Replies
29
Views
8,510
A guy who programs PLC's, drives, HMI's, scada's... And is not an engineer. But a Bachelor. WHat is he... ? Not a project engineer !! An...
Replies
107
Views
26,106
Hello, I am trying to setup on plc so If I enter 60 jph (job per hour) it will send the vfd hertz based on what jph is entered by...
Replies
2
Views
148
Years ago, when I was an Automation engineer, I relied on this site heavily, for help, with questions I had. Many times, this site saved my...
Replies
2
Views
162
Back
Top Bottom