<?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: How to Improve Hiring at Startups</title>
	<atom:link href="http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/</link>
	<description>Entrepreneur turned VC</description>
	<lastBuildDate>Mon, 14 Nov 2011 23:37:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: William</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-12860</link>
		<dc:creator>William</dc:creator>
		<pubDate>Sun, 04 Apr 2010 20:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-12860</guid>
		<description>Excellent post. Two other things that are important for me:&lt;br&gt;&lt;br&gt;I will always pepper them with questions about topics they should know something about, but where it&#039;s impossible to know everything. I&#039;ll then dig into one of their responses, seeing how deep their knowledge goes. This is partly to judge smarts and experience, but mainly to tell what happens when they don&#039;t know something. If they can&#039;t comfortably say, &quot;I don&#039;t know,&quot; then I never hire them.&lt;br&gt;&lt;br&gt;The other is to, if possible, make them do some actual work. For developers, my last step is a 3-hour pair programming session working on some toy problem that I use on all the final candidates. This not only lets you eliminate the bluffers, but it lets you find the occasional rock star with poor self-promotion skills.</description>
		<content:encoded><![CDATA[<p>Excellent post. Two other things that are important for me:</p>
<p>I will always pepper them with questions about topics they should know something about, but where it&#39;s impossible to know everything. I&#39;ll then dig into one of their responses, seeing how deep their knowledge goes. This is partly to judge smarts and experience, but mainly to tell what happens when they don&#39;t know something. If they can&#39;t comfortably say, &#8220;I don&#39;t know,&#8221; then I never hire them.</p>
<p>The other is to, if possible, make them do some actual work. For developers, my last step is a 3-hour pair programming session working on some toy problem that I use on all the final candidates. This not only lets you eliminate the bluffers, but it lets you find the occasional rock star with poor self-promotion skills.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-5628</link>
		<dc:creator>William</dc:creator>
		<pubDate>Sun, 04 Apr 2010 20:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-5628</guid>
		<description>Excellent post. Two other things that are important for me:&lt;br&gt;&lt;br&gt;I will always pepper them with questions about topics they should know something about, but where it&#039;s impossible to know everything. I&#039;ll then dig into one of their responses, seeing how deep their knowledge goes. This is partly to judge smarts and experience, but mainly to tell what happens when they don&#039;t know something. If they can&#039;t comfortably say, &quot;I don&#039;t know,&quot; then I never hire them.&lt;br&gt;&lt;br&gt;The other is to, if possible, make them do some actual work. For developers, my last step is a 3-hour pair programming session working on some toy problem that I use on all the final candidates. This not only lets you eliminate the bluffers, but it lets you find the occasional rock star with poor self-promotion skills.</description>
		<content:encoded><![CDATA[<p>Excellent post. Two other things that are important for me:</p>
<p>I will always pepper them with questions about topics they should know something about, but where it&#39;s impossible to know everything. I&#39;ll then dig into one of their responses, seeing how deep their knowledge goes. This is partly to judge smarts and experience, but mainly to tell what happens when they don&#39;t know something. If they can&#39;t comfortably say, &#8220;I don&#39;t know,&#8221; then I never hire them.</p>
<p>The other is to, if possible, make them do some actual work. For developers, my last step is a 3-hour pair programming session working on some toy problem that I use on all the final candidates. This not only lets you eliminate the bluffers, but it lets you find the occasional rock star with poor self-promotion skills.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-5627</link>
		<dc:creator>William</dc:creator>
		<pubDate>Sun, 04 Apr 2010 15:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-5627</guid>
		<description>Excellent post. Two other things that are important for me:&lt;br&gt;&lt;br&gt;I will always pepper them with questions about topics they should know something about, but where it&#039;s impossible to know everything. I&#039;ll then dig into one of their responses, seeing how deep their knowledge goes. This is partly to judge smarts and experience, but mainly to tell what happens when they don&#039;t know something. If they can&#039;t comfortably say, &quot;I don&#039;t know,&quot; then I never hire them.&lt;br&gt;&lt;br&gt;The other is to, if possible, make them do some actual work. For developers, my last step is a 3-hour pair programming session working on some toy problem that I use on all the final candidates. This not only lets you eliminate the bluffers, but it lets you find the occasional rock star with poor self-promotion skills.</description>
		<content:encoded><![CDATA[<p>Excellent post. Two other things that are important for me:</p>
<p>I will always pepper them with questions about topics they should know something about, but where it&#39;s impossible to know everything. I&#39;ll then dig into one of their responses, seeing how deep their knowledge goes. This is partly to judge smarts and experience, but mainly to tell what happens when they don&#39;t know something. If they can&#39;t comfortably say, &#8220;I don&#39;t know,&#8221; then I never hire them.</p>
<p>The other is to, if possible, make them do some actual work. For developers, my last step is a 3-hour pair programming session working on some toy problem that I use on all the final candidates. This not only lets you eliminate the bluffers, but it lets you find the occasional rock star with poor self-promotion skills.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Morelock</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-12904</link>
		<dc:creator>Phillip Morelock</dc:creator>
		<pubDate>Thu, 01 Apr 2010 04:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-12904</guid>
		<description>I absolutely agree.  Hiring is the beginning of a relationship, and you don&#039;t want to have other people negotiate and position on your behalf at the beginning of your relationship. Take the time to guide the candidate, make the offer yourself, and close the deal all the way to start day.  It pays off.&lt;br&gt;&lt;br&gt;I&#039;ve had more than one &quot;turf&quot; fight with recruiters / HR about this point, but it absolutely matters.</description>
		<content:encoded><![CDATA[<p>I absolutely agree.  Hiring is the beginning of a relationship, and you don&#39;t want to have other people negotiate and position on your behalf at the beginning of your relationship. Take the time to guide the candidate, make the offer yourself, and close the deal all the way to start day.  It pays off.</p>
<p>I&#39;ve had more than one &#8220;turf&#8221; fight with recruiters / HR about this point, but it absolutely matters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Morelock</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-12915</link>
		<dc:creator>Phillip Morelock</dc:creator>
		<pubDate>Thu, 01 Apr 2010 04:55:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-12915</guid>
		<description>I like the thought here, but the &quot;big-company-trained-HR&quot; meter in my head is going off.  What if you meet the wife/husband and that ends up being the reason you don&#039;t hire the candidate?  Is this legal?  Is it appropriate?  And, considering I always try to be really frank with people who make it far in the process but don&#039;t get the job -- what do you tell them??&lt;br&gt;&lt;br&gt;This is very interesting and I admit this angle is something I never would have considered.  Would appreciate guidance on the sticky legal/personal front.</description>
		<content:encoded><![CDATA[<p>I like the thought here, but the &#8220;big-company-trained-HR&#8221; meter in my head is going off.  What if you meet the wife/husband and that ends up being the reason you don&#39;t hire the candidate?  Is this legal?  Is it appropriate?  And, considering I always try to be really frank with people who make it far in the process but don&#39;t get the job &#8212; what do you tell them??</p>
<p>This is very interesting and I admit this angle is something I never would have considered.  Would appreciate guidance on the sticky legal/personal front.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Morelock</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-5625</link>
		<dc:creator>Phillip Morelock</dc:creator>
		<pubDate>Wed, 31 Mar 2010 23:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-5625</guid>
		<description>I absolutely agree.  Hiring is the beginning of a relationship, and you don&#039;t want to have other people negotiate and position on your behalf at the beginning of your relationship. Take the time to guide the candidate, make the offer yourself, and close the deal all the way to start day.  It pays off.&lt;br&gt;&lt;br&gt;I&#039;ve had more than one &quot;turf&quot; fight with recruiters / HR about this point, but it absolutely matters.</description>
		<content:encoded><![CDATA[<p>I absolutely agree.  Hiring is the beginning of a relationship, and you don&#39;t want to have other people negotiate and position on your behalf at the beginning of your relationship. Take the time to guide the candidate, make the offer yourself, and close the deal all the way to start day.  It pays off.</p>
<p>I&#39;ve had more than one &#8220;turf&#8221; fight with recruiters / HR about this point, but it absolutely matters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Morelock</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-5626</link>
		<dc:creator>Phillip Morelock</dc:creator>
		<pubDate>Wed, 31 Mar 2010 23:55:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-5626</guid>
		<description>I like the thought here, but the &quot;big-company-trained-HR&quot; meter in my head is going off.  What if you meet the wife/husband and that ends up being the reason you don&#039;t hire the candidate?  Is this legal?  Is it appropriate?  And, considering I always try to be really frank with people who make it far in the process but don&#039;t get the job -- what do you tell them??&lt;br&gt;&lt;br&gt;This is very interesting and I admit this angle is something I never would have considered.  Would appreciate guidance on the sticky legal/personal front.</description>
		<content:encoded><![CDATA[<p>I like the thought here, but the &#8220;big-company-trained-HR&#8221; meter in my head is going off.  What if you meet the wife/husband and that ends up being the reason you don&#39;t hire the candidate?  Is this legal?  Is it appropriate?  And, considering I always try to be really frank with people who make it far in the process but don&#39;t get the job &#8212; what do you tell them??</p>
<p>This is very interesting and I admit this angle is something I never would have considered.  Would appreciate guidance on the sticky legal/personal front.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philsugar</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-12861</link>
		<dc:creator>philsugar</dc:creator>
		<pubDate>Mon, 29 Mar 2010 18:20:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-12861</guid>
		<description>The only thing I expect to get out of a reference is a referral to another reference.....second level references really show the true picture.&lt;br&gt;&lt;br&gt;Totally agree about the process (why piss people off) and the deep dive (amazing how many people will take credit for something but not be able to remember the gory details)</description>
		<content:encoded><![CDATA[<p>The only thing I expect to get out of a reference is a referral to another reference&#8230;..second level references really show the true picture.</p>
<p>Totally agree about the process (why piss people off) and the deep dive (amazing how many people will take credit for something but not be able to remember the gory details)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philsugar</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-5624</link>
		<dc:creator>philsugar</dc:creator>
		<pubDate>Mon, 29 Mar 2010 13:20:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-5624</guid>
		<description>The only thing I expect to get out of a reference is a referral to another reference.....second level references really show the true picture.&lt;br&gt;&lt;br&gt;Totally agree about the process (why piss people off) and the deep dive (amazing how many people will take credit for something but not be able to remember the gory details)</description>
		<content:encoded><![CDATA[<p>The only thing I expect to get out of a reference is a referral to another reference&#8230;..second level references really show the true picture.</p>
<p>Totally agree about the process (why piss people off) and the deep dive (amazing how many people will take credit for something but not be able to remember the gory details)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ravi Kannan</title>
		<link>http://www.bothsidesofthetable.com/2010/03/27/how-to-improve-hiring-at-startups/comment-page-2/#comment-12876</link>
		<dc:creator>Ravi Kannan</dc:creator>
		<pubDate>Mon, 29 Mar 2010 11:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bothsidesofthetable.com/?p=2223#comment-12876</guid>
		<description>Thanks Mark. Will like to ping you with details and get your thoughts. Can I?</description>
		<content:encoded><![CDATA[<p>Thanks Mark. Will like to ping you with details and get your thoughts. Can I?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

