Mixing
What is the importance of mentioning start/end dates for projects?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
I have seen a number of resumes mentioning a list of significant projects worked on, which also mention the start and end dates, like so:
McCool Project (Jan 2009 - Jul 2009)
  Achieved this, achieved that, achieved some more cool stuff, and then some more, etc. etc.
I am wondering if mentioning the start and end dates of projects, or even the project duration is really necessary. After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Note: I am referring to projects done while being a full-time permanent employee. For a contract-based job, I can totally understand why this information is necessary. (Thanks to JeffO's comment below. )
resume
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
suggest improvements |Â
up vote
2
down vote
favorite
I have seen a number of resumes mentioning a list of significant projects worked on, which also mention the start and end dates, like so:
McCool Project (Jan 2009 - Jul 2009)
  Achieved this, achieved that, achieved some more cool stuff, and then some more, etc. etc.
I am wondering if mentioning the start and end dates of projects, or even the project duration is really necessary. After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Note: I am referring to projects done while being a full-time permanent employee. For a contract-based job, I can totally understand why this information is necessary. (Thanks to JeffO's comment below. )
resume
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
Are these contract work projects or projects that occurred while being an employee?
– user8365
Nov 25 '14 at 14:02
@JeffO Good question. These are projects done while being a full-time permanent employee.
– Masked Man♦
Nov 25 '14 at 16:31
Do you believe anyone reading the resume would take the time to find out the details of the size of the project in every case? By stating it in the resume, this can be a way to state the size of the project as a 2 week project is quite different from a 2 year project, at least to my mind.
– JB King
Nov 25 '14 at 18:05
suggest improvements |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have seen a number of resumes mentioning a list of significant projects worked on, which also mention the start and end dates, like so:
McCool Project (Jan 2009 - Jul 2009)
  Achieved this, achieved that, achieved some more cool stuff, and then some more, etc. etc.
I am wondering if mentioning the start and end dates of projects, or even the project duration is really necessary. After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Note: I am referring to projects done while being a full-time permanent employee. For a contract-based job, I can totally understand why this information is necessary. (Thanks to JeffO's comment below. )
resume
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
I have seen a number of resumes mentioning a list of significant projects worked on, which also mention the start and end dates, like so:
McCool Project (Jan 2009 - Jul 2009)
  Achieved this, achieved that, achieved some more cool stuff, and then some more, etc. etc.
I am wondering if mentioning the start and end dates of projects, or even the project duration is really necessary. After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Note: I am referring to projects done while being a full-time permanent employee. For a contract-based job, I can totally understand why this information is necessary. (Thanks to JeffO's comment below. )
resume
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
edited Nov 25 '14 at 16:33
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
asked Nov 24 '14 at 18:12
Masked Man♦
43.6k25114163
43.6k25114163
Are these contract work projects or projects that occurred while being an employee?
– user8365
Nov 25 '14 at 14:02
@JeffO Good question. These are projects done while being a full-time permanent employee.
– Masked Man♦
Nov 25 '14 at 16:31
Do you believe anyone reading the resume would take the time to find out the details of the size of the project in every case? By stating it in the resume, this can be a way to state the size of the project as a 2 week project is quite different from a 2 year project, at least to my mind.
– JB King
Nov 25 '14 at 18:05
suggest improvements |Â
Are these contract work projects or projects that occurred while being an employee?
– user8365
Nov 25 '14 at 14:02
@JeffO Good question. These are projects done while being a full-time permanent employee.
– Masked Man♦
Nov 25 '14 at 16:31
Do you believe anyone reading the resume would take the time to find out the details of the size of the project in every case? By stating it in the resume, this can be a way to state the size of the project as a 2 week project is quite different from a 2 year project, at least to my mind.
– JB King
Nov 25 '14 at 18:05
Are these contract work projects or projects that occurred while being an employee?
– user8365
Nov 25 '14 at 14:02
Are these contract work projects or projects that occurred while being an employee?
– user8365
Nov 25 '14 at 14:02
@JeffO Good question. These are projects done while being a full-time permanent employee.
– Masked Man♦
Nov 25 '14 at 16:31
@JeffO Good question. These are projects done while being a full-time permanent employee.
– Masked Man♦
Nov 25 '14 at 16:31
Do you believe anyone reading the resume would take the time to find out the details of the size of the project in every case? By stating it in the resume, this can be a way to state the size of the project as a 2 week project is quite different from a 2 year project, at least to my mind.
– JB King
Nov 25 '14 at 18:05
Do you believe anyone reading the resume would take the time to find out the details of the size of the project in every case? By stating it in the resume, this can be a way to state the size of the project as a 2 week project is quite different from a 2 year project, at least to my mind.
– JB King
Nov 25 '14 at 18:05
suggest improvements |Â
3 Answers
3
active
oldest
votes
up vote
8
down vote
accepted
After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Knowing someone worked on a project with a multi-year lifespan is a huge difference than a project of a few months!
You have to deal with the outcomes of your decisions a lot more when you have a project for 3 years than you do for six months. This is beneficial (especially when applying to more senior roles). If I am looking for someone to work on a large project I almost assuredly will prefer people with experience on longer projects.
For those who have many years experience with one company it can help separate out into a more readable fashion the project work one did during their time with that company. For example, having five years with one company might be a single "wall of text" without some delineation, especially if you never got promoted/etc.
If I worked on a project five years ago in many fields this also may mean my skills are somewhat outdated. Clarifying this is helpful.
Additionally, for people who worked primarily contract work that is largely how a resume will appear.
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
suggest improvements |Â
up vote
2
down vote
Not all project experiences are created equally, but I don't think giving date ranges is important. Overlapping projects can look confusing. I would be more concerned knowing the following:
- What are you currently working on?
- What part(s) of the project were you involved in?
- What was the amount of completion of the project?
There's no guarantee a 3 year project was seen through completion or if you were involved during the initial planning stage.
Usually dates of employment are given to help identify gaps along with the amount of time spent there. The dates of individual projects within a given job doesn't tell me what I would really want to know.
suggest improvements |Â
up vote
0
down vote
I would hesitate in adding project dates to my resume. I'm involved in the recruiting process and project dates are not useful to me. To determine the size and scope of a project would require much more than just the project start and end dates. The dates would take up valuable real estate on the resume that is better used to highlight your accomplishments.
answered Nov 25 '14 at 17:43
Muro
48125
suggest improvements |Â
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
8
down vote
accepted
After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Knowing someone worked on a project with a multi-year lifespan is a huge difference than a project of a few months!
You have to deal with the outcomes of your decisions a lot more when you have a project for 3 years than you do for six months. This is beneficial (especially when applying to more senior roles). If I am looking for someone to work on a large project I almost assuredly will prefer people with experience on longer projects.
For those who have many years experience with one company it can help separate out into a more readable fashion the project work one did during their time with that company. For example, having five years with one company might be a single "wall of text" without some delineation, especially if you never got promoted/etc.
If I worked on a project five years ago in many fields this also may mean my skills are somewhat outdated. Clarifying this is helpful.
Additionally, for people who worked primarily contract work that is largely how a resume will appear.
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
suggest improvements |Â
up vote
8
down vote
accepted
After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Knowing someone worked on a project with a multi-year lifespan is a huge difference than a project of a few months!
You have to deal with the outcomes of your decisions a lot more when you have a project for 3 years than you do for six months. This is beneficial (especially when applying to more senior roles). If I am looking for someone to work on a large project I almost assuredly will prefer people with experience on longer projects.
For those who have many years experience with one company it can help separate out into a more readable fashion the project work one did during their time with that company. For example, having five years with one company might be a single "wall of text" without some delineation, especially if you never got promoted/etc.
If I worked on a project five years ago in many fields this also may mean my skills are somewhat outdated. Clarifying this is helpful.
Additionally, for people who worked primarily contract work that is largely how a resume will appear.
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
suggest improvements |Â
up vote
8
down vote
accepted
up vote
8
down vote
accepted
After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Knowing someone worked on a project with a multi-year lifespan is a huge difference than a project of a few months!
You have to deal with the outcomes of your decisions a lot more when you have a project for 3 years than you do for six months. This is beneficial (especially when applying to more senior roles). If I am looking for someone to work on a large project I almost assuredly will prefer people with experience on longer projects.
For those who have many years experience with one company it can help separate out into a more readable fashion the project work one did during their time with that company. For example, having five years with one company might be a single "wall of text" without some delineation, especially if you never got promoted/etc.
If I worked on a project five years ago in many fields this also may mean my skills are somewhat outdated. Clarifying this is helpful.
Additionally, for people who worked primarily contract work that is largely how a resume will appear.
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
After all, wouldn't the recruiter be more interested in what your achieved than whether you started in January or March, or even how long the project lasted? Is there any good reason at all to mention this?
Knowing someone worked on a project with a multi-year lifespan is a huge difference than a project of a few months!
You have to deal with the outcomes of your decisions a lot more when you have a project for 3 years than you do for six months. This is beneficial (especially when applying to more senior roles). If I am looking for someone to work on a large project I almost assuredly will prefer people with experience on longer projects.
For those who have many years experience with one company it can help separate out into a more readable fashion the project work one did during their time with that company. For example, having five years with one company might be a single "wall of text" without some delineation, especially if you never got promoted/etc.
If I worked on a project five years ago in many fields this also may mean my skills are somewhat outdated. Clarifying this is helpful.
Additionally, for people who worked primarily contract work that is largely how a resume will appear.
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
answered Nov 24 '14 at 18:20
Elysian Fields♦
96.9k46292449
96.9k46292449
suggest improvements |Â
suggest improvements |Â
up vote
2
down vote
Not all project experiences are created equally, but I don't think giving date ranges is important. Overlapping projects can look confusing. I would be more concerned knowing the following:
- What are you currently working on?
- What part(s) of the project were you involved in?
- What was the amount of completion of the project?
There's no guarantee a 3 year project was seen through completion or if you were involved during the initial planning stage.
Usually dates of employment are given to help identify gaps along with the amount of time spent there. The dates of individual projects within a given job doesn't tell me what I would really want to know.
suggest improvements |Â
up vote
2
down vote
Not all project experiences are created equally, but I don't think giving date ranges is important. Overlapping projects can look confusing. I would be more concerned knowing the following:
- What are you currently working on?
- What part(s) of the project were you involved in?
- What was the amount of completion of the project?
There's no guarantee a 3 year project was seen through completion or if you were involved during the initial planning stage.
Usually dates of employment are given to help identify gaps along with the amount of time spent there. The dates of individual projects within a given job doesn't tell me what I would really want to know.
suggest improvements |Â
up vote
2
down vote
up vote
2
down vote
Not all project experiences are created equally, but I don't think giving date ranges is important. Overlapping projects can look confusing. I would be more concerned knowing the following:
- What are you currently working on?
- What part(s) of the project were you involved in?
- What was the amount of completion of the project?
There's no guarantee a 3 year project was seen through completion or if you were involved during the initial planning stage.
Usually dates of employment are given to help identify gaps along with the amount of time spent there. The dates of individual projects within a given job doesn't tell me what I would really want to know.
Not all project experiences are created equally, but I don't think giving date ranges is important. Overlapping projects can look confusing. I would be more concerned knowing the following:
- What are you currently working on?
- What part(s) of the project were you involved in?
- What was the amount of completion of the project?
There's no guarantee a 3 year project was seen through completion or if you were involved during the initial planning stage.
Usually dates of employment are given to help identify gaps along with the amount of time spent there. The dates of individual projects within a given job doesn't tell me what I would really want to know.
answered Nov 25 '14 at 16:59
user8365
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
I would hesitate in adding project dates to my resume. I'm involved in the recruiting process and project dates are not useful to me. To determine the size and scope of a project would require much more than just the project start and end dates. The dates would take up valuable real estate on the resume that is better used to highlight your accomplishments.
answered Nov 25 '14 at 17:43
Muro
48125
suggest improvements |Â
up vote
0
down vote
I would hesitate in adding project dates to my resume. I'm involved in the recruiting process and project dates are not useful to me. To determine the size and scope of a project would require much more than just the project start and end dates. The dates would take up valuable real estate on the resume that is better used to highlight your accomplishments.
answered Nov 25 '14 at 17:43
Muro
48125
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
I would hesitate in adding project dates to my resume. I'm involved in the recruiting process and project dates are not useful to me. To determine the size and scope of a project would require much more than just the project start and end dates. The dates would take up valuable real estate on the resume that is better used to highlight your accomplishments.
answered Nov 25 '14 at 17:43
Muro
48125
I would hesitate in adding project dates to my resume. I'm involved in the recruiting process and project dates are not useful to me. To determine the size and scope of a project would require much more than just the project start and end dates. The dates would take up valuable real estate on the resume that is better used to highlight your accomplishments.
answered Nov 25 '14 at 17:43
Muro
48125
answered Nov 25 '14 at 17:43
Muro
48125
answered Nov 25 '14 at 17:43
Muro
48125
answered Nov 25 '14 at 17:43
Muro
48125
48125
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%2f36671%2fwhat-is-the-importance-of-mentioning-start-end-dates-for-projects%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
Are these contract work projects or projects that occurred while being an employee?
– user8365
Nov 25 '14 at 14:02
@JeffO Good question. These are projects done while being a full-time permanent employee.
– Masked Man♦
Nov 25 '14 at 16:31
Do you believe anyone reading the resume would take the time to find out the details of the size of the project in every case? By stating it in the resume, this can be a way to state the size of the project as a 2 week project is quite different from a 2 year project, at least to my mind.
– JB King
Nov 25 '14 at 18:05