Will a job title change in resume affect my career?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
3
down vote
favorite
As an employer of software industry with 3 years of total IT experience, in which I have worked as:
- Network Support Engineer in Company 'X' for 1 year 3 months and
- Software engineer in Company 'Y' for 1 year 8 months.
When I was working as Network Support Engineer in company 'X' on contract, in the offer letters issued by them, the job title was mentioned as "Network Support Engineer". But, in my experience letter from the same company 'X' they have mentioned the job title as Network Support Engineer later redesignated as "Product Implementation Executive".
- Will this be a problem in the future? After leaving company 'X', I'm working in another company as they did not care about it that much as this is a startup. But, I don't know how they might feel in big companies.
- How can I mention this job title in my resume?
When I told the HR manager of company 'X' to mention only one job title, he says he can't do it and it will be against company policy. Currently I'm mentioning it as Network Support Engineer alone and not mentioning it as Product Implementation Executive.
What should I do for this?
resume software-industry title
suggest improvements |Â
up vote
3
down vote
favorite
As an employer of software industry with 3 years of total IT experience, in which I have worked as:
- Network Support Engineer in Company 'X' for 1 year 3 months and
- Software engineer in Company 'Y' for 1 year 8 months.
When I was working as Network Support Engineer in company 'X' on contract, in the offer letters issued by them, the job title was mentioned as "Network Support Engineer". But, in my experience letter from the same company 'X' they have mentioned the job title as Network Support Engineer later redesignated as "Product Implementation Executive".
- Will this be a problem in the future? After leaving company 'X', I'm working in another company as they did not care about it that much as this is a startup. But, I don't know how they might feel in big companies.
- How can I mention this job title in my resume?
When I told the HR manager of company 'X' to mention only one job title, he says he can't do it and it will be against company policy. Currently I'm mentioning it as Network Support Engineer alone and not mentioning it as Product Implementation Executive.
What should I do for this?
resume software-industry title
What are the respective job descriptions?
– jcm
Jul 15 '14 at 10:01
Hi @jcm, are you asking me for the job descriptions of Network Support Engineer and Product Implementation Executive?
– user3004356
Jul 15 '14 at 10:04
Yes. Are they identical?
– jcm
Jul 15 '14 at 10:13
@jcm Yes they are. Both the job descriptions were relatively same
– user3004356
Jul 15 '14 at 10:19
suggest improvements |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
As an employer of software industry with 3 years of total IT experience, in which I have worked as:
- Network Support Engineer in Company 'X' for 1 year 3 months and
- Software engineer in Company 'Y' for 1 year 8 months.
When I was working as Network Support Engineer in company 'X' on contract, in the offer letters issued by them, the job title was mentioned as "Network Support Engineer". But, in my experience letter from the same company 'X' they have mentioned the job title as Network Support Engineer later redesignated as "Product Implementation Executive".
- Will this be a problem in the future? After leaving company 'X', I'm working in another company as they did not care about it that much as this is a startup. But, I don't know how they might feel in big companies.
- How can I mention this job title in my resume?
When I told the HR manager of company 'X' to mention only one job title, he says he can't do it and it will be against company policy. Currently I'm mentioning it as Network Support Engineer alone and not mentioning it as Product Implementation Executive.
What should I do for this?
resume software-industry title
As an employer of software industry with 3 years of total IT experience, in which I have worked as:
- Network Support Engineer in Company 'X' for 1 year 3 months and
- Software engineer in Company 'Y' for 1 year 8 months.
When I was working as Network Support Engineer in company 'X' on contract, in the offer letters issued by them, the job title was mentioned as "Network Support Engineer". But, in my experience letter from the same company 'X' they have mentioned the job title as Network Support Engineer later redesignated as "Product Implementation Executive".
- Will this be a problem in the future? After leaving company 'X', I'm working in another company as they did not care about it that much as this is a startup. But, I don't know how they might feel in big companies.
- How can I mention this job title in my resume?
When I told the HR manager of company 'X' to mention only one job title, he says he can't do it and it will be against company policy. Currently I'm mentioning it as Network Support Engineer alone and not mentioning it as Product Implementation Executive.
What should I do for this?
resume software-industry title
edited Jul 15 '14 at 10:14
yochannah
4,21462747
4,21462747
asked Jul 15 '14 at 9:45
user3004356
1333
1333
What are the respective job descriptions?
– jcm
Jul 15 '14 at 10:01
Hi @jcm, are you asking me for the job descriptions of Network Support Engineer and Product Implementation Executive?
– user3004356
Jul 15 '14 at 10:04
Yes. Are they identical?
– jcm
Jul 15 '14 at 10:13
@jcm Yes they are. Both the job descriptions were relatively same
– user3004356
Jul 15 '14 at 10:19
suggest improvements |Â
What are the respective job descriptions?
– jcm
Jul 15 '14 at 10:01
Hi @jcm, are you asking me for the job descriptions of Network Support Engineer and Product Implementation Executive?
– user3004356
Jul 15 '14 at 10:04
Yes. Are they identical?
– jcm
Jul 15 '14 at 10:13
@jcm Yes they are. Both the job descriptions were relatively same
– user3004356
Jul 15 '14 at 10:19
What are the respective job descriptions?
– jcm
Jul 15 '14 at 10:01
What are the respective job descriptions?
– jcm
Jul 15 '14 at 10:01
Hi @jcm, are you asking me for the job descriptions of Network Support Engineer and Product Implementation Executive?
– user3004356
Jul 15 '14 at 10:04
Hi @jcm, are you asking me for the job descriptions of Network Support Engineer and Product Implementation Executive?
– user3004356
Jul 15 '14 at 10:04
Yes. Are they identical?
– jcm
Jul 15 '14 at 10:13
Yes. Are they identical?
– jcm
Jul 15 '14 at 10:13
@jcm Yes they are. Both the job descriptions were relatively same
– user3004356
Jul 15 '14 at 10:19
@jcm Yes they are. Both the job descriptions were relatively same
– user3004356
Jul 15 '14 at 10:19
suggest improvements |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
Why not simply list it as "Network Support Engineer/Product Implementation Executive"?
That gets the title you prefer across, as well as the title your HR prefers. Alternatively, list only preferred title in the header, and mention in the description of duties that it is also known within the company as the other one, e.g.:
Network Support Engineer Jan 2013 - (July 2014)
Performed important networky support things, such as (blah) and (blah). This position was
also sometimes referred to as "Product Implementation Executive".
My experience in the UK is that the role and work you did is a lot more important than the job title*, so make sure you describe accurately what your roles, responsibilities, skills, and achievements were.
*note: this probably doesn't hold true for differing seniority levels, so you wouldn't want to be listed as a junior llama wrangling engineer if you were actually a senior llama wrangling engineer.
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
suggest improvements |Â
up vote
0
down vote
- No, I don't think this will be a problem. The IT industry evolves so quickly that what Company A describes as an 'engineer' or a 'developer' is described as a 'coordinator' or 'architect' at Company B (or sometimes that switch happens at Company A, within the space of a year. You've run into this.) Describe what you did, even as you list what you were called. Enough people are familiar with this - especially in the IT field - that very few of them will even think to raise an eyebrow at the job title change. Your career would be negatively impacted if you outright lied about your job title in such a way that it implied experience or skills that you did not have. THAT would indeed be bad. This? This is just another case of "the company tweaked the titles again".
- I would list the hybridized title, unless you feel very strongly that you don't want to be known as a "Product Implementation Executive." (The term "executive" can come up in keyword searches on LinkedIn, and you may have to field a few messages from recruiters who don't glance through peoples' profiles before sending off their "are you interested" emails...but that won't be the majority.)
suggest improvements |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Why not simply list it as "Network Support Engineer/Product Implementation Executive"?
That gets the title you prefer across, as well as the title your HR prefers. Alternatively, list only preferred title in the header, and mention in the description of duties that it is also known within the company as the other one, e.g.:
Network Support Engineer Jan 2013 - (July 2014)
Performed important networky support things, such as (blah) and (blah). This position was
also sometimes referred to as "Product Implementation Executive".
My experience in the UK is that the role and work you did is a lot more important than the job title*, so make sure you describe accurately what your roles, responsibilities, skills, and achievements were.
*note: this probably doesn't hold true for differing seniority levels, so you wouldn't want to be listed as a junior llama wrangling engineer if you were actually a senior llama wrangling engineer.
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
suggest improvements |Â
up vote
3
down vote
Why not simply list it as "Network Support Engineer/Product Implementation Executive"?
That gets the title you prefer across, as well as the title your HR prefers. Alternatively, list only preferred title in the header, and mention in the description of duties that it is also known within the company as the other one, e.g.:
Network Support Engineer Jan 2013 - (July 2014)
Performed important networky support things, such as (blah) and (blah). This position was
also sometimes referred to as "Product Implementation Executive".
My experience in the UK is that the role and work you did is a lot more important than the job title*, so make sure you describe accurately what your roles, responsibilities, skills, and achievements were.
*note: this probably doesn't hold true for differing seniority levels, so you wouldn't want to be listed as a junior llama wrangling engineer if you were actually a senior llama wrangling engineer.
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
Why not simply list it as "Network Support Engineer/Product Implementation Executive"?
That gets the title you prefer across, as well as the title your HR prefers. Alternatively, list only preferred title in the header, and mention in the description of duties that it is also known within the company as the other one, e.g.:
Network Support Engineer Jan 2013 - (July 2014)
Performed important networky support things, such as (blah) and (blah). This position was
also sometimes referred to as "Product Implementation Executive".
My experience in the UK is that the role and work you did is a lot more important than the job title*, so make sure you describe accurately what your roles, responsibilities, skills, and achievements were.
*note: this probably doesn't hold true for differing seniority levels, so you wouldn't want to be listed as a junior llama wrangling engineer if you were actually a senior llama wrangling engineer.
Why not simply list it as "Network Support Engineer/Product Implementation Executive"?
That gets the title you prefer across, as well as the title your HR prefers. Alternatively, list only preferred title in the header, and mention in the description of duties that it is also known within the company as the other one, e.g.:
Network Support Engineer Jan 2013 - (July 2014)
Performed important networky support things, such as (blah) and (blah). This position was
also sometimes referred to as "Product Implementation Executive".
My experience in the UK is that the role and work you did is a lot more important than the job title*, so make sure you describe accurately what your roles, responsibilities, skills, and achievements were.
*note: this probably doesn't hold true for differing seniority levels, so you wouldn't want to be listed as a junior llama wrangling engineer if you were actually a senior llama wrangling engineer.
edited Jul 15 '14 at 12:59
answered Jul 15 '14 at 11:57
yochannah
4,21462747
4,21462747
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
suggest improvements |Â
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
I have found combining works best. I put Help desk technician / Adjunct Instructor. Both the IT and instructional experience are valuable to me, the roles overlapped at times so rather than trying to line by line it I combine them. (plus it looks better on a resume)
– RualStorge
Jul 15 '14 at 18:46
suggest improvements |Â
up vote
0
down vote
- No, I don't think this will be a problem. The IT industry evolves so quickly that what Company A describes as an 'engineer' or a 'developer' is described as a 'coordinator' or 'architect' at Company B (or sometimes that switch happens at Company A, within the space of a year. You've run into this.) Describe what you did, even as you list what you were called. Enough people are familiar with this - especially in the IT field - that very few of them will even think to raise an eyebrow at the job title change. Your career would be negatively impacted if you outright lied about your job title in such a way that it implied experience or skills that you did not have. THAT would indeed be bad. This? This is just another case of "the company tweaked the titles again".
- I would list the hybridized title, unless you feel very strongly that you don't want to be known as a "Product Implementation Executive." (The term "executive" can come up in keyword searches on LinkedIn, and you may have to field a few messages from recruiters who don't glance through peoples' profiles before sending off their "are you interested" emails...but that won't be the majority.)
suggest improvements |Â
up vote
0
down vote
- No, I don't think this will be a problem. The IT industry evolves so quickly that what Company A describes as an 'engineer' or a 'developer' is described as a 'coordinator' or 'architect' at Company B (or sometimes that switch happens at Company A, within the space of a year. You've run into this.) Describe what you did, even as you list what you were called. Enough people are familiar with this - especially in the IT field - that very few of them will even think to raise an eyebrow at the job title change. Your career would be negatively impacted if you outright lied about your job title in such a way that it implied experience or skills that you did not have. THAT would indeed be bad. This? This is just another case of "the company tweaked the titles again".
- I would list the hybridized title, unless you feel very strongly that you don't want to be known as a "Product Implementation Executive." (The term "executive" can come up in keyword searches on LinkedIn, and you may have to field a few messages from recruiters who don't glance through peoples' profiles before sending off their "are you interested" emails...but that won't be the majority.)
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
- No, I don't think this will be a problem. The IT industry evolves so quickly that what Company A describes as an 'engineer' or a 'developer' is described as a 'coordinator' or 'architect' at Company B (or sometimes that switch happens at Company A, within the space of a year. You've run into this.) Describe what you did, even as you list what you were called. Enough people are familiar with this - especially in the IT field - that very few of them will even think to raise an eyebrow at the job title change. Your career would be negatively impacted if you outright lied about your job title in such a way that it implied experience or skills that you did not have. THAT would indeed be bad. This? This is just another case of "the company tweaked the titles again".
- I would list the hybridized title, unless you feel very strongly that you don't want to be known as a "Product Implementation Executive." (The term "executive" can come up in keyword searches on LinkedIn, and you may have to field a few messages from recruiters who don't glance through peoples' profiles before sending off their "are you interested" emails...but that won't be the majority.)
- No, I don't think this will be a problem. The IT industry evolves so quickly that what Company A describes as an 'engineer' or a 'developer' is described as a 'coordinator' or 'architect' at Company B (or sometimes that switch happens at Company A, within the space of a year. You've run into this.) Describe what you did, even as you list what you were called. Enough people are familiar with this - especially in the IT field - that very few of them will even think to raise an eyebrow at the job title change. Your career would be negatively impacted if you outright lied about your job title in such a way that it implied experience or skills that you did not have. THAT would indeed be bad. This? This is just another case of "the company tweaked the titles again".
- I would list the hybridized title, unless you feel very strongly that you don't want to be known as a "Product Implementation Executive." (The term "executive" can come up in keyword searches on LinkedIn, and you may have to field a few messages from recruiters who don't glance through peoples' profiles before sending off their "are you interested" emails...but that won't be the majority.)
edited Jul 15 '14 at 17:32
answered Jul 15 '14 at 17:27
user22432
suggest improvements |Â
suggest improvements |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f30621%2fwill-a-job-title-change-in-resume-affect-my-career%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
What are the respective job descriptions?
– jcm
Jul 15 '14 at 10:01
Hi @jcm, are you asking me for the job descriptions of Network Support Engineer and Product Implementation Executive?
– user3004356
Jul 15 '14 at 10:04
Yes. Are they identical?
– jcm
Jul 15 '14 at 10:13
@jcm Yes they are. Both the job descriptions were relatively same
– user3004356
Jul 15 '14 at 10:19