<?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: Are you guilty of these Project Management CV errors?</title>
	<atom:link href="http://www.arraspeople.co.uk/camel-blog/projectmanagement/are-you-guilty-of-these-project-management-cv-errors/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.arraspeople.co.uk/camel-blog/projectmanagement/are-you-guilty-of-these-project-management-cv-errors/</link>
	<description>Project management and recruitment news from Arras People</description>
	<lastBuildDate>Wed, 08 Feb 2012 11:56:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: PPM Community - Programme and Project Management Community Blogs</title>
		<link>http://www.arraspeople.co.uk/camel-blog/projectmanagement/are-you-guilty-of-these-project-management-cv-errors/comment-page-1/#comment-70201</link>
		<dc:creator>PPM Community - Programme and Project Management Community Blogs</dc:creator>
		<pubDate>Tue, 14 Dec 2010 16:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.arraspeople.co.uk/camel-blog/?p=1661#comment-70201</guid>
		<description>[...] Are you guilty of these project management CV errors &#8211; &#8220;It lays bare some of the hidden errors you might not necessarily look for on your CV. It&#8217;s rated third in number of views as well, so we’ve reached our target audience.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Are you guilty of these project management CV errors &#8211; &#8220;It lays bare some of the hidden errors you might not necessarily look for on your CV. It&#8217;s rated third in number of views as well, so we’ve reached our target audience.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: UK Careers</title>
		<link>http://www.arraspeople.co.uk/camel-blog/projectmanagement/are-you-guilty-of-these-project-management-cv-errors/comment-page-1/#comment-66086</link>
		<dc:creator>UK Careers</dc:creator>
		<pubDate>Tue, 27 Jul 2010 02:58:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.arraspeople.co.uk/camel-blog/?p=1661#comment-66086</guid>
		<description>With the current market being flooded with jobseekers,companies are implementing stricter criteria for selection. This article gave some great tips for creating a reference list.Too many people just rattle off a CV without taking enough time, care and attention over it. A well prepared CV stands out a mile from others that aren&#039;t and will therefore be the one that gets a candidate invited for interview</description>
		<content:encoded><![CDATA[<p>With the current market being flooded with jobseekers,companies are implementing stricter criteria for selection. This article gave some great tips for creating a reference list.Too many people just rattle off a CV without taking enough time, care and attention over it. A well prepared CV stands out a mile from others that aren&#8217;t and will therefore be the one that gets a candidate invited for interview</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lindsayascott</title>
		<link>http://www.arraspeople.co.uk/camel-blog/projectmanagement/are-you-guilty-of-these-project-management-cv-errors/comment-page-1/#comment-53432</link>
		<dc:creator>lindsayascott</dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.arraspeople.co.uk/camel-blog/?p=1661#comment-53432</guid>
		<description>Thanks Ajay, good comments that I totally agree with. I have another post coming up on Friday about cover notes, the much overlooked brother to the CV!</description>
		<content:encoded><![CDATA[<p>Thanks Ajay, good comments that I totally agree with. I have another post coming up on Friday about cover notes, the much overlooked brother to the CV!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay Patwardhan</title>
		<link>http://www.arraspeople.co.uk/camel-blog/projectmanagement/are-you-guilty-of-these-project-management-cv-errors/comment-page-1/#comment-53413</link>
		<dc:creator>Ajay Patwardhan</dc:creator>
		<pubDate>Mon, 26 Oct 2009 18:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.arraspeople.co.uk/camel-blog/?p=1661#comment-53413</guid>
		<description>Good points and the author is asking right questions. I would like dwell upon answers to some of the points mentioned.

1. Every person is different and so is every job. You cannot reuse your resume created for one job to be applied to the next job. I know this is painful, but this helps you focus really on the job(s) that you care for. Sending a cookie cutter resume is a sure way to &quot;delete&quot;, &quot;ignore&quot;, or &quot;next please!&quot;

2. Based on the above hypothesis, the author is  correct to best utilize the CV real estate well. 

3. Basically a recruiter / resume screener / hiring manager is trying to answer a simple question, while going through the heap of resumes. &quot;who are the top 5 candidates that I myself would talk to, in the interview round?&quot;. Even if you any advanced mathematics or algorithms, there is no scientific way to arrive at this top 5. So the screener is basically making three lists in his mind. Must have candidates, may be candidates, and sure shot NO candidates. Its your responsibility of a resume writer to pas through these filters.

3. As mentioned above, the screener is now taking the responsibility of selling these top 5 candidates to the interview panel. Imagine the American Idol preliminary rounds, where judges find out top 100 or 50 finalists to be sold to the American population to vote in the final rounds. That is the real crux of the shows&#039; popularity. Back to resume case, the person need to find out what is the screener going to use criteria to make a &quot;NO&quot; list and try to stay away from it.

4. In my opinion, and back to my point #1, every resume need to be newly created for every job you apply. Here is how to do it... 
A) Carefully read the Req.
B) Underline the key job requirements, key department within the company where the job is going to go, business unit of the large corporation where this job is required.
C) Review your own education, experience, recommendations that are most valuable to this job. The candidate may have worked on a java development, but its useless for an HTML development job.
D) Create a simple table, yes a table in the first page with three columns. Serial number, key job requirements, how do you map against these requirements.
E) Basically you are helping the screener simplify his or her job. So rather than reading a three page resume to find the answer to the key question, stated in a different way, &quot;Hope this is not a wrong candidate!&quot;.

5. Once you have this table in the first page of the resume, remove all the unrelated topics from the rest of the resume and keep only the relevant information.

This has worked very well for me.

Thanks,
Ajay</description>
		<content:encoded><![CDATA[<p>Good points and the author is asking right questions. I would like dwell upon answers to some of the points mentioned.</p>
<p>1. Every person is different and so is every job. You cannot reuse your resume created for one job to be applied to the next job. I know this is painful, but this helps you focus really on the job(s) that you care for. Sending a cookie cutter resume is a sure way to &#8220;delete&#8221;, &#8220;ignore&#8221;, or &#8220;next please!&#8221;</p>
<p>2. Based on the above hypothesis, the author is  correct to best utilize the CV real estate well. </p>
<p>3. Basically a recruiter / resume screener / hiring manager is trying to answer a simple question, while going through the heap of resumes. &#8220;who are the top 5 candidates that I myself would talk to, in the interview round?&#8221;. Even if you any advanced mathematics or algorithms, there is no scientific way to arrive at this top 5. So the screener is basically making three lists in his mind. Must have candidates, may be candidates, and sure shot NO candidates. Its your responsibility of a resume writer to pas through these filters.</p>
<p>3. As mentioned above, the screener is now taking the responsibility of selling these top 5 candidates to the interview panel. Imagine the American Idol preliminary rounds, where judges find out top 100 or 50 finalists to be sold to the American population to vote in the final rounds. That is the real crux of the shows&#8217; popularity. Back to resume case, the person need to find out what is the screener going to use criteria to make a &#8220;NO&#8221; list and try to stay away from it.</p>
<p>4. In my opinion, and back to my point #1, every resume need to be newly created for every job you apply. Here is how to do it&#8230;<br />
A) Carefully read the Req.<br />
B) Underline the key job requirements, key department within the company where the job is going to go, business unit of the large corporation where this job is required.<br />
C) Review your own education, experience, recommendations that are most valuable to this job. The candidate may have worked on a java development, but its useless for an HTML development job.<br />
D) Create a simple table, yes a table in the first page with three columns. Serial number, key job requirements, how do you map against these requirements.<br />
E) Basically you are helping the screener simplify his or her job. So rather than reading a three page resume to find the answer to the key question, stated in a different way, &#8220;Hope this is not a wrong candidate!&#8221;.</p>
<p>5. Once you have this table in the first page of the resume, remove all the unrelated topics from the rest of the resume and keep only the relevant information.</p>
<p>This has worked very well for me.</p>
<p>Thanks,<br />
Ajay</p>
]]></content:encoded>
	</item>
</channel>
</rss>

