<?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 Employers Reading Your Emails?</title>
	<atom:link href="http://recruiteruncensored.com/?feed=rss2&#038;p=665" rel="self" type="application/rss+xml" />
	<link>http://recruiteruncensored.com/?p=665</link>
	<description>The Candid Ramblings Of A Professional Recruiter Who Has Seen It All - Copyright 2010</description>
	<lastBuildDate>Thu, 20 Dec 2012 18:18:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Lisa</title>
		<link>http://recruiteruncensored.com/?p=665&#038;cpage=1#comment-254</link>
		<dc:creator><![CDATA[Lisa]]></dc:creator>
		<pubDate>Tue, 19 Oct 2010 16:08:37 +0000</pubDate>
		<guid isPermaLink="false">http://recruiteruncensored.com/?p=665#comment-254</guid>
		<description><![CDATA[Matt, thanks for stopping by and sharing some insight as a potential employer.]]></description>
		<content:encoded><![CDATA[<p>Matt, thanks for stopping by and sharing some insight as a potential employer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Schoenherr</title>
		<link>http://recruiteruncensored.com/?p=665&#038;cpage=1#comment-252</link>
		<dc:creator><![CDATA[Matt Schoenherr]]></dc:creator>
		<pubDate>Tue, 19 Oct 2010 15:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://recruiteruncensored.com/?p=665#comment-252</guid>
		<description><![CDATA[As a potential employer, job candidates find us one of two ways: by referral or randomly, through our contact form on our website. We take a serious look at the folks who are personally referred to us and although we may not have a fit for them at the time, we place them near the top of the pile in case we need to look for them later. 

As for the random hopefuls that solicit our attention through our website, they get substantially less consideration if they approach us without their whole package. If they simply ask us if we have any availability, they&#039;re likely to get a friendly &quot;no, not at this time, but thanks for asking.&quot; 

If, however, they have an online portfolio that illustrates their web design and print layout experience, NOW they MIGHT have our attention (quality of work withstanding.) At that point, they&#039;ve proven they have the skills and the experience we would seek to put in front of our clients. In essence, if they answer some of the basic questions with PROOF then, yes, they MAY become a candidate during a &quot;cold call.&quot;]]></description>
		<content:encoded><![CDATA[<p>As a potential employer, job candidates find us one of two ways: by referral or randomly, through our contact form on our website. We take a serious look at the folks who are personally referred to us and although we may not have a fit for them at the time, we place them near the top of the pile in case we need to look for them later. </p>
<p>As for the random hopefuls that solicit our attention through our website, they get substantially less consideration if they approach us without their whole package. If they simply ask us if we have any availability, they&#8217;re likely to get a friendly &#8220;no, not at this time, but thanks for asking.&#8221; </p>
<p>If, however, they have an online portfolio that illustrates their web design and print layout experience, NOW they MIGHT have our attention (quality of work withstanding.) At that point, they&#8217;ve proven they have the skills and the experience we would seek to put in front of our clients. In essence, if they answer some of the basic questions with PROOF then, yes, they MAY become a candidate during a &#8220;cold call.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa</title>
		<link>http://recruiteruncensored.com/?p=665&#038;cpage=1#comment-231</link>
		<dc:creator><![CDATA[Lisa]]></dc:creator>
		<pubDate>Fri, 24 Sep 2010 20:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://recruiteruncensored.com/?p=665#comment-231</guid>
		<description><![CDATA[Scot, for me that is an excellent subject line. I&#039;d love to have something that clear in my inbox. Of course, this is my personal opinion.]]></description>
		<content:encoded><![CDATA[<p>Scot, for me that is an excellent subject line. I&#8217;d love to have something that clear in my inbox. Of course, this is my personal opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scot Richards</title>
		<link>http://recruiteruncensored.com/?p=665&#038;cpage=1#comment-230</link>
		<dc:creator><![CDATA[Scot Richards]]></dc:creator>
		<pubDate>Fri, 24 Sep 2010 20:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://recruiteruncensored.com/?p=665#comment-230</guid>
		<description><![CDATA[Hello!  Here is a copy of a subject line I used recently.
&quot;Follow up - Quality Assurance Analyst position - from Scot Richards&quot;
I try to cover the &quot;why&quot; (follow-up), the &quot;what&quot; (position description) and the &quot;who&quot; (me) in the subject line.  As a person who used to get 100 emails a day, I felt the least I could do was to help the recipient with enough information to make a prioritizing decision.

What do you think?  Could my strategy be better?  I would appreciate your experienced input.

Thanks!

@Scot_R]]></description>
		<content:encoded><![CDATA[<p>Hello!  Here is a copy of a subject line I used recently.<br />
&#8220;Follow up &#8211; Quality Assurance Analyst position &#8211; from Scot Richards&#8221;<br />
I try to cover the &#8220;why&#8221; (follow-up), the &#8220;what&#8221; (position description) and the &#8220;who&#8221; (me) in the subject line.  As a person who used to get 100 emails a day, I felt the least I could do was to help the recipient with enough information to make a prioritizing decision.</p>
<p>What do you think?  Could my strategy be better?  I would appreciate your experienced input.</p>
<p>Thanks!</p>
<p>@Scot_R</p>
]]></content:encoded>
	</item>
</channel>
</rss>
