Mixing
![How are specific skills evaluated in salary? [duplicate]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
Should one omit experience in tasks unrelated to the position applied for?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
6
down vote
favorite
When one has accumulated a number of previous positions, and writes a CV for a new one, there will likely be some positions held, often entry-level jobs, that are nothing at all like the sought position.
Should one simple leave such positions out from the CV all together?
resume job-change cv
edited Jul 12 '12 at 23:42
Rarity
4,37643457
asked Jul 12 '12 at 19:24
Letharion
95011021
add a comment |Â
up vote
6
down vote
favorite
When one has accumulated a number of previous positions, and writes a CV for a new one, there will likely be some positions held, often entry-level jobs, that are nothing at all like the sought position.
Should one simple leave such positions out from the CV all together?
resume job-change cv
edited Jul 12 '12 at 23:42
Rarity
4,37643457
asked Jul 12 '12 at 19:24
Letharion
95011021
add a comment |Â
up vote
6
down vote
favorite
up vote
6
down vote
favorite
When one has accumulated a number of previous positions, and writes a CV for a new one, there will likely be some positions held, often entry-level jobs, that are nothing at all like the sought position.
Should one simple leave such positions out from the CV all together?
resume job-change cv
edited Jul 12 '12 at 23:42
Rarity
4,37643457
asked Jul 12 '12 at 19:24
Letharion
95011021
When one has accumulated a number of previous positions, and writes a CV for a new one, there will likely be some positions held, often entry-level jobs, that are nothing at all like the sought position.
Should one simple leave such positions out from the CV all together?
resume job-change cv
edited Jul 12 '12 at 23:42
Rarity
4,37643457
asked Jul 12 '12 at 19:24
Letharion
95011021
edited Jul 12 '12 at 23:42
Rarity
4,37643457
edited Jul 12 '12 at 23:42
Rarity
4,37643457
edited Jul 12 '12 at 23:42
Rarity
4,37643457
4,37643457
asked Jul 12 '12 at 19:24
Letharion
95011021
asked Jul 12 '12 at 19:24
Letharion
95011021
asked Jul 12 '12 at 19:24
Letharion
95011021
95011021
add a comment |Â
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
3
down vote
accepted
It depends on quite a lot of factors,
First is career stage. You've indicated a fair bit of experience so, yes as the previous positions become older (in time) or longer ago (if there's a lot more jobs recently in sheer numbers), then you'll eventually stop listing the oldest ones - which can be a little difficult sometimes, as you may still have a fair amount of emotional attachment to them.
Second is Industry. Some industries may more interested in all previous positions, for example those in security or government, when compared to new tech where it's really the recent relevant technology experience that's important. Technology skills over 10 years old (at the coding level) can be too old to be worth listing or list in much detail.
Third is the position level. If this is for quite a senior management position, you'll likely not want to show many low level jobs - other than for character purposes and in that case having janitor listed may actually be a bonus! (No offense to Janitors though, key folks!)
Third is career change. If you have switched careers and have many positions/employers in the previous career you may want to sum them all up under a broad heading that is not employer specific. Or perhaps mention one the the larger/longer (employment) ones as an example (one that you can talk about well and perhaps provide references for).
Forth is the brevity required. Some positions and applications don't have much space for listing stuff. Also if your resume is reaching 5 pages instead of the standard 1-2 (as mine was) then it's time for some pruning!
Fifth is just how many jobs you are actually talking about. There are many positions where, if you have more then say 10 jobs you probably want to avoid listing them all, particularly if you can just prune the oldest.
Sixth is nature of the work, e.g. if this was for seasonal jobs within a community where it's usually a different employer from year to year, it may be more ok.
Finally, you can also address this as I did by basically turning previous long descriptions into 1 or 2 line summaries.
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
add a comment |Â
up vote
4
down vote
You only get 30 seconds to make an impression with your resume. Leave everything off the resume that isn't relevant to the specific position you are applying to.
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
add a comment |Â
up vote
2
down vote
You only need the last ten years. If you have those postions in that time, it is best to leave them in the chronological list of your jobs and not really have more than a one liner about the job. It is better to be seen as employed than not employed. However, you don't need to say you are a qualified Access programmer if you don't want to be considered for jobs in that area! Just keep the stuff that is irrelevant to the job you are applying for out of the accomplishments and technical qualifications sections.
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
It depends on quite a lot of factors,
First is career stage. You've indicated a fair bit of experience so, yes as the previous positions become older (in time) or longer ago (if there's a lot more jobs recently in sheer numbers), then you'll eventually stop listing the oldest ones - which can be a little difficult sometimes, as you may still have a fair amount of emotional attachment to them.
Second is Industry. Some industries may more interested in all previous positions, for example those in security or government, when compared to new tech where it's really the recent relevant technology experience that's important. Technology skills over 10 years old (at the coding level) can be too old to be worth listing or list in much detail.
Third is the position level. If this is for quite a senior management position, you'll likely not want to show many low level jobs - other than for character purposes and in that case having janitor listed may actually be a bonus! (No offense to Janitors though, key folks!)
Third is career change. If you have switched careers and have many positions/employers in the previous career you may want to sum them all up under a broad heading that is not employer specific. Or perhaps mention one the the larger/longer (employment) ones as an example (one that you can talk about well and perhaps provide references for).
Forth is the brevity required. Some positions and applications don't have much space for listing stuff. Also if your resume is reaching 5 pages instead of the standard 1-2 (as mine was) then it's time for some pruning!
Fifth is just how many jobs you are actually talking about. There are many positions where, if you have more then say 10 jobs you probably want to avoid listing them all, particularly if you can just prune the oldest.
Sixth is nature of the work, e.g. if this was for seasonal jobs within a community where it's usually a different employer from year to year, it may be more ok.
Finally, you can also address this as I did by basically turning previous long descriptions into 1 or 2 line summaries.
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
add a comment |Â
up vote
3
down vote
accepted
It depends on quite a lot of factors,
First is career stage. You've indicated a fair bit of experience so, yes as the previous positions become older (in time) or longer ago (if there's a lot more jobs recently in sheer numbers), then you'll eventually stop listing the oldest ones - which can be a little difficult sometimes, as you may still have a fair amount of emotional attachment to them.
Second is Industry. Some industries may more interested in all previous positions, for example those in security or government, when compared to new tech where it's really the recent relevant technology experience that's important. Technology skills over 10 years old (at the coding level) can be too old to be worth listing or list in much detail.
Third is the position level. If this is for quite a senior management position, you'll likely not want to show many low level jobs - other than for character purposes and in that case having janitor listed may actually be a bonus! (No offense to Janitors though, key folks!)
Third is career change. If you have switched careers and have many positions/employers in the previous career you may want to sum them all up under a broad heading that is not employer specific. Or perhaps mention one the the larger/longer (employment) ones as an example (one that you can talk about well and perhaps provide references for).
Forth is the brevity required. Some positions and applications don't have much space for listing stuff. Also if your resume is reaching 5 pages instead of the standard 1-2 (as mine was) then it's time for some pruning!
Fifth is just how many jobs you are actually talking about. There are many positions where, if you have more then say 10 jobs you probably want to avoid listing them all, particularly if you can just prune the oldest.
Sixth is nature of the work, e.g. if this was for seasonal jobs within a community where it's usually a different employer from year to year, it may be more ok.
Finally, you can also address this as I did by basically turning previous long descriptions into 1 or 2 line summaries.
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
It depends on quite a lot of factors,
First is career stage. You've indicated a fair bit of experience so, yes as the previous positions become older (in time) or longer ago (if there's a lot more jobs recently in sheer numbers), then you'll eventually stop listing the oldest ones - which can be a little difficult sometimes, as you may still have a fair amount of emotional attachment to them.
Second is Industry. Some industries may more interested in all previous positions, for example those in security or government, when compared to new tech where it's really the recent relevant technology experience that's important. Technology skills over 10 years old (at the coding level) can be too old to be worth listing or list in much detail.
Third is the position level. If this is for quite a senior management position, you'll likely not want to show many low level jobs - other than for character purposes and in that case having janitor listed may actually be a bonus! (No offense to Janitors though, key folks!)
Third is career change. If you have switched careers and have many positions/employers in the previous career you may want to sum them all up under a broad heading that is not employer specific. Or perhaps mention one the the larger/longer (employment) ones as an example (one that you can talk about well and perhaps provide references for).
Forth is the brevity required. Some positions and applications don't have much space for listing stuff. Also if your resume is reaching 5 pages instead of the standard 1-2 (as mine was) then it's time for some pruning!
Fifth is just how many jobs you are actually talking about. There are many positions where, if you have more then say 10 jobs you probably want to avoid listing them all, particularly if you can just prune the oldest.
Sixth is nature of the work, e.g. if this was for seasonal jobs within a community where it's usually a different employer from year to year, it may be more ok.
Finally, you can also address this as I did by basically turning previous long descriptions into 1 or 2 line summaries.
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
It depends on quite a lot of factors,
First is career stage. You've indicated a fair bit of experience so, yes as the previous positions become older (in time) or longer ago (if there's a lot more jobs recently in sheer numbers), then you'll eventually stop listing the oldest ones - which can be a little difficult sometimes, as you may still have a fair amount of emotional attachment to them.
Second is Industry. Some industries may more interested in all previous positions, for example those in security or government, when compared to new tech where it's really the recent relevant technology experience that's important. Technology skills over 10 years old (at the coding level) can be too old to be worth listing or list in much detail.
Third is the position level. If this is for quite a senior management position, you'll likely not want to show many low level jobs - other than for character purposes and in that case having janitor listed may actually be a bonus! (No offense to Janitors though, key folks!)
Third is career change. If you have switched careers and have many positions/employers in the previous career you may want to sum them all up under a broad heading that is not employer specific. Or perhaps mention one the the larger/longer (employment) ones as an example (one that you can talk about well and perhaps provide references for).
Forth is the brevity required. Some positions and applications don't have much space for listing stuff. Also if your resume is reaching 5 pages instead of the standard 1-2 (as mine was) then it's time for some pruning!
Fifth is just how many jobs you are actually talking about. There are many positions where, if you have more then say 10 jobs you probably want to avoid listing them all, particularly if you can just prune the oldest.
Sixth is nature of the work, e.g. if this was for seasonal jobs within a community where it's usually a different employer from year to year, it may be more ok.
Finally, you can also address this as I did by basically turning previous long descriptions into 1 or 2 line summaries.
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
answered Jul 13 '12 at 1:05
Michael Durrant
9,68122856
9,68122856
add a comment |Â
add a comment |Â
up vote
4
down vote
You only get 30 seconds to make an impression with your resume. Leave everything off the resume that isn't relevant to the specific position you are applying to.
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
add a comment |Â
up vote
4
down vote
You only get 30 seconds to make an impression with your resume. Leave everything off the resume that isn't relevant to the specific position you are applying to.
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
add a comment |Â
up vote
4
down vote
up vote
4
down vote
You only get 30 seconds to make an impression with your resume. Leave everything off the resume that isn't relevant to the specific position you are applying to.
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
You only get 30 seconds to make an impression with your resume. Leave everything off the resume that isn't relevant to the specific position you are applying to.
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
answered Jul 13 '12 at 12:05
MathAttack
2,3061220
2,3061220
add a comment |Â
add a comment |Â
up vote
2
down vote
You only need the last ten years. If you have those postions in that time, it is best to leave them in the chronological list of your jobs and not really have more than a one liner about the job. It is better to be seen as employed than not employed. However, you don't need to say you are a qualified Access programmer if you don't want to be considered for jobs in that area! Just keep the stuff that is irrelevant to the job you are applying for out of the accomplishments and technical qualifications sections.
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
add a comment |Â
up vote
2
down vote
You only need the last ten years. If you have those postions in that time, it is best to leave them in the chronological list of your jobs and not really have more than a one liner about the job. It is better to be seen as employed than not employed. However, you don't need to say you are a qualified Access programmer if you don't want to be considered for jobs in that area! Just keep the stuff that is irrelevant to the job you are applying for out of the accomplishments and technical qualifications sections.
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
add a comment |Â
up vote
2
down vote
up vote
2
down vote
You only need the last ten years. If you have those postions in that time, it is best to leave them in the chronological list of your jobs and not really have more than a one liner about the job. It is better to be seen as employed than not employed. However, you don't need to say you are a qualified Access programmer if you don't want to be considered for jobs in that area! Just keep the stuff that is irrelevant to the job you are applying for out of the accomplishments and technical qualifications sections.
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
You only need the last ten years. If you have those postions in that time, it is best to leave them in the chronological list of your jobs and not really have more than a one liner about the job. It is better to be seen as employed than not employed. However, you don't need to say you are a qualified Access programmer if you don't want to be considered for jobs in that area! Just keep the stuff that is irrelevant to the job you are applying for out of the accomplishments and technical qualifications sections.
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
edited Jul 13 '12 at 5:41
yoozer8
4,10442955
4,10442955
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
answered Jul 12 '12 at 20:28
HLGEM
133k25227489
133k25227489
add a comment |Â
add a comment |Â
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%2f2465%2fshould-one-omit-experience-in-tasks-unrelated-to-the-position-applied-for%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
