<?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: Interviewing &#8211; Types of questions</title>
	<atom:link href="http://elegantcode.com/2008/01/14/interviewing-types-of-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/</link>
	<description></description>
	<lastBuildDate>Fri, 12 Mar 2010 14:11:39 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alex Mueller</title>
		<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/comment-page-1/#comment-17312</link>
		<dc:creator>Alex Mueller</dc:creator>
		<pubDate>Fri, 25 Jan 2008 04:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/01/14/interviewing-types-of-questions/#comment-17312</guid>
		<description>Thanks Scott, this is a helpful post for those of us having to interview. I will be sure to apply these techniques.</description>
		<content:encoded><![CDATA[<p>Thanks Scott, this is a helpful post for those of us having to interview. I will be sure to apply these techniques.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Starr</title>
		<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/comment-page-1/#comment-17155</link>
		<dc:creator>David Starr</dc:creator>
		<pubDate>Wed, 16 Jan 2008 03:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/01/14/interviewing-types-of-questions/#comment-17155</guid>
		<description>I get your point, Steve. I don&#039;t think Scott means to imply that other loines of questioning shouldn&#039;t be explored. For folks such as yourself, it may be better to have you walk through a problem on a white board, or something of that nature. Even that, though, is a situation in which you want the candidate to talk and open up.</description>
		<content:encoded><![CDATA[<p>I get your point, Steve. I don&#8217;t think Scott means to imply that other loines of questioning shouldn&#8217;t be explored. For folks such as yourself, it may be better to have you walk through a problem on a white board, or something of that nature. Even that, though, is a situation in which you want the candidate to talk and open up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Schimanski</title>
		<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/comment-page-1/#comment-17154</link>
		<dc:creator>Scott Schimanski</dc:creator>
		<pubDate>Wed, 16 Jan 2008 03:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/01/14/interviewing-types-of-questions/#comment-17154</guid>
		<description>Steve:

Thank you for the comments.  

You are absolutely correct.  You don&#039;t want to miss a great hire because the candidate is not great at speaking off the cuff.  With the quieter candidates, you will have to listen closely to their answers and ask questions based on their answers.  Hopefully, this will bring further information.   That is more difficult then bringing a list of questions.  Think of the reporters questions.  After the first answer to a question, think of the &quot;what&quot;, &quot;where&quot;, &quot;why&quot;, &quot;how&#039;, &quot;who&quot; of the topic to delve into more detail.

Scott</description>
		<content:encoded><![CDATA[<p>Steve:</p>
<p>Thank you for the comments.  </p>
<p>You are absolutely correct.  You don&#8217;t want to miss a great hire because the candidate is not great at speaking off the cuff.  With the quieter candidates, you will have to listen closely to their answers and ask questions based on their answers.  Hopefully, this will bring further information.   That is more difficult then bringing a list of questions.  Think of the reporters questions.  After the first answer to a question, think of the &#8220;what&#8221;, &#8220;where&#8221;, &#8220;why&#8221;, &#8220;how&#8217;, &#8220;who&#8221; of the topic to delve into more detail.</p>
<p>Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/comment-page-1/#comment-17137</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 15 Jan 2008 18:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/01/14/interviewing-types-of-questions/#comment-17137</guid>
		<description>Nice post. As always, the purpose of interview questions is to get the candidate to start talking. :)

A good acid test: If a question can be answered by the phrase &quot;YES&quot; or &quot;NO&quot; then it probably needs to be rephrased.

One question I ask in every interview is: &quot;What is the name of the last book you read?&quot; It&#039;s a moderately closed question, but it must be followed up with dialogue about either (1) why the person doesn&#039;t read, or (2) the person&#039;s good reading habits.

You&#039;d be surprised how many people -- technology people, developers included -- who say they don&#039;t read, not even technical books. Next candidate, please!</description>
		<content:encoded><![CDATA[<p>Nice post. As always, the purpose of interview questions is to get the candidate to start talking. <img src='http://elegantcode.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>A good acid test: If a question can be answered by the phrase &#8220;YES&#8221; or &#8220;NO&#8221; then it probably needs to be rephrased.</p>
<p>One question I ask in every interview is: &#8220;What is the name of the last book you read?&#8221; It&#8217;s a moderately closed question, but it must be followed up with dialogue about either (1) why the person doesn&#8217;t read, or (2) the person&#8217;s good reading habits.</p>
<p>You&#8217;d be surprised how many people &#8212; technology people, developers included &#8212; who say they don&#8217;t read, not even technical books. Next candidate, please!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Campbell</title>
		<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/comment-page-1/#comment-17135</link>
		<dc:creator>Steve Campbell</dc:creator>
		<pubDate>Tue, 15 Jan 2008 18:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/01/14/interviewing-types-of-questions/#comment-17135</guid>
		<description>It seems to me like the open ended questions would predispose towards a particular type of candidate - one that is good at thinking on his feet and putting thoughts into words right away.    I think you&#039;re probably missing out on the more thoughtful introspective potentials.

Without preparing for the specific question, there is small chance for someone like me to answer your questions well during an interview.</description>
		<content:encoded><![CDATA[<p>It seems to me like the open ended questions would predispose towards a particular type of candidate &#8211; one that is good at thinking on his feet and putting thoughts into words right away.    I think you&#8217;re probably missing out on the more thoughtful introspective potentials.</p>
<p>Without preparing for the specific question, there is small chance for someone like me to answer your questions well during an interview.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: McCoy</title>
		<link>http://elegantcode.com/2008/01/14/interviewing-types-of-questions/comment-page-1/#comment-17100</link>
		<dc:creator>McCoy</dc:creator>
		<pubDate>Mon, 14 Jan 2008 19:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/01/14/interviewing-types-of-questions/#comment-17100</guid>
		<description>Go Mad Dog!  Another great post!</description>
		<content:encoded><![CDATA[<p>Go Mad Dog!  Another great post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
