<?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: Hiring Developers &#8211; not just about the code</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/08/10/hiring-developers-not-just-about-the-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/08/10/hiring-developers-not-just-about-the-code/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/08/10/hiring-developers-not-just-about-the-code/comment-page-1/#comment-11</link>
		<dc:creator>Mark Needham</dc:creator>
		<pubDate>Sun, 10 Aug 2008 20:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=49#comment-11</guid>
		<description>Re: group interview sessions

Certainly do that in the UK for the TWU recruitment process. I&#039;m not sure whether it&#039;s done for lateral hires or not. I did do some pairing interviews when I was in Australia, not sure if that&#039;s still done in the UK.

I think that&#039;s a good point you make about putting the effort into the code review being a fair indicator of whether they will excel at their profession.</description>
		<content:encoded><![CDATA[<p>Re: group interview sessions</p>
<p>Certainly do that in the UK for the TWU recruitment process. I&#8217;m not sure whether it&#8217;s done for lateral hires or not. I did do some pairing interviews when I was in Australia, not sure if that&#8217;s still done in the UK.</p>
<p>I think that&#8217;s a good point you make about putting the effort into the code review being a fair indicator of whether they will excel at their profession.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Kemper</title>
		<link>http://www.markhneedham.com/blog/2008/08/10/hiring-developers-not-just-about-the-code/comment-page-1/#comment-10</link>
		<dc:creator>Kris Kemper</dc:creator>
		<pubDate>Sun, 10 Aug 2008 18:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=49#comment-10</guid>
		<description>Oh, and on the point of toxicity - I would agree with that. I&#039;ve heard that in the Thoughtworks UK office, they have group interview sessions where people have to work together to solve a problem. I love this idea as well, as it should help identify toxic individuals.</description>
		<content:encoded><![CDATA[<p>Oh, and on the point of toxicity &#8211; I would agree with that. I&#8217;ve heard that in the Thoughtworks UK office, they have group interview sessions where people have to work together to solve a problem. I love this idea as well, as it should help identify toxic individuals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Kemper</title>
		<link>http://www.markhneedham.com/blog/2008/08/10/hiring-developers-not-just-about-the-code/comment-page-1/#comment-9</link>
		<dc:creator>Kris Kemper</dc:creator>
		<pubDate>Sun, 10 Aug 2008 18:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=49#comment-9</guid>
		<description>Perhaps I was overly focused on the code submission in my post - there are certainly other aspects of the process around getting a great candidate. 

However, I still think that having a code submission be a &quot;gate&quot; in the process is important - immediately eliminating the ones that do not have the initial skill level.

Even outside of skill level, you can often tell how much effort someone puts into the code submission, so regardless of whether they make technical mistakes, you can tell whether they really tried in the first place. I find this to a be a reflection on hard they will try to excel at their profession, and grow as an individual.

Certainly, if any company can identify people who are lacking in skill but certainly have great desire to grow, and wants to spend the money training and nurturing those people, then they could build a top notch person. It may be a little harsh, but I&#039;d rather begin with people that have both skill and motivation.</description>
		<content:encoded><![CDATA[<p>Perhaps I was overly focused on the code submission in my post &#8211; there are certainly other aspects of the process around getting a great candidate. </p>
<p>However, I still think that having a code submission be a &#8220;gate&#8221; in the process is important &#8211; immediately eliminating the ones that do not have the initial skill level.</p>
<p>Even outside of skill level, you can often tell how much effort someone puts into the code submission, so regardless of whether they make technical mistakes, you can tell whether they really tried in the first place. I find this to a be a reflection on hard they will try to excel at their profession, and grow as an individual.</p>
<p>Certainly, if any company can identify people who are lacking in skill but certainly have great desire to grow, and wants to spend the money training and nurturing those people, then they could build a top notch person. It may be a little harsh, but I&#8217;d rather begin with people that have both skill and motivation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

