Writing two job responsibilities at work
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
How can one write his job title in the CV if I have two responsibilities at work like : CRM Developer / .Net Developer ?
Should it be like?
Title: CRM / .Net Developer
OR should I only write one of them as a title then below in the description write the other ?
resume developer
suggest improvements |Â
up vote
1
down vote
favorite
How can one write his job title in the CV if I have two responsibilities at work like : CRM Developer / .Net Developer ?
Should it be like?
Title: CRM / .Net Developer
OR should I only write one of them as a title then below in the description write the other ?
resume developer
1
Instead of /, use &. That should make it pretty obvious you did both things. Right?
– Falgantil
Jan 20 '16 at 10:44
suggest improvements |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
How can one write his job title in the CV if I have two responsibilities at work like : CRM Developer / .Net Developer ?
Should it be like?
Title: CRM / .Net Developer
OR should I only write one of them as a title then below in the description write the other ?
resume developer
How can one write his job title in the CV if I have two responsibilities at work like : CRM Developer / .Net Developer ?
Should it be like?
Title: CRM / .Net Developer
OR should I only write one of them as a title then below in the description write the other ?
resume developer
asked Jan 20 '16 at 9:49
user3340627
26347
26347
1
Instead of /, use &. That should make it pretty obvious you did both things. Right?
– Falgantil
Jan 20 '16 at 10:44
suggest improvements |Â
1
Instead of /, use &. That should make it pretty obvious you did both things. Right?
– Falgantil
Jan 20 '16 at 10:44
1
1
Instead of /, use &. That should make it pretty obvious you did both things. Right?
– Falgantil
Jan 20 '16 at 10:44
Instead of /, use &. That should make it pretty obvious you did both things. Right?
– Falgantil
Jan 20 '16 at 10:44
suggest improvements |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
In a resume you should always use your official title. This is to avoid appearing to misrepresent yourself and to avoid problems during reference checks.
A typical job history on a resume will list the company name, your actual title, year range and then your responsibilities and accomplishments in a bulleted list.
Even if you have two main roles, you will still be registered in the system or known to HR by a single title: (Junior/Senior) Developer, Consultant, Architect, etc. If you don't know your title, check your offer letter or contract or the description of the position when you originally applied for the job.
Here's a sample job history. Ignore the responsibilities I list and forgive the lousy formating, StackExchange markdown is rather limited.
- CRM Solutions Inc. - Senior Consultant - 2014-Present
- something something CRM
- bla bla .Net bla bla
- ...
- Acme Co. - Developer - 2012-2014 // Junior Developer - 2011-2012
- something something CRM ... using .Net ...
- ...
1
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
suggest improvements |Â
up vote
0
down vote
It all depends what impression you want to convey - what do you want your next role to be? What job are you applying for with this CV?
If you want to emphasise your CRM credentials, you could use something like
2015-2016 CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
If you want to emphasise that you're a .NET developer, you could use something like
2015-2016 .NET Developer, Acme Corp
Development work for a number of CRMs in the Widget Division.
or if you want to emphasise the fact that you're an all-rounder who can do both, you could use something like
2015-2016 .NET & CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
suggest improvements |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
In a resume you should always use your official title. This is to avoid appearing to misrepresent yourself and to avoid problems during reference checks.
A typical job history on a resume will list the company name, your actual title, year range and then your responsibilities and accomplishments in a bulleted list.
Even if you have two main roles, you will still be registered in the system or known to HR by a single title: (Junior/Senior) Developer, Consultant, Architect, etc. If you don't know your title, check your offer letter or contract or the description of the position when you originally applied for the job.
Here's a sample job history. Ignore the responsibilities I list and forgive the lousy formating, StackExchange markdown is rather limited.
- CRM Solutions Inc. - Senior Consultant - 2014-Present
- something something CRM
- bla bla .Net bla bla
- ...
- Acme Co. - Developer - 2012-2014 // Junior Developer - 2011-2012
- something something CRM ... using .Net ...
- ...
1
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
suggest improvements |Â
up vote
1
down vote
In a resume you should always use your official title. This is to avoid appearing to misrepresent yourself and to avoid problems during reference checks.
A typical job history on a resume will list the company name, your actual title, year range and then your responsibilities and accomplishments in a bulleted list.
Even if you have two main roles, you will still be registered in the system or known to HR by a single title: (Junior/Senior) Developer, Consultant, Architect, etc. If you don't know your title, check your offer letter or contract or the description of the position when you originally applied for the job.
Here's a sample job history. Ignore the responsibilities I list and forgive the lousy formating, StackExchange markdown is rather limited.
- CRM Solutions Inc. - Senior Consultant - 2014-Present
- something something CRM
- bla bla .Net bla bla
- ...
- Acme Co. - Developer - 2012-2014 // Junior Developer - 2011-2012
- something something CRM ... using .Net ...
- ...
1
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
suggest improvements |Â
up vote
1
down vote
up vote
1
down vote
In a resume you should always use your official title. This is to avoid appearing to misrepresent yourself and to avoid problems during reference checks.
A typical job history on a resume will list the company name, your actual title, year range and then your responsibilities and accomplishments in a bulleted list.
Even if you have two main roles, you will still be registered in the system or known to HR by a single title: (Junior/Senior) Developer, Consultant, Architect, etc. If you don't know your title, check your offer letter or contract or the description of the position when you originally applied for the job.
Here's a sample job history. Ignore the responsibilities I list and forgive the lousy formating, StackExchange markdown is rather limited.
- CRM Solutions Inc. - Senior Consultant - 2014-Present
- something something CRM
- bla bla .Net bla bla
- ...
- Acme Co. - Developer - 2012-2014 // Junior Developer - 2011-2012
- something something CRM ... using .Net ...
- ...
In a resume you should always use your official title. This is to avoid appearing to misrepresent yourself and to avoid problems during reference checks.
A typical job history on a resume will list the company name, your actual title, year range and then your responsibilities and accomplishments in a bulleted list.
Even if you have two main roles, you will still be registered in the system or known to HR by a single title: (Junior/Senior) Developer, Consultant, Architect, etc. If you don't know your title, check your offer letter or contract or the description of the position when you originally applied for the job.
Here's a sample job history. Ignore the responsibilities I list and forgive the lousy formating, StackExchange markdown is rather limited.
- CRM Solutions Inc. - Senior Consultant - 2014-Present
- something something CRM
- bla bla .Net bla bla
- ...
- Acme Co. - Developer - 2012-2014 // Junior Developer - 2011-2012
- something something CRM ... using .Net ...
- ...
edited Jan 20 '16 at 11:58
answered Jan 20 '16 at 11:50


Lilienthal♦
53.9k36183218
53.9k36183218
1
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
suggest improvements |Â
1
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
1
1
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
I agree, always use the official title in the heading
– Kilisi
Jan 20 '16 at 23:06
suggest improvements |Â
up vote
0
down vote
It all depends what impression you want to convey - what do you want your next role to be? What job are you applying for with this CV?
If you want to emphasise your CRM credentials, you could use something like
2015-2016 CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
If you want to emphasise that you're a .NET developer, you could use something like
2015-2016 .NET Developer, Acme Corp
Development work for a number of CRMs in the Widget Division.
or if you want to emphasise the fact that you're an all-rounder who can do both, you could use something like
2015-2016 .NET & CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
suggest improvements |Â
up vote
0
down vote
It all depends what impression you want to convey - what do you want your next role to be? What job are you applying for with this CV?
If you want to emphasise your CRM credentials, you could use something like
2015-2016 CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
If you want to emphasise that you're a .NET developer, you could use something like
2015-2016 .NET Developer, Acme Corp
Development work for a number of CRMs in the Widget Division.
or if you want to emphasise the fact that you're an all-rounder who can do both, you could use something like
2015-2016 .NET & CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
It all depends what impression you want to convey - what do you want your next role to be? What job are you applying for with this CV?
If you want to emphasise your CRM credentials, you could use something like
2015-2016 CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
If you want to emphasise that you're a .NET developer, you could use something like
2015-2016 .NET Developer, Acme Corp
Development work for a number of CRMs in the Widget Division.
or if you want to emphasise the fact that you're an all-rounder who can do both, you could use something like
2015-2016 .NET & CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
It all depends what impression you want to convey - what do you want your next role to be? What job are you applying for with this CV?
If you want to emphasise your CRM credentials, you could use something like
2015-2016 CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
If you want to emphasise that you're a .NET developer, you could use something like
2015-2016 .NET Developer, Acme Corp
Development work for a number of CRMs in the Widget Division.
or if you want to emphasise the fact that you're an all-rounder who can do both, you could use something like
2015-2016 .NET & CRM Developer, Acme Corp
Worked on a number of .NET-based CRMs in the Widget Division.
answered Jan 20 '16 at 11:51


Philip Kendall
40.9k27105135
40.9k27105135
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%2f60771%2fwriting-two-job-responsibilities-at-work%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
1
Instead of /, use &. That should make it pretty obvious you did both things. Right?
– Falgantil
Jan 20 '16 at 10:44