<?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: Dice Offers Searchers Something Extra, Passive Candidates</title>
	<atom:link href="http://www.ere.net/2009/10/23/dice-offers-searchers-something-extra-passive-candidates/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ere.net/2009/10/23/dice-offers-searchers-something-extra-passive-candidates/</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: Dan Boersma</title>
		<link>http://www.ere.net/2009/10/23/dice-offers-searchers-something-extra-passive-candidates/comment-page-1/#comment-16263</link>
		<dc:creator>Dan Boersma</dc:creator>
		<pubDate>Mon, 26 Oct 2009 15:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=10467#comment-16263</guid>
		<description>I am having a tough time grasping the language used in this article describing a passive candidate.  A passive candidate is someone who is currently working but open for a better opportunity.  All I read is a spin on how old resumes in an old database with old contact information may be beneficial.  I hope Dice isn&#039;t charging for this as a premium feature. 

New technologies are on the market with the hope of finding the truly passive candidate.  Talentspring and JobVite are two examples.  While the features on these applications are good they still have to work within the parameters of their main candidate source LinkedIn.  LinkedIn is in no way an open search tool.  You have to play the LinkedIn game by building your network and joining groups to be able to contact certain users (but only through LinkedIn).  I like LinkedIn and I feel one of the best things about LinkedIn is it took the taboo away from having your job history searchable by calling it a profile.  However, $7K per corporate seat is a bit steep for most of us to have access to the users.

With Google&#039;s partnership with Twitter and Facebook&#039;s continuation of adding more job related content to their website these top social media sites will be the next generation of sourcing passive candidates.  An individual using sites such as ResuWe.com can tweet their resume to their Twitter contacts and have this information searchable on the open web.  ResuWe users are also able to have their Facebook friends make comments and recommendations on their resume. 

Having your resume available online is part of an individuals personal brand.  Gone are the days when an employee gets reprimanded for having their resume on Monster.  What we need to focus on is not old resumes in a database but educating everyone on how to fully integrate social media so their job information can be found by everyone at anytime...not just a corporation who can afford a user license.</description>
		<content:encoded><![CDATA[<p>I am having a tough time grasping the language used in this article describing a passive candidate.  A passive candidate is someone who is currently working but open for a better opportunity.  All I read is a spin on how old resumes in an old database with old contact information may be beneficial.  I hope Dice isn&#8217;t charging for this as a premium feature. </p>
<p>New technologies are on the market with the hope of finding the truly passive candidate.  Talentspring and JobVite are two examples.  While the features on these applications are good they still have to work within the parameters of their main candidate source LinkedIn.  LinkedIn is in no way an open search tool.  You have to play the LinkedIn game by building your network and joining groups to be able to contact certain users (but only through LinkedIn).  I like LinkedIn and I feel one of the best things about LinkedIn is it took the taboo away from having your job history searchable by calling it a profile.  However, $7K per corporate seat is a bit steep for most of us to have access to the users.</p>
<p>With Google&#8217;s partnership with Twitter and Facebook&#8217;s continuation of adding more job related content to their website these top social media sites will be the next generation of sourcing passive candidates.  An individual using sites such as ResuWe.com can tweet their resume to their Twitter contacts and have this information searchable on the open web.  ResuWe users are also able to have their Facebook friends make comments and recommendations on their resume. </p>
<p>Having your resume available online is part of an individuals personal brand.  Gone are the days when an employee gets reprimanded for having their resume on Monster.  What we need to focus on is not old resumes in a database but educating everyone on how to fully integrate social media so their job information can be found by everyone at anytime&#8230;not just a corporation who can afford a user license.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric shannon</title>
		<link>http://www.ere.net/2009/10/23/dice-offers-searchers-something-extra-passive-candidates/comment-page-1/#comment-16204</link>
		<dc:creator>eric shannon</dc:creator>
		<pubDate>Sat, 24 Oct 2009 15:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=10467#comment-16204</guid>
		<description>on LatPro.com we&#039;ve been doing something like dice.com since 2000 - we purge inactive resumes selectively to preserve access to high-value candidates, not so much for hiring as for research/sourcing...</description>
		<content:encoded><![CDATA[<p>on LatPro.com we&#8217;ve been doing something like dice.com since 2000 &#8211; we purge inactive resumes selectively to preserve access to high-value candidates, not so much for hiring as for research/sourcing&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

