<?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: Potholes on the Road to Compliance With the New Definition of an Internet Applicant</title>
	<atom:link href="http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/</link>
	<description>Recruiting News, Recruiting Events, Recruiting Community, Social Recruiting</description>
	<lastBuildDate>Tue, 14 Feb 2012 01:03:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Lona Dion</title>
		<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/comment-page-1/#comment-4237</link>
		<dc:creator>Lona Dion</dc:creator>
		<pubDate>Fri, 31 Mar 2006 04:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/#comment-4237</guid>
		<description>Why wait for the Fedora to come back in style?  Leaders lead, never follow!</description>
		<content:encoded><![CDATA[<p>Why wait for the Fedora to come back in style?  Leaders lead, never follow!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Westmoreland</title>
		<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/comment-page-1/#comment-4236</link>
		<dc:creator>Paul Westmoreland</dc:creator>
		<pubDate>Thu, 30 Mar 2006 11:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/#comment-4236</guid>
		<description>&#039;Love That Hat&#039; 
mmm... ahhgree. but so anyhow, the article rawks too. 

What I find healing is this: &#039;If the activities are focused on building a talent pipeline and not filling a specific position, the search activity does not need to be logged.&#039;

M&#039;kay. Okay so I don&#039;t like what most people - including experts in our trade whom I respect - have written about this thing.

Long and short, that With both passive and active candidates, no matter the source or method, we only record those who respond to our queries and are qualified. As long as we do it consistently. Yes? No? Whether in response to postings, searches of internal/external databases, general web searches, or names gen from phone research, etc. ???
 
A couple of things still concern me. Gerry Crispen wrote something on this also, a white paper here: http://www.shrm.org/hrresources/whitepapers_published/CMS_016203.asp#P-4_0

He presented examples and solutions, each well reasoned and thought out, of course. But contrary to at least one example in his white paper, we (at Freescale) would use technology to quickly scour all 1000 (in his example) to find the &#039;most&#039; qualified, not necessarily the &#039;first&#039; qualified to show up in the first batch of 100. So... 75 people out of the entire 1000 (e.g.) may be minimally qualified, but we would choose the best 5 - 10 as a short list. While doing this, we may network with the remaining for future things.

Do our Freescale internal rules - or at least our interpretation of them - properly reflect the OFCCP regulation? Or could we limit stuff to just contract openings with federal (Tier I Prime etc) vendors? Compliance would be literally impossible given the resources we now have available. That is, if we take the interpretations literally. We cannot capture and store every (ostensibly) qualified resume we stumble across in our internet searches. Between all of our recruiters we might see 100,000+ each year. We don&#039;t have the warehouse or staff to input all of it; and in fact doing so might well violate an &#039;applicant&#039;s&#039; copyrights and/or privacy or whatever.

Yet many feel the &#039;applicant&#039; threshold is crossed if we even glance at a resume we?ve spotted using search engines or bots. 

But after the hype, the rule clearly requires a job seeker. 

www.dictionary.com defines a seeker as: &#039;n 1: someone making a search or inquiry...&#039;

An applicant is someone who seeks us out, not us them. Yet some interpretations say, &#039;An individual?s posting of a resume on a commercial resume database is generally sufficient to satisfy the &#039;expression of interest&#039; requirement; this includes googling for resumes.&#039;

An &#039;applicant&#039; is: 

n : One that applies, as for a job.
n : a person who requests or seeks something such as assistance or employment or admission

Applying is a deliberate step taken by someone toward a specific THING that they are aware of: 

ap?ply    

v. ap?plied, ap?ply?ing, ap?plies 
1. To bring into nearness or contact with someTHING (allcaps mine)
?
4. To devote (oneself or one&#039;s efforts) to someTHING
v. intr.
...
2. To request or seek assistance, employment, or admission: applied for unemployment benefits; will apply to college next year. See Synonyms at resort.?
So by definition Freescale interpretation is off.

I would also say the (internal) rules of companies I&#039;ve seen bar this interpretation: &#039;Note: An individual is not an &#039;internet applicant&#039; unless all four criteria are satisfied.&#039; etc.

The ?four criteria&#039; I always see presented are a watered down version of 41 CFR 60-1.3. This CFR clearly establishes the context of a two way connection between applicant and company: It requires an &#039;expression of interest&#039; initiated on the part of applicant, not employer. Going further, the regulation says IMHO that after an ?expression of interest? the interaction ?must be non-comparative, objective and relevant to performance in the particular position.&#039;  41 CFR 60-1.3(3). 

So, what is required is a mutual, expressed interest between company and person about a specific position, initiated by the applicant. Applicant&#039;s only way of expressing to company, as far as I can tell, is to apply directly to a job posting and/or contact the company. Only then can it &#039;consider&#039; applicant and raise interaction to the level of the mutual exchange contemplated in the CFR.  Within the clear words of 41 CFR 60-1.3, we have no connection whatsoever with people who have not engaged us with a qualified expression of interest on a specific opening.

Finally, there is a clear difference between people companies run across doing a Google (or other non-board) search v. those who post their resumes on Monster et al.

Search engines index resume homepages and such. The people found in those databases don&#039;t ask to be put there. They are not ?applying? for anything. By comparison, we cannot reasonably say that someone who posts their resume on a roadside billboard in Michigan is made an &#039;applicant&#039; by the mere hope that some anonymous trucker will snap a picture of the resume and drive it somewhere. More specifically, does this &#039;applicant&#039; know for a fact that some heretofore unknowing trucker driving to Texas will snap a picture of the billboard and hand deliver it to a company recruiter? who will then ?consider? and maybe present the person against an opening that the transporting trucker is probably not aware of? ???

Someone who posts to Monster (on the other hand) is arguably closer to &#039;applying&#039; than someone Google just happens to snag. But these people are not applicants. They&#039;ve not initiated contact with the company to apply for specific positions for which they qualify. 
And because Monster gives people tools to &#039;apply&#039; to specific, open positions at companies they seek out, someone (IMHO) who does not use these tools to apply does so for a reason; there is no applicant initiated ?expression of interest? that is ?relevant to performance in the particular position.? Thus they cannot be considered an applicant. They&#039;re sort of in their own category; maybe &#039;Postant&#039; or something but as yet that word doesn?t exist in our lexicon. 

Okay, that&#039;s my minor opinion dying view and that&#039;s all I have to say about that.

Best regards,
Paul

Paul Westmoreland
Global Strategist
Freescale Talent Sourcing
www.freescale.com
7700 West Parmer Lane
Austin, Texas 78729
512.996.4362 (W)
512.964.6049 (C)
paul.westmoreland@freescale.com
 
 
This e-mail, and any associated attachments have been classified as:
[x] Freescale Semiconductor General Business
[ ] Freescale Semiconductor Internal Use Only
[ ] Freescale Semiconductor Confidential Proprietary

PS I am not a lawyer, but I think that anyone who posts a resume on Monster, or any of the other boards, would have a hard time supporting any claim under Title VII arising from the posting and response. Has anyone ever filed a supportable and successful claim for discrimination based on an unsolicited approach from a company? I would challenge legal at any company (even the most clever ones) to find an instance of this anywhere in Western law, unless the recruiting conversation went reasonably past the point of first approach by the company. The last thing we need is government to team with legal to tell us how to recruit when we are stretched so thin already.

IMHO</description>
		<content:encoded><![CDATA[<p>&#8216;Love That Hat&#8217;<br />
mmm&#8230; ahhgree. but so anyhow, the article rawks too. </p>
<p>What I find healing is this: &#8216;If the activities are focused on building a talent pipeline and not filling a specific position, the search activity does not need to be logged.&#8217;</p>
<p>M&#8217;kay. Okay so I don&#8217;t like what most people &#8211; including experts in our trade whom I respect &#8211; have written about this thing.</p>
<p>Long and short, that With both passive and active candidates, no matter the source or method, we only record those who respond to our queries and are qualified. As long as we do it consistently. Yes? No? Whether in response to postings, searches of internal/external databases, general web searches, or names gen from phone research, etc. ???</p>
<p>A couple of things still concern me. Gerry Crispen wrote something on this also, a white paper here: <a href="http://www.shrm.org/hrresources/whitepapers_published/CMS_016203.asp#P-4_0" rel="nofollow">http://www.shrm.org/hrresources/whitepapers_published/CMS_016203.asp#P-4_0</a></p>
<p>He presented examples and solutions, each well reasoned and thought out, of course. But contrary to at least one example in his white paper, we (at Freescale) would use technology to quickly scour all 1000 (in his example) to find the &#8216;most&#8217; qualified, not necessarily the &#8216;first&#8217; qualified to show up in the first batch of 100. So&#8230; 75 people out of the entire 1000 (e.g.) may be minimally qualified, but we would choose the best 5 &#8211; 10 as a short list. While doing this, we may network with the remaining for future things.</p>
<p>Do our Freescale internal rules &#8211; or at least our interpretation of them &#8211; properly reflect the OFCCP regulation? Or could we limit stuff to just contract openings with federal (Tier I Prime etc) vendors? Compliance would be literally impossible given the resources we now have available. That is, if we take the interpretations literally. We cannot capture and store every (ostensibly) qualified resume we stumble across in our internet searches. Between all of our recruiters we might see 100,000+ each year. We don&#8217;t have the warehouse or staff to input all of it; and in fact doing so might well violate an &#8216;applicant&#8217;s&#8217; copyrights and/or privacy or whatever.</p>
<p>Yet many feel the &#8216;applicant&#8217; threshold is crossed if we even glance at a resume we?ve spotted using search engines or bots. </p>
<p>But after the hype, the rule clearly requires a job seeker. </p>
<p><a href="http://www.dictionary.com" rel="nofollow">http://www.dictionary.com</a> defines a seeker as: &#8216;n 1: someone making a search or inquiry&#8230;&#8217;</p>
<p>An applicant is someone who seeks us out, not us them. Yet some interpretations say, &#8216;An individual?s posting of a resume on a commercial resume database is generally sufficient to satisfy the &#8216;expression of interest&#8217; requirement; this includes googling for resumes.&#8217;</p>
<p>An &#8216;applicant&#8217; is: </p>
<p>n : One that applies, as for a job.<br />
n : a person who requests or seeks something such as assistance or employment or admission</p>
<p>Applying is a deliberate step taken by someone toward a specific THING that they are aware of: </p>
<p>ap?ply    </p>
<p>v. ap?plied, ap?ply?ing, ap?plies<br />
1. To bring into nearness or contact with someTHING (allcaps mine)<br />
?<br />
4. To devote (oneself or one&#8217;s efforts) to someTHING<br />
v. intr.<br />
&#8230;<br />
2. To request or seek assistance, employment, or admission: applied for unemployment benefits; will apply to college next year. See Synonyms at resort.?<br />
So by definition Freescale interpretation is off.</p>
<p>I would also say the (internal) rules of companies I&#8217;ve seen bar this interpretation: &#8216;Note: An individual is not an &#8216;internet applicant&#8217; unless all four criteria are satisfied.&#8217; etc.</p>
<p>The ?four criteria&#8217; I always see presented are a watered down version of 41 CFR 60-1.3. This CFR clearly establishes the context of a two way connection between applicant and company: It requires an &#8216;expression of interest&#8217; initiated on the part of applicant, not employer. Going further, the regulation says IMHO that after an ?expression of interest? the interaction ?must be non-comparative, objective and relevant to performance in the particular position.&#8217;  41 CFR 60-1.3(3). </p>
<p>So, what is required is a mutual, expressed interest between company and person about a specific position, initiated by the applicant. Applicant&#8217;s only way of expressing to company, as far as I can tell, is to apply directly to a job posting and/or contact the company. Only then can it &#8216;consider&#8217; applicant and raise interaction to the level of the mutual exchange contemplated in the CFR.  Within the clear words of 41 CFR 60-1.3, we have no connection whatsoever with people who have not engaged us with a qualified expression of interest on a specific opening.</p>
<p>Finally, there is a clear difference between people companies run across doing a Google (or other non-board) search v. those who post their resumes on Monster et al.</p>
<p>Search engines index resume homepages and such. The people found in those databases don&#8217;t ask to be put there. They are not ?applying? for anything. By comparison, we cannot reasonably say that someone who posts their resume on a roadside billboard in Michigan is made an &#8216;applicant&#8217; by the mere hope that some anonymous trucker will snap a picture of the resume and drive it somewhere. More specifically, does this &#8216;applicant&#8217; know for a fact that some heretofore unknowing trucker driving to Texas will snap a picture of the billboard and hand deliver it to a company recruiter? who will then ?consider? and maybe present the person against an opening that the transporting trucker is probably not aware of? ???</p>
<p>Someone who posts to Monster (on the other hand) is arguably closer to &#8216;applying&#8217; than someone Google just happens to snag. But these people are not applicants. They&#8217;ve not initiated contact with the company to apply for specific positions for which they qualify.<br />
And because Monster gives people tools to &#8216;apply&#8217; to specific, open positions at companies they seek out, someone (IMHO) who does not use these tools to apply does so for a reason; there is no applicant initiated ?expression of interest? that is ?relevant to performance in the particular position.? Thus they cannot be considered an applicant. They&#8217;re sort of in their own category; maybe &#8216;Postant&#8217; or something but as yet that word doesn?t exist in our lexicon. </p>
<p>Okay, that&#8217;s my minor opinion dying view and that&#8217;s all I have to say about that.</p>
<p>Best regards,<br />
Paul</p>
<p>Paul Westmoreland<br />
Global Strategist<br />
Freescale Talent Sourcing<br />
<a href="http://www.freescale.com" rel="nofollow">http://www.freescale.com</a><br />
7700 West Parmer Lane<br />
Austin, Texas 78729<br />
512.996.4362 (W)<br />
512.964.6049 (C)<br />
<a href="mailto:paul.westmoreland@freescale.com">paul.westmoreland@freescale.com</a></p>
<p>This e-mail, and any associated attachments have been classified as:<br />
[x] Freescale Semiconductor General Business<br />
[ ] Freescale Semiconductor Internal Use Only<br />
[ ] Freescale Semiconductor Confidential Proprietary</p>
<p>PS I am not a lawyer, but I think that anyone who posts a resume on Monster, or any of the other boards, would have a hard time supporting any claim under Title VII arising from the posting and response. Has anyone ever filed a supportable and successful claim for discrimination based on an unsolicited approach from a company? I would challenge legal at any company (even the most clever ones) to find an instance of this anywhere in Western law, unless the recruiting conversation went reasonably past the point of first approach by the company. The last thing we need is government to team with legal to tell us how to recruit when we are stretched so thin already.</p>
<p>IMHO</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Ebeling</title>
		<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/comment-page-1/#comment-4234</link>
		<dc:creator>Brandon Ebeling</dc:creator>
		<pubDate>Thu, 30 Mar 2006 06:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/#comment-4234</guid>
		<description>I&#039;m waiting for the Fedora [like my grandfather wore] to become stylish again...

On a more serious note, Robert Style NAPS council has recently chimed in on the issue. Maybe he and Lisa [other association?s council] could collaborate on a follow up piece regarding TPR [retained/contingency/temp/etc.] implications?</description>
		<content:encoded><![CDATA[<p>I&#8217;m waiting for the Fedora [like my grandfather wore] to become stylish again&#8230;</p>
<p>On a more serious note, Robert Style NAPS council has recently chimed in on the issue. Maybe he and Lisa [other association?s council] could collaborate on a follow up piece regarding TPR [retained/contingency/temp/etc.] implications?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Kent</title>
		<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/comment-page-1/#comment-4233</link>
		<dc:creator>Sean Kent</dc:creator>
		<pubDate>Thu, 30 Mar 2006 06:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/#comment-4233</guid>
		<description>Perhaps the most concise and direct explanation of key areas regarding the new OFCCP rules that I have read.  Great article - I will definitely forward this one on.</description>
		<content:encoded><![CDATA[<p>Perhaps the most concise and direct explanation of key areas regarding the new OFCCP rules that I have read.  Great article &#8211; I will definitely forward this one on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sherry Karr</title>
		<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/comment-page-1/#comment-4235</link>
		<dc:creator>Sherry Karr</dc:creator>
		<pubDate>Thu, 30 Mar 2006 03:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/#comment-4235</guid>
		<description>and the article.</description>
		<content:encoded><![CDATA[<p>and the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Howard Adamsky</title>
		<link>http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/comment-page-1/#comment-4232</link>
		<dc:creator>Howard Adamsky</dc:creator>
		<pubDate>Thu, 30 Mar 2006 02:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/2006/03/30/potholes-on-the-road-to-compliance-with-the-new-definition-of-an-internet-applicant/#comment-4232</guid>
		<description>Is that a great hat or what?

Howard Adamsky</description>
		<content:encoded><![CDATA[<p>Is that a great hat or what?</p>
<p>Howard Adamsky</p>
]]></content:encoded>
	</item>
</channel>
</rss>

