<?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: Building the initial team for seed stage startups</title>
	<atom:link href="http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/feed/" rel="self" type="application/rss+xml" />
	<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/</link>
	<description>Essays on viral marketing, freemium, and social gaming</description>
	<lastBuildDate>Sun, 07 Mar 2010 15:07:14 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew Chen</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2131</link>
		<dc:creator>Andrew Chen</dc:creator>
		<pubDate>Tue, 15 Sep 2009 21:01:02 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2131</guid>
		<description>re: vital, fixed! Thanks for the catch.&lt;br&gt;&lt;br&gt;Yes, hiring people who are consultants/contractors have the advantage that you can &quot;try before you buy&quot; with the drawback that I&#039;ve found that people with those backgrounds are often very wide but shallow. More _ shaped than T ;-)&lt;br&gt;&lt;br&gt;We&#039;ve found one thing that works is having people fly in on a Friday and do a 3-day interview crossing into the weekend, and after 3 days, you have an amazing sense for that person&#039;s skillsets.</description>
		<content:encoded><![CDATA[<p>re: vital, fixed! Thanks for the catch.</p>
<p>Yes, hiring people who are consultants/contractors have the advantage that you can &#8220;try before you buy&#8221; with the drawback that I&#39;ve found that people with those backgrounds are often very wide but shallow. More _ shaped than T <img src='http://andrewchenblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>We&#39;ve found one thing that works is having people fly in on a Friday and do a 3-day interview crossing into the weekend, and after 3 days, you have an amazing sense for that person&#39;s skillsets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: facebook-509888148</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2128</link>
		<dc:creator>facebook-509888148</dc:creator>
		<pubDate>Tue, 15 Sep 2009 18:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2128</guid>
		<description>Andrew great insights &amp; points. We&#039;re at the point you described at TapSmack where we are building out the team and many of your points resonate with our thinking. Another critical point to consider is looking beyond a candidate&#039;s experience at brand name companies or universities and focus on their actual accomplishments. To reach the next level success, it&#039;s important to find team members who are in it for the long haul and are scrappy enough to get it done when the going gets tough. Sometimes it simply means hiring the &quot;hungrier&quot; candidate.</description>
		<content:encoded><![CDATA[<p>Andrew great insights &#038; points. We&#39;re at the point you described at TapSmack where we are building out the team and many of your points resonate with our thinking. Another critical point to consider is looking beyond a candidate&#39;s experience at brand name companies or universities and focus on their actual accomplishments. To reach the next level success, it&#39;s important to find team members who are in it for the long haul and are scrappy enough to get it done when the going gets tough. Sometimes it simply means hiring the &#8220;hungrier&#8221; candidate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikiscevak</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2123</link>
		<dc:creator>nikiscevak</dc:creator>
		<pubDate>Mon, 14 Sep 2009 23:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2123</guid>
		<description>Excellent thoughts once again Andrew. I truly believe (like you) that nearly all of the resume pimping and multi-stage interviews are all pomp and circumstance.&lt;br&gt;&lt;br&gt;One of the greatest things about oDesk et al is the ease in which you can do the &#039;working interviews&#039; and scale from 1 day to 5 day to 3  months to valued full time employee. Sure there are a lot of downsides as well, but this fact nets all of them off and then some.&lt;br&gt;&lt;br&gt;Also, I know you&#039;ve been writing this blog (or working in viral marketing/metrics) too long when you write &quot;the depth gives them a source of knowledge that makes them viral to the team.&quot;&lt;br&gt;&lt;br&gt;Shouldn&#039;t that be &#039;vital&#039; instead of &#039;viral&#039;. I am not sure you want a team member going all &#039;viral&#039; on everybody else :)</description>
		<content:encoded><![CDATA[<p>Excellent thoughts once again Andrew. I truly believe (like you) that nearly all of the resume pimping and multi-stage interviews are all pomp and circumstance.</p>
<p>One of the greatest things about oDesk et al is the ease in which you can do the &#39;working interviews&#39; and scale from 1 day to 5 day to 3  months to valued full time employee. Sure there are a lot of downsides as well, but this fact nets all of them off and then some.</p>
<p>Also, I know you&#39;ve been writing this blog (or working in viral marketing/metrics) too long when you write &#8220;the depth gives them a source of knowledge that makes them viral to the team.&#8221;</p>
<p>Shouldn&#39;t that be &#39;vital&#39; instead of &#39;viral&#39;. I am not sure you want a team member going all &#39;viral&#39; on everybody else <img src='http://andrewchenblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DGentry</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2122</link>
		<dc:creator>DGentry</dc:creator>
		<pubDate>Mon, 14 Sep 2009 22:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2122</guid>
		<description>One painful lesson: in startups personality actually matters more than contributions. If the person is producing, but is absolutely toxic to the morale of the rest of the team, you need to part ways. No-one is so indispensable as to be allowed to destroy the rest of the team.&lt;br&gt;&lt;br&gt;Unfortunately this trait is often well hidden during a typical interview, and only appears later.</description>
		<content:encoded><![CDATA[<p>One painful lesson: in startups personality actually matters more than contributions. If the person is producing, but is absolutely toxic to the morale of the rest of the team, you need to part ways. No-one is so indispensable as to be allowed to destroy the rest of the team.</p>
<p>Unfortunately this trait is often well hidden during a typical interview, and only appears later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nacho Gutierrez</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2121</link>
		<dc:creator>Nacho Gutierrez</dc:creator>
		<pubDate>Mon, 14 Sep 2009 19:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2121</guid>
		<description>Hi Andrew!  Excellent post as usual!&lt;br&gt;&lt;br&gt;I am involved in a social network startup with the freemium model and I wanted to ask you where can i find social network historical data or statistics like virality or free to premium conversion, to backup my business plan data!&lt;br&gt;&lt;br&gt;Thanks for all your essays! &lt;br&gt;&lt;br&gt;Ignacio</description>
		<content:encoded><![CDATA[<p>Hi Andrew!  Excellent post as usual!</p>
<p>I am involved in a social network startup with the freemium model and I wanted to ask you where can i find social network historical data or statistics like virality or free to premium conversion, to backup my business plan data!</p>
<p>Thanks for all your essays! </p>
<p>Ignacio</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Gries</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2120</link>
		<dc:creator>Adam Gries</dc:creator>
		<pubDate>Mon, 14 Sep 2009 17:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2120</guid>
		<description>great post and comment thanks!</description>
		<content:encoded><![CDATA[<p>great post and comment thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Mitchell</title>
		<link>http://andrewchenblog.com/2009/09/14/building-the-initial-team-for-seed-stage-startups/comment-page-1/#comment-2119</link>
		<dc:creator>Bill Mitchell</dc:creator>
		<pubDate>Mon, 14 Sep 2009 15:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://andrewchenblog.com/?p=1196#comment-2119</guid>
		<description>Suggestions:&lt;br&gt;&lt;br&gt;1.  Hire people who already do the job as a hobby.  This is a silver bullet.  At Firepad, we mostly hired coders who had shipped their own PalmOS shareware.  They were easy to find, knew the API, but more critically, they had proven motivation completely finish Palm software apps, without any oversight or schedule pressure.&lt;br&gt;&lt;br&gt;2.   Read at least 10 resumes for every interview;  interview at least 10 for every hire.  It&#039;s a numbers game.  You need volume, but have limited time.  Face time is costly.  Narrow the field.&lt;br&gt;&lt;br&gt;3.  Use an intern to take a first cut at resumes.  For each job, define features to look for, and have them present you with the winners.  Then you have a stronger pool on which to execute #2 above.&lt;br&gt;&lt;br&gt;4.   Interviews:  rate candidates on a scale of 1 to 3 for motivation, integrity and ability.  No fractions -- if they aren&#039;t a 3, then they are a 2.  Any candidate scoring a 1 is rejected.  Any candidate with more than one 2 is rejected.  The very structure of this system forces hard judgment calls to be made quickly.&lt;br&gt; &lt;br&gt;5.   Hire someone just for a day.  If they perform, they get the job.  If not, you pay for their time and show them the door.  Interviews are essentially hypothetical, while a one-day contractor shows you plenty.  This requires a slack labor market (e.g. 2002).&lt;br&gt;&lt;br&gt;6.  Either fire your new hire within 2 weeks, or never.  Why only 2 weeks?  First because, if they aren&#039;t great then, while on best behavior, then they never will be.  Second because, if you fire later, after friendships have formed, the whole company will suffer bad feelings.  Hesitating to reverse a mistake is probably the most common, yet most destructive, hiring error.&lt;br&gt;&lt;br&gt;Credit where due:  learned #4  and #5 from other sharp software company founders.</description>
		<content:encoded><![CDATA[<p>Suggestions:</p>
<p>1.  Hire people who already do the job as a hobby.  This is a silver bullet.  At Firepad, we mostly hired coders who had shipped their own PalmOS shareware.  They were easy to find, knew the API, but more critically, they had proven motivation completely finish Palm software apps, without any oversight or schedule pressure.</p>
<p>2.   Read at least 10 resumes for every interview;  interview at least 10 for every hire.  It&#39;s a numbers game.  You need volume, but have limited time.  Face time is costly.  Narrow the field.</p>
<p>3.  Use an intern to take a first cut at resumes.  For each job, define features to look for, and have them present you with the winners.  Then you have a stronger pool on which to execute #2 above.</p>
<p>4.   Interviews:  rate candidates on a scale of 1 to 3 for motivation, integrity and ability.  No fractions &#8212; if they aren&#39;t a 3, then they are a 2.  Any candidate scoring a 1 is rejected.  Any candidate with more than one 2 is rejected.  The very structure of this system forces hard judgment calls to be made quickly.</p>
<p>5.   Hire someone just for a day.  If they perform, they get the job.  If not, you pay for their time and show them the door.  Interviews are essentially hypothetical, while a one-day contractor shows you plenty.  This requires a slack labor market (e.g. 2002).</p>
<p>6.  Either fire your new hire within 2 weeks, or never.  Why only 2 weeks?  First because, if they aren&#39;t great then, while on best behavior, then they never will be.  Second because, if you fire later, after friendships have formed, the whole company will suffer bad feelings.  Hesitating to reverse a mistake is probably the most common, yet most destructive, hiring error.</p>
<p>Credit where due:  learned #4  and #5 from other sharp software company founders.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
