<?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: Solving the “Candidate Sharing Problem” Using a Social Media Approach</title>
	<atom:link href="http://www.ere.net/2012/10/08/solving-the-%E2%80%9Ccandidate-sharing-problem%E2%80%9D-using-a-social-media-approach/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ere.net/2012/10/08/solving-the-%e2%80%9ccandidate-sharing-problem%e2%80%9d-using-a-social-media-approach/</link>
	<description>Recruiting News, Recruiting Events, Recruiting Community, Social Recruiting</description>
	<lastBuildDate>Sun, 19 May 2013 00:32:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Ty Chartwell</title>
		<link>http://www.ere.net/2012/10/08/solving-the-%e2%80%9ccandidate-sharing-problem%e2%80%9d-using-a-social-media-approach/comment-page-1/#comment-71027</link>
		<dc:creator>Ty Chartwell</dc:creator>
		<pubDate>Thu, 11 Oct 2012 19:06:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=28260#comment-71027</guid>
		<description><![CDATA[Another brilliant article Doc.
Susan - R U Kiddin?]]></description>
		<content:encoded><![CDATA[<p>Another brilliant article Doc.<br />
Susan &#8211; R U Kiddin?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susan Burke</title>
		<link>http://www.ere.net/2012/10/08/solving-the-%e2%80%9ccandidate-sharing-problem%e2%80%9d-using-a-social-media-approach/comment-page-1/#comment-70779</link>
		<dc:creator>Susan Burke</dc:creator>
		<pubDate>Tue, 09 Oct 2012 15:29:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=28260#comment-70779</guid>
		<description><![CDATA[I love the concept of this (and have used it with previous employers).  One concern that continues to be brought up around this though is OFCCP/EEOC reporting.  If you create a list such as this and share it, wouldn&#039;t you then have to include that person in the applicant pool for every position posted for each of those managers, and, potentially, every position being managed by the recruiters who receive those resumes?  The company I work for now is compliance-oriented to an extreme (for a variety of reasons I won&#039;t get into here), and we require our applicants to express interest for every position before we&#039;ll &quot;consider&quot; them for the job.  It&#039;s certainly not ideal from the candidate experience side, but allows us to better manage our applicant pools.  
On a somewhat unrelated note... we&#039;ve been hearing about potential changes to the treatment of candidates with Veterans status - that we would have to consider them for every opening, regardless of whether they applied.  What you&#039;re suggesting in this article might be a great way to help manage that.
Susan]]></description>
		<content:encoded><![CDATA[<p>I love the concept of this (and have used it with previous employers).  One concern that continues to be brought up around this though is OFCCP/EEOC reporting.  If you create a list such as this and share it, wouldn&#8217;t you then have to include that person in the applicant pool for every position posted for each of those managers, and, potentially, every position being managed by the recruiters who receive those resumes?  The company I work for now is compliance-oriented to an extreme (for a variety of reasons I won&#8217;t get into here), and we require our applicants to express interest for every position before we&#8217;ll &#8220;consider&#8221; them for the job.  It&#8217;s certainly not ideal from the candidate experience side, but allows us to better manage our applicant pools.<br />
On a somewhat unrelated note&#8230; we&#8217;ve been hearing about potential changes to the treatment of candidates with Veterans status &#8211; that we would have to consider them for every opening, regardless of whether they applied.  What you&#8217;re suggesting in this article might be a great way to help manage that.<br />
Susan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Halperin</title>
		<link>http://www.ere.net/2012/10/08/solving-the-%e2%80%9ccandidate-sharing-problem%e2%80%9d-using-a-social-media-approach/comment-page-1/#comment-70660</link>
		<dc:creator>Keith Halperin</dc:creator>
		<pubDate>Mon, 08 Oct 2012 17:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=28260#comment-70660</guid>
		<description><![CDATA[Thanks, Dr. Sullivan. ISTM that this assumes a couple of conditions are true:

1) Entered information about candidates is complete, correct, and easily accessible to recruiters and managers. I&#039;d like to work at a place where this is the case- quite often there is a mystery about a possible candidate that takes time and effort to track down.

2) Recruiters and recruiting managers have the bandwidth and support to be able to share in this manner- often we don&#039;t have either.

Cheers,

Keith]]></description>
		<content:encoded><![CDATA[<p>Thanks, Dr. Sullivan. ISTM that this assumes a couple of conditions are true:</p>
<p>1) Entered information about candidates is complete, correct, and easily accessible to recruiters and managers. I&#8217;d like to work at a place where this is the case- quite often there is a mystery about a possible candidate that takes time and effort to track down.</p>
<p>2) Recruiters and recruiting managers have the bandwidth and support to be able to share in this manner- often we don&#8217;t have either.</p>
<p>Cheers,</p>
<p>Keith</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Melrose</title>
		<link>http://www.ere.net/2012/10/08/solving-the-%e2%80%9ccandidate-sharing-problem%e2%80%9d-using-a-social-media-approach/comment-page-1/#comment-70654</link>
		<dc:creator>Richard Melrose</dc:creator>
		<pubDate>Mon, 08 Oct 2012 16:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=28260#comment-70654</guid>
		<description><![CDATA[Great points, Dr. John.

The &quot;sharing candidates&quot; challenge poses the same basic requirements as hiring, promotion, succession planning, high potential identification and strategic workforce planning -- i.e. specifically the need to compare people to jobs and jobs to people, in an expedient and yet results-oriented and compliant manner.

The Profile XT (PXT) assessment accomplishes that by characterizing jobs in terms of Performance Models based on the scale score ranges achieved by top performers and contrast performers, augmented by Job Analysis Surveys.

Employees and candidates assessed with the Profile XT can then be compared directly to any PXT Performance Model to determine the degree of cognitive, behavioral, interest and overall match.  The PXT also provides structured interview questions to probe departures from the performance model ranges. The assessment has a small one-time cost and all future analytics, including unlimited Performance Model comparisons and Strategic Workforce Planning exercises are free.

In the context of candidate sharing, any high quality candidate could be automatically (i.e. via software) compared to the Performance Models for jobs in the same or proximate job family. Strong matches could be forwarded to hiring managers for consideration via emailed &quot;Total Person&quot; interview reports.  &quot;Kept on file&quot; would come to mean &quot;available for immediate and objective consideration&quot;.

Even candidates that turned down offers could be retained as targets for future recruitment, based on a strong job match to a subsequent position opening.

Most employers have no way to make direct, objective valid, job-related comparisons between people and jobs, as required by the Uniform Guidelines on Employee Selection Procedures.  That jeopardizes regulatory compliance but, just as importantly, it undermines enterprise talent management.

r.melrose@vision21.us]]></description>
		<content:encoded><![CDATA[<p>Great points, Dr. John.</p>
<p>The &#8220;sharing candidates&#8221; challenge poses the same basic requirements as hiring, promotion, succession planning, high potential identification and strategic workforce planning &#8212; i.e. specifically the need to compare people to jobs and jobs to people, in an expedient and yet results-oriented and compliant manner.</p>
<p>The Profile XT (PXT) assessment accomplishes that by characterizing jobs in terms of Performance Models based on the scale score ranges achieved by top performers and contrast performers, augmented by Job Analysis Surveys.</p>
<p>Employees and candidates assessed with the Profile XT can then be compared directly to any PXT Performance Model to determine the degree of cognitive, behavioral, interest and overall match.  The PXT also provides structured interview questions to probe departures from the performance model ranges. The assessment has a small one-time cost and all future analytics, including unlimited Performance Model comparisons and Strategic Workforce Planning exercises are free.</p>
<p>In the context of candidate sharing, any high quality candidate could be automatically (i.e. via software) compared to the Performance Models for jobs in the same or proximate job family. Strong matches could be forwarded to hiring managers for consideration via emailed &#8220;Total Person&#8221; interview reports.  &#8220;Kept on file&#8221; would come to mean &#8220;available for immediate and objective consideration&#8221;.</p>
<p>Even candidates that turned down offers could be retained as targets for future recruitment, based on a strong job match to a subsequent position opening.</p>
<p>Most employers have no way to make direct, objective valid, job-related comparisons between people and jobs, as required by the Uniform Guidelines on Employee Selection Procedures.  That jeopardizes regulatory compliance but, just as importantly, it undermines enterprise talent management.</p>
<p><a href="mailto:r.melrose@vision21.us">r.melrose@vision21.us</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
