<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Common CV mistakes in IT recruitment</title>
	<atom:link href="http://blog.goyello.com/2009/05/05/common-cv-mistakes-in-it-recruitment/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.goyello.com/2009/05/05/common-cv-mistakes-in-it-recruitment/</link>
	<description>Sharing our daily IT experience</description>
	<lastBuildDate>Wed, 08 Sep 2010 12:49:10 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: KeHoeff</title>
		<link>http://blog.goyello.com/2009/05/05/common-cv-mistakes-in-it-recruitment/comment-page-1/#comment-49</link>
		<dc:creator>KeHoeff</dc:creator>
		<pubDate>Thu, 28 May 2009 23:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.goyellogroup.nl/?p=96#comment-49</guid>
		<description>hey this is a very interesting article!</description>
		<content:encoded><![CDATA[<p>hey this is a very interesting article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aga Gibowska</title>
		<link>http://blog.goyello.com/2009/05/05/common-cv-mistakes-in-it-recruitment/comment-page-1/#comment-15</link>
		<dc:creator>Aga Gibowska</dc:creator>
		<pubDate>Thu, 14 May 2009 13:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.goyellogroup.nl/?p=96#comment-15</guid>
		<description>Thank you for your comment Gary! I really aprreciate the feedback you gave. What you wrote here made me look at things from a different perspective. I totally agree that sometimes it&#039;s just better to meet face to face with the recruiter to get the story straight rather than put all the explainations on the resume. I agree that the strange dates may be misleading and give a false impression about the candidate, for example, that ha is a &quot;pathological job-hopper&quot;. Despite all my complaints here I don&#039;t reject candidates with inaccurate employement dates. It&#039;s better to discuss such things in person, so I usually invite them.</description>
		<content:encoded><![CDATA[<p>Thank you for your comment Gary! I really aprreciate the feedback you gave. What you wrote here made me look at things from a different perspective. I totally agree that sometimes it&#8217;s just better to meet face to face with the recruiter to get the story straight rather than put all the explainations on the resume. I agree that the strange dates may be misleading and give a false impression about the candidate, for example, that ha is a &#8220;pathological job-hopper&#8221;. Despite all my complaints here I don&#8217;t reject candidates with inaccurate employement dates. It&#8217;s better to discuss such things in person, so I usually invite them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://blog.goyello.com/2009/05/05/common-cv-mistakes-in-it-recruitment/comment-page-1/#comment-13</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Wed, 13 May 2009 10:34:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.goyellogroup.nl/?p=96#comment-13</guid>
		<description>You hit the nail on the head!  A good resume is difficult to write because of its simplicity.  Most employers look for solid active verbs and not the lengthy dribble of past life experiences.  

I also agree with you about the pettiness of experiences.  It looks like desperation when a candidate writes that he helps his grandma take out the trash when he is applying for a leadership position.  Or, even worse, it looks like he has been too lazy to update his resume since he was in high school.

I believe that the dates of past employment should be more accurate, although I do see a few exceptions that would keep me from doing this.  For example, if the candidate was laid off after a few months of work, twice during one year due to economic circumstances, through no fault of his own, he might not want to be too specific about that on the resume if it seems to smell fishy.  It&#039;s sometimes better to get the interview and explain some things then.  Explanations of a sketchy past rarely look good on any resume or CV.

Overall, I agree with your advice.  Keep things concise using power words.  Be detailed but relevant.  As Shakespeare said &quot;Brevity is the soul of wit&quot;.  Wit is good on a resume.  Monologues are not.</description>
		<content:encoded><![CDATA[<p>You hit the nail on the head!  A good resume is difficult to write because of its simplicity.  Most employers look for solid active verbs and not the lengthy dribble of past life experiences.  </p>
<p>I also agree with you about the pettiness of experiences.  It looks like desperation when a candidate writes that he helps his grandma take out the trash when he is applying for a leadership position.  Or, even worse, it looks like he has been too lazy to update his resume since he was in high school.</p>
<p>I believe that the dates of past employment should be more accurate, although I do see a few exceptions that would keep me from doing this.  For example, if the candidate was laid off after a few months of work, twice during one year due to economic circumstances, through no fault of his own, he might not want to be too specific about that on the resume if it seems to smell fishy.  It&#8217;s sometimes better to get the interview and explain some things then.  Explanations of a sketchy past rarely look good on any resume or CV.</p>
<p>Overall, I agree with your advice.  Keep things concise using power words.  Be detailed but relevant.  As Shakespeare said &#8220;Brevity is the soul of wit&#8221;.  Wit is good on a resume.  Monologues are not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
