
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Dates of Employment for Older Positions in Work History </title>
<link>https://members.parwcc.com/forums/posts.aspx?topic=1720674</link>
<description></description>
<lastBuildDate>Fri, 26 Jun 2026 22:31:28 GMT</lastBuildDate>
<pubDate>Mon, 2 Jan 2023 14:18:24 GMT</pubDate>
<copyright>Copyright &#xA9; 2023 Professional Association of Resume Writers and Career Coaches</copyright>
<atom:link href="https://members.parwcc.com/forums/topic_rss.asp?id=1720674" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>Dates of Employment for Older Positions in Work History </title>
<link>https://members.parwcc.com/forums/posts.aspx?topic=1720674</link>
<guid>https://members.parwcc.com/forums/posts.aspx?topic=1720674</guid>
<description><![CDATA[I am working on a revision of an existing resume.  The client worked from 2004 - 2022 for the same employer in various HR roles and has described those four positions with years spent in each role under a "Professional Experience" section.   Following is an "Additional Professional Experience" section that describes three roles with three different companies.  The current version of the resume doesn't include dates in this section.   The client is trying to make it harder to guess her age by not listing the dates. Similar to not listing dates of graduation.     I am concerned that it raises a red flag.  Interested in hearing what others think.   Since the jobs were so long ago, does it matter? ]]></description>
<pubDate>Thu, 29 Dec 2022 01:20:28 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://members.parwcc.com/forums/posts.aspx?topic=1720676</link>
<guid>https://members.parwcc.com/forums/posts.aspx?topic=1720676</guid>
<description><![CDATA[For clarification - the “Additional Professional Experience” section jobs are all HR management roles and relevant to the current job target.  Would be less concerned about dates  if they were not directly related.<br /><br /><br />]]></description>
<pubDate>Thu, 29 Dec 2022 03:40:54 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://members.parwcc.com/forums/posts.aspx?topic=1720807</link>
<guid>https://members.parwcc.com/forums/posts.aspx?topic=1720807</guid>
<description><![CDATA[I agree that not having dates would raise questions. Even though the experience is related it could be left off, or the dates could be added.]]></description>
<pubDate>Sat, 31 Dec 2022 02:30:45 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://members.parwcc.com/forums/posts.aspx?topic=1720858</link>
<guid>https://members.parwcc.com/forums/posts.aspx?topic=1720858</guid>
<description><![CDATA[I do that all the time with relevant older experience, but no one needs to know the dates.  It doesn't throw flags because most recruiters know why it is on there in that format.  The candidate may have to fill out an application listing the dates of employment, but that is not what a resume is. An example I always use is for my CPA and accounting executive clients.  Many of them start with the Big4 accounting firms.  It's just something you have to do if you want to be a controller or CFO for a publicly traded company.  For many of them, the Big4 public experience is going to be 20 years ago - but it has to be on the resume.  I add a public accounting experience section with no dates. I have successfully used the Additional Experience section depending on the story I want to tell. ]]></description>
<pubDate>Sun, 1 Jan 2023 22:27:47 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://members.parwcc.com/forums/posts.aspx?topic=1720878</link>
<guid>https://members.parwcc.com/forums/posts.aspx?topic=1720878</guid>
<description><![CDATA[I would add the dates. I like having the specific information there if the earlier experience was directly related to the job being sought, and it shows that the person had experience with a diversity of companies, not just one.]]></description>
<pubDate>Mon, 2 Jan 2023 15:18:24 GMT</pubDate>
</item>
</channel>
</rss>
