<?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 for Calm Water Business Partner, LLC</title>
	<atom:link href="http://www.calm-water.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.calm-water.com</link>
	<description>Professional Recruiting Services</description>
	<lastBuildDate>Thu, 05 Jan 2012 16:09:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on The First Ten Seconds by Mark H</title>
		<link>http://www.calm-water.com/the-first-ten-seconds/#comment-32</link>
		<dc:creator>Mark H</dc:creator>
		<pubDate>Thu, 05 Jan 2012 16:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.calm-water.com/?p=337#comment-32</guid>
		<description>Thanks for highlighting what I&#039;ll refer to as the &quot;Objective Trap&quot;... a pet peeve of mine for years as an HR professional from both the career counselling and recruiting point of view. In my experience, I&#039;ve found that objectives on a resume are either obvious (and therefore completely unnecessary) or wrong.  On the obvious front, is it necessary to take up space on a resume to state that your objective is to get the job you&#039;re applying for?  I assume that from the application itself!  And if the objective refers to a different role or industry than the open position, why would I hire someone who&#039;s resume indicates they&#039;d really rather do something else?  I&#039;m a proponent of getting rid of the objective altogether.  Include a summary of qualifications or core competencies that match the position&#039;s requirements on your resume and use the cover letter or interview process to state or clarify your true objective.</description>
		<content:encoded><![CDATA[<p>Thanks for highlighting what I&#8217;ll refer to as the &#8220;Objective Trap&#8221;&#8230; a pet peeve of mine for years as an HR professional from both the career counselling and recruiting point of view. In my experience, I&#8217;ve found that objectives on a resume are either obvious (and therefore completely unnecessary) or wrong.  On the obvious front, is it necessary to take up space on a resume to state that your objective is to get the job you&#8217;re applying for?  I assume that from the application itself!  And if the objective refers to a different role or industry than the open position, why would I hire someone who&#8217;s resume indicates they&#8217;d really rather do something else?  I&#8217;m a proponent of getting rid of the objective altogether.  Include a summary of qualifications or core competencies that match the position&#8217;s requirements on your resume and use the cover letter or interview process to state or clarify your true objective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Salary Requirement by Jason L</title>
		<link>http://www.calm-water.com/salary-requirement-2/#comment-4</link>
		<dc:creator>Jason L</dc:creator>
		<pubDate>Wed, 09 Nov 2011 15:45:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.calm-water.com/?p=161#comment-4</guid>
		<description>Great post, Nancy.  

The salary question has been the deciding factor in two of my offers in the past two months.  The first time it happened, I listed my expectations on the application (yes, management position and they wanted an application) the guy saw it and made comment of it during the interview.  I told him, &quot;Hey, you were honest enough to ask, I figured I ought to be straight with you.&quot;  He kind of laughed it off.  A week later, their offer was 2/3 of my asking salary.  That plus a few other factors resulted in me turning them down.</description>
		<content:encoded><![CDATA[<p>Great post, Nancy.  </p>
<p>The salary question has been the deciding factor in two of my offers in the past two months.  The first time it happened, I listed my expectations on the application (yes, management position and they wanted an application) the guy saw it and made comment of it during the interview.  I told him, &#8220;Hey, you were honest enough to ask, I figured I ought to be straight with you.&#8221;  He kind of laughed it off.  A week later, their offer was 2/3 of my asking salary.  That plus a few other factors resulted in me turning them down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Salary Requirement by Bill Ryan</title>
		<link>http://www.calm-water.com/salary-requirement-2/#comment-3</link>
		<dc:creator>Bill Ryan</dc:creator>
		<pubDate>Wed, 09 Nov 2011 12:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.calm-water.com/?p=161#comment-3</guid>
		<description>I advise client to research internal equity, i.e. industry salary standards for positions. With this economy and it&#039;s demands for lower costs internal equity may be headed downward. I believe that arming oneself with this information puts the job seeker in a better negotiating position.</description>
		<content:encoded><![CDATA[<p>I advise client to research internal equity, i.e. industry salary standards for positions. With this economy and it&#8217;s demands for lower costs internal equity may be headed downward. I believe that arming oneself with this information puts the job seeker in a better negotiating position.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.calm-water.com/comments/feed/ ) in 0.54459 seconds, on Feb 23rd, 2012 at 5:11 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 23rd, 2012 at 6:11 pm UTC -->
