<?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: Is the Resume Dead? by Personal Branding Strategist Jean Cummings</title>
	<atom:link href="http://www.personalbranding.tv/is-the-resume-dead-by-personal-branding-strategist-jean-cummings/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.personalbranding.tv/is-the-resume-dead-by-personal-branding-strategist-jean-cummings/</link>
	<description>Tips and Techniques for Building the Brand of You</description>
	<lastBuildDate>Wed, 08 Feb 2012 21:42:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jean Cummings</title>
		<link>http://www.personalbranding.tv/is-the-resume-dead-by-personal-branding-strategist-jean-cummings/comment-page-1/#comment-688</link>
		<dc:creator>Jean Cummings</dc:creator>
		<pubDate>Wed, 03 Nov 2010 20:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.personalbranding.tv/?p=1879#comment-688</guid>
		<description>Hey, Paul, great to hear from you! The resume is even now taking a back seat to LinkedIn profiles and other online content - at least for a first pass as recruiters and hiring managers decide whether they want to pursue a candidate further. 

I do think a Web portal in the form of a blogsite would be a much more dynamic way to experience a potential hire than a resume (if feasible for everyone) - with home page content, executive bio, critical leadership initiatives, project profiles, endorsements, press clippings, graphs, video etc. But, as an executive resume writer, I also am a believer in the power of a 2-page doc to communicate value prop, brand, and history. If it&#039;s easily scannable by the eye - it can do the job fast, cleanly - and - all by itself! 

How do you see the future of job search marketing communications? I&#039;d love to hear -</description>
		<content:encoded><![CDATA[<p>Hey, Paul, great to hear from you! The resume is even now taking a back seat to LinkedIn profiles and other online content &#8211; at least for a first pass as recruiters and hiring managers decide whether they want to pursue a candidate further. </p>
<p>I do think a Web portal in the form of a blogsite would be a much more dynamic way to experience a potential hire than a resume (if feasible for everyone) &#8211; with home page content, executive bio, critical leadership initiatives, project profiles, endorsements, press clippings, graphs, video etc. But, as an executive resume writer, I also am a believer in the power of a 2-page doc to communicate value prop, brand, and history. If it&#8217;s easily scannable by the eye &#8211; it can do the job fast, cleanly &#8211; and &#8211; all by itself! </p>
<p>How do you see the future of job search marketing communications? I&#8217;d love to hear -</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Copcutt - Square Peg</title>
		<link>http://www.personalbranding.tv/is-the-resume-dead-by-personal-branding-strategist-jean-cummings/comment-page-1/#comment-502</link>
		<dc:creator>Paul Copcutt - Square Peg</dc:creator>
		<pubDate>Fri, 16 Jul 2010 13:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.personalbranding.tv/?p=1879#comment-502</guid>
		<description>Jean great to see the visual representation of your personal brand and some very important points about the resume - eventually I feel it will not exist but for now your tips are great ways to make it survive for now. Just my toonies worth.</description>
		<content:encoded><![CDATA[<p>Jean great to see the visual representation of your personal brand and some very important points about the resume &#8211; eventually I feel it will not exist but for now your tips are great ways to make it survive for now. Just my toonies worth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

