What is the difference between a software developer, software programmer and software engineer? [closed]

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
11
down vote

favorite

3

I've been working in the IT sector as an "associate software developer" for the past two years. While applying for new jobs, I've seen job titles like "software developer", "software programmer" and "software engineer", but the the requirements often seem to be almost identical. Is there any difference between the roles associated with these job titles?

job-search title job-description

share|improve this question

edited Jan 15 '15 at 6:14

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

closed as off-topic by Jim G., Jan Doggen, gnat, Garrison Neely, IDrinkandIKnowThings Aug 11 '14 at 15:23

• This question does not appear to be about the workplace within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  16
  

  
  
  
  
  
  

  
  In my experience, the terms mean the same thing and are used interchangeably.
  – aroth
  Aug 11 '14 at 7:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Sometimes a Programmer has a little bit lower salary than a Developer/Engineer, but it's probably more to do with the company than any common practice. Perhaps to do with less responsibilies, or that the job is more purely coding - no client meetings, requirements gathering, or such - while a developer/engineer might do those activities in addition to coding.
  – Juha Untinen
  Aug 11 '14 at 11:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  Besides the legal implications, it usually gives away how the company sees people. By extension it is something you could use to get a sense of what the company culture is. Of course this is just an indicator among many others.
  – nha
  Aug 11 '14 at 12:22
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  This question appears to be off-topic because it is about terminology. The distinction between these terms is subjective and arbitrary.
  – Jim G.
  Aug 11 '14 at 12:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  also, see programmers.stackexchange.com/q/4951
  – Andrea
  Aug 11 '14 at 12:29
  

  
  
  
  

 | 
show 1 more comment

up vote
11
down vote

favorite

3

I've been working in the IT sector as an "associate software developer" for the past two years. While applying for new jobs, I've seen job titles like "software developer", "software programmer" and "software engineer", but the the requirements often seem to be almost identical. Is there any difference between the roles associated with these job titles?

job-search title job-description

share|improve this question

edited Jan 15 '15 at 6:14

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

closed as off-topic by Jim G., Jan Doggen, gnat, Garrison Neely, IDrinkandIKnowThings Aug 11 '14 at 15:23

• This question does not appear to be about the workplace within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  16
  

  
  
  
  
  
  

  
  In my experience, the terms mean the same thing and are used interchangeably.
  – aroth
  Aug 11 '14 at 7:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Sometimes a Programmer has a little bit lower salary than a Developer/Engineer, but it's probably more to do with the company than any common practice. Perhaps to do with less responsibilies, or that the job is more purely coding - no client meetings, requirements gathering, or such - while a developer/engineer might do those activities in addition to coding.
  – Juha Untinen
  Aug 11 '14 at 11:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  Besides the legal implications, it usually gives away how the company sees people. By extension it is something you could use to get a sense of what the company culture is. Of course this is just an indicator among many others.
  – nha
  Aug 11 '14 at 12:22
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  This question appears to be off-topic because it is about terminology. The distinction between these terms is subjective and arbitrary.
  – Jim G.
  Aug 11 '14 at 12:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  also, see programmers.stackexchange.com/q/4951
  – Andrea
  Aug 11 '14 at 12:29
  

  
  
  
  

 | 
show 1 more comment

up vote
11
down vote

favorite

3

up vote
11
down vote

favorite

3

3

I've been working in the IT sector as an "associate software developer" for the past two years. While applying for new jobs, I've seen job titles like "software developer", "software programmer" and "software engineer", but the the requirements often seem to be almost identical. Is there any difference between the roles associated with these job titles?

job-search title job-description

share|improve this question

edited Jan 15 '15 at 6:14

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

I've been working in the IT sector as an "associate software developer" for the past two years. While applying for new jobs, I've seen job titles like "software developer", "software programmer" and "software engineer", but the the requirements often seem to be almost identical. Is there any difference between the roles associated with these job titles?

job-search title job-description

share|improve this question

edited Jan 15 '15 at 6:14

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

share|improve this question

share|improve this question

edited Jan 15 '15 at 6:14

edited Jan 15 '15 at 6:14

edited Jan 15 '15 at 6:14

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

asked Aug 11 '14 at 7:00

w͏̢in̡͢g͘̕ed̨p̢͟a͞n͏͏t̡͜͝he̸r̴

200211

200211

closed as off-topic by Jim G., Jan Doggen, gnat, Garrison Neely, IDrinkandIKnowThings Aug 11 '14 at 15:23

• This question does not appear to be about the workplace within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.

closed as off-topic by Jim G., Jan Doggen, gnat, Garrison Neely, IDrinkandIKnowThings Aug 11 '14 at 15:23

• This question does not appear to be about the workplace within the scope defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.

• 
  
  
  

  
  16
  

  
  
  
  
  
  

  
  In my experience, the terms mean the same thing and are used interchangeably.
  – aroth
  Aug 11 '14 at 7:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Sometimes a Programmer has a little bit lower salary than a Developer/Engineer, but it's probably more to do with the company than any common practice. Perhaps to do with less responsibilies, or that the job is more purely coding - no client meetings, requirements gathering, or such - while a developer/engineer might do those activities in addition to coding.
  – Juha Untinen
  Aug 11 '14 at 11:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  Besides the legal implications, it usually gives away how the company sees people. By extension it is something you could use to get a sense of what the company culture is. Of course this is just an indicator among many others.
  – nha
  Aug 11 '14 at 12:22
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  This question appears to be off-topic because it is about terminology. The distinction between these terms is subjective and arbitrary.
  – Jim G.
  Aug 11 '14 at 12:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  also, see programmers.stackexchange.com/q/4951
  – Andrea
  Aug 11 '14 at 12:29
  

  
  
  
  

 | 
show 1 more comment

• 
  
  
  

  
  16
  

  
  
  
  
  
  

  
  In my experience, the terms mean the same thing and are used interchangeably.
  – aroth
  Aug 11 '14 at 7:16
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  Sometimes a Programmer has a little bit lower salary than a Developer/Engineer, but it's probably more to do with the company than any common practice. Perhaps to do with less responsibilies, or that the job is more purely coding - no client meetings, requirements gathering, or such - while a developer/engineer might do those activities in addition to coding.
  – Juha Untinen
  Aug 11 '14 at 11:55
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  Besides the legal implications, it usually gives away how the company sees people. By extension it is something you could use to get a sense of what the company culture is. Of course this is just an indicator among many others.
  – nha
  Aug 11 '14 at 12:22
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  This question appears to be off-topic because it is about terminology. The distinction between these terms is subjective and arbitrary.
  – Jim G.
  Aug 11 '14 at 12:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  also, see programmers.stackexchange.com/q/4951
  – Andrea
  Aug 11 '14 at 12:29
  

  
  
  
  

16

16

In my experience, the terms mean the same thing and are used interchangeably.
– aroth
Aug 11 '14 at 7:16

In my experience, the terms mean the same thing and are used interchangeably.
– aroth
Aug 11 '14 at 7:16

Sometimes a Programmer has a little bit lower salary than a Developer/Engineer, but it's probably more to do with the company than any common practice. Perhaps to do with less responsibilies, or that the job is more purely coding - no client meetings, requirements gathering, or such - while a developer/engineer might do those activities in addition to coding.
– Juha Untinen
Aug 11 '14 at 11:55

Sometimes a Programmer has a little bit lower salary than a Developer/Engineer, but it's probably more to do with the company than any common practice. Perhaps to do with less responsibilies, or that the job is more purely coding - no client meetings, requirements gathering, or such - while a developer/engineer might do those activities in addition to coding.
– Juha Untinen
Aug 11 '14 at 11:55

1

1

Besides the legal implications, it usually gives away how the company sees people. By extension it is something you could use to get a sense of what the company culture is. Of course this is just an indicator among many others.
– nha
Aug 11 '14 at 12:22

Besides the legal implications, it usually gives away how the company sees people. By extension it is something you could use to get a sense of what the company culture is. Of course this is just an indicator among many others.
– nha
Aug 11 '14 at 12:22

4

4

This question appears to be off-topic because it is about terminology. The distinction between these terms is subjective and arbitrary.
– Jim G.
Aug 11 '14 at 12:23

This question appears to be off-topic because it is about terminology. The distinction between these terms is subjective and arbitrary.
– Jim G.
Aug 11 '14 at 12:23

also, see programmers.stackexchange.com/q/4951
– Andrea
Aug 11 '14 at 12:29

also, see programmers.stackexchange.com/q/4951
– Andrea
Aug 11 '14 at 12:29

 | 
show 1 more comment

2 Answers
2

active

oldest

votes

up vote
30
down vote

It is possible that a particular company may use those titles to mean different things and to describe different positions within that company.

But I do not believe that there is a clear distinction between them which is common across different companies.

Personally I have had all three of "developer", "programmer" and "engineer" as titles in different jobs involving the programming of software. There was no relationship between the differing titles and the differing work I did at those jobs.

Don't stress the titles too much, just look at the actual requirements and the actual job descriptions.

Edit: as has been pointed out in the comments, the title "Engineer" carries significance in some countries, e.g. Finland (thanks Juha) and Canada (thanks Dogbert). It's not the case where I am (Australia) nor does it appear to be the case in the USA or the UK, where there may be an implication of greater education or expertise, but I think no more than an implication.

share|improve this answer

edited Apr 6 '16 at 23:46

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
  – Bakuriu
  Aug 11 '14 at 11:34
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
  – Liath
  Aug 11 '14 at 11:41
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
  – Juha Untinen
  Aug 11 '14 at 11:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
  – thanby
  Aug 11 '14 at 12:27
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  @Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
  – Nathan Cooper
  Aug 11 '14 at 12:29
  
  

  
  
  
  

 | 
show 6 more comments

up vote
5
down vote

In theory, development would be the whole process from taking the requirements over planning the project to its execution, while engineering is planning the technical design of the software and programming is the execution of these designs.

But in practice, there is little difference between these titles. In the real world, a person having either of these job titles might be expected to cover the whole scope of a software developement or be reduced to being only a code monkey. The "Senior Software Developer" in company A might have even less responsibility than the "Junior Programmer" in company B.

To learn what kind of work a position actually entails, read between the lines of the actual job description and which skills it states as required. Or even better: ask them.

share|improve this answer

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  +1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
  – Lightness Races in Orbit
  Aug 11 '14 at 14:16
  

  
  
  
  

suggest improvements | 

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
30
down vote

It is possible that a particular company may use those titles to mean different things and to describe different positions within that company.

But I do not believe that there is a clear distinction between them which is common across different companies.

Personally I have had all three of "developer", "programmer" and "engineer" as titles in different jobs involving the programming of software. There was no relationship between the differing titles and the differing work I did at those jobs.

Don't stress the titles too much, just look at the actual requirements and the actual job descriptions.

Edit: as has been pointed out in the comments, the title "Engineer" carries significance in some countries, e.g. Finland (thanks Juha) and Canada (thanks Dogbert). It's not the case where I am (Australia) nor does it appear to be the case in the USA or the UK, where there may be an implication of greater education or expertise, but I think no more than an implication.

share|improve this answer

edited Apr 6 '16 at 23:46

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
  – Bakuriu
  Aug 11 '14 at 11:34
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
  – Liath
  Aug 11 '14 at 11:41
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
  – Juha Untinen
  Aug 11 '14 at 11:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
  – thanby
  Aug 11 '14 at 12:27
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  @Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
  – Nathan Cooper
  Aug 11 '14 at 12:29
  
  

  
  
  
  

 | 
show 6 more comments

up vote
30
down vote

It is possible that a particular company may use those titles to mean different things and to describe different positions within that company.

But I do not believe that there is a clear distinction between them which is common across different companies.

Personally I have had all three of "developer", "programmer" and "engineer" as titles in different jobs involving the programming of software. There was no relationship between the differing titles and the differing work I did at those jobs.

Don't stress the titles too much, just look at the actual requirements and the actual job descriptions.

Edit: as has been pointed out in the comments, the title "Engineer" carries significance in some countries, e.g. Finland (thanks Juha) and Canada (thanks Dogbert). It's not the case where I am (Australia) nor does it appear to be the case in the USA or the UK, where there may be an implication of greater education or expertise, but I think no more than an implication.

share|improve this answer

edited Apr 6 '16 at 23:46

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
  – Bakuriu
  Aug 11 '14 at 11:34
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
  – Liath
  Aug 11 '14 at 11:41
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
  – Juha Untinen
  Aug 11 '14 at 11:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
  – thanby
  Aug 11 '14 at 12:27
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  @Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
  – Nathan Cooper
  Aug 11 '14 at 12:29
  
  

  
  
  
  

 | 
show 6 more comments

up vote
30
down vote

up vote
30
down vote

It is possible that a particular company may use those titles to mean different things and to describe different positions within that company.

But I do not believe that there is a clear distinction between them which is common across different companies.

Personally I have had all three of "developer", "programmer" and "engineer" as titles in different jobs involving the programming of software. There was no relationship between the differing titles and the differing work I did at those jobs.

Don't stress the titles too much, just look at the actual requirements and the actual job descriptions.

Edit: as has been pointed out in the comments, the title "Engineer" carries significance in some countries, e.g. Finland (thanks Juha) and Canada (thanks Dogbert). It's not the case where I am (Australia) nor does it appear to be the case in the USA or the UK, where there may be an implication of greater education or expertise, but I think no more than an implication.

share|improve this answer

edited Apr 6 '16 at 23:46

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

It is possible that a particular company may use those titles to mean different things and to describe different positions within that company.

But I do not believe that there is a clear distinction between them which is common across different companies.

Personally I have had all three of "developer", "programmer" and "engineer" as titles in different jobs involving the programming of software. There was no relationship between the differing titles and the differing work I did at those jobs.

Don't stress the titles too much, just look at the actual requirements and the actual job descriptions.

Edit: as has been pointed out in the comments, the title "Engineer" carries significance in some countries, e.g. Finland (thanks Juha) and Canada (thanks Dogbert). It's not the case where I am (Australia) nor does it appear to be the case in the USA or the UK, where there may be an implication of greater education or expertise, but I think no more than an implication.

share|improve this answer

edited Apr 6 '16 at 23:46

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

share|improve this answer

share|improve this answer

edited Apr 6 '16 at 23:46

edited Apr 6 '16 at 23:46

edited Apr 6 '16 at 23:46

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

answered Aug 11 '14 at 7:18

Carson63000

7,1712748

7,1712748

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
  – Bakuriu
  Aug 11 '14 at 11:34
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
  – Liath
  Aug 11 '14 at 11:41
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
  – Juha Untinen
  Aug 11 '14 at 11:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
  – thanby
  Aug 11 '14 at 12:27
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  @Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
  – Nathan Cooper
  Aug 11 '14 at 12:29
  
  

  
  
  
  

 | 
show 6 more comments

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
  – Bakuriu
  Aug 11 '14 at 11:34
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  @Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
  – Liath
  Aug 11 '14 at 11:41
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
  – Juha Untinen
  Aug 11 '14 at 11:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
  – thanby
  Aug 11 '14 at 12:27
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  @Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
  – Nathan Cooper
  Aug 11 '14 at 12:29
  
  

  
  
  
  

2

2

Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
– Bakuriu
Aug 11 '14 at 11:34

Engineer usually refers to a legal title that requires some sort of exam after taking a degree (at least in some countries), so, legally, a software engineer is a software developer but the opposite need not be true. No idea whether the US have such a distinction, or whether it is taken into consideration.
– Bakuriu
Aug 11 '14 at 11:34

4

4

@Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
– Liath
Aug 11 '14 at 11:41

@Bakuriu In the UK I don't believe you have to have any kind of qualification for label yourself as an engineer. It's a bone of contention for those of us who did engineering degrees...
– Liath
Aug 11 '14 at 11:41

1

1

In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
– Juha Untinen
Aug 11 '14 at 11:53

In Finland, an Engineering diploma specifically states (translated) "With receiving this diploma, you have the right to use the title of ______ Engineer". Emphasis mine.
– Juha Untinen
Aug 11 '14 at 11:53

1

1

While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
– thanby
Aug 11 '14 at 12:27

While in the US "Engineer" tends to imply a more formal educational background, the only time there is an actual written requirement for it is if you are a "Certified Professional Engineer," which implies you have passed an exam like the one mentioned by @Bakuriu
– thanby
Aug 11 '14 at 12:27

3

3

@Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
– Nathan Cooper
Aug 11 '14 at 12:29

@Liath Yes, I believe British Gas send engineers to check your boiler, and if they struggle they call in a technician (obviously a more prestigious title). I hear when you have a PhD in Engineering this title use only compounds the misery of said broken boiler. I would like to add my meaningless (but still quite nice) title of "software consultant" into the fray.
– Nathan Cooper
Aug 11 '14 at 12:29

 | 
show 6 more comments

up vote
5
down vote

In theory, development would be the whole process from taking the requirements over planning the project to its execution, while engineering is planning the technical design of the software and programming is the execution of these designs.

But in practice, there is little difference between these titles. In the real world, a person having either of these job titles might be expected to cover the whole scope of a software developement or be reduced to being only a code monkey. The "Senior Software Developer" in company A might have even less responsibility than the "Junior Programmer" in company B.

To learn what kind of work a position actually entails, read between the lines of the actual job description and which skills it states as required. Or even better: ask them.

share|improve this answer

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  +1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
  – Lightness Races in Orbit
  Aug 11 '14 at 14:16
  

  
  
  
  

suggest improvements | 

up vote
5
down vote

In theory, development would be the whole process from taking the requirements over planning the project to its execution, while engineering is planning the technical design of the software and programming is the execution of these designs.

But in practice, there is little difference between these titles. In the real world, a person having either of these job titles might be expected to cover the whole scope of a software developement or be reduced to being only a code monkey. The "Senior Software Developer" in company A might have even less responsibility than the "Junior Programmer" in company B.

To learn what kind of work a position actually entails, read between the lines of the actual job description and which skills it states as required. Or even better: ask them.

share|improve this answer

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  +1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
  – Lightness Races in Orbit
  Aug 11 '14 at 14:16
  

  
  
  
  

suggest improvements | 

up vote
5
down vote

up vote
5
down vote

In theory, development would be the whole process from taking the requirements over planning the project to its execution, while engineering is planning the technical design of the software and programming is the execution of these designs.

But in practice, there is little difference between these titles. In the real world, a person having either of these job titles might be expected to cover the whole scope of a software developement or be reduced to being only a code monkey. The "Senior Software Developer" in company A might have even less responsibility than the "Junior Programmer" in company B.

To learn what kind of work a position actually entails, read between the lines of the actual job description and which skills it states as required. Or even better: ask them.

share|improve this answer

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

In theory, development would be the whole process from taking the requirements over planning the project to its execution, while engineering is planning the technical design of the software and programming is the execution of these designs.

But in practice, there is little difference between these titles. In the real world, a person having either of these job titles might be expected to cover the whole scope of a software developement or be reduced to being only a code monkey. The "Senior Software Developer" in company A might have even less responsibility than the "Junior Programmer" in company B.

To learn what kind of work a position actually entails, read between the lines of the actual job description and which skills it states as required. Or even better: ask them.

share|improve this answer

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

share|improve this answer

share|improve this answer

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

answered Aug 11 '14 at 12:02

Philipp

20.3k34885

20.3k34885

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  +1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
  – Lightness Races in Orbit
  Aug 11 '14 at 14:16
  

  
  
  
  

suggest improvements | 

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  +1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
  – Lightness Races in Orbit
  Aug 11 '14 at 14:16
  

  
  
  
  

2

2

+1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
– Lightness Races in Orbit
Aug 11 '14 at 14:16

+1: I agree. In fact, the term "software programmer" as applied to these roles is more often than not nothing more than evidence that upper management has no idea what software development actually entails.
– Lightness Races in Orbit
Aug 11 '14 at 14:16

suggest improvements |