<?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 &#8212; What to ask during an Interview</title>
	<atom:link href="http://www.earnedlessons.com/2009/03/06/interviewing-what-to-ask-during-an-interview/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.earnedlessons.com/2009/03/06/interviewing-what-to-ask-during-an-interview/</link>
	<description>Customer Joy. Employee Success. Investor Wealth.</description>
	<lastBuildDate>Thu, 27 May 2010 16:46:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Greg Linden</title>
		<link>http://www.earnedlessons.com/2009/03/06/interviewing-what-to-ask-during-an-interview/comment-page-1/#comment-25</link>
		<dc:creator>Greg Linden</dc:creator>
		<pubDate>Tue, 12 May 2009 16:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=143#comment-25</guid>
		<description>Good advice here, Ruben.

I see you mentioned expanding in depth during the interview.  That is closest to my personal style of interviewing.

I usually am looking for enthusiasm for a problem, depth of knowledge on that problem, and a willingness to admit the limits to their knowledge.  My strategy is to keep asking probing questions about an area of their previous work, going deeper and deeper, asking them to express why it is important, what they tried, and what they could also have tried.

Ideally, not only does the candidate infect you with their enthusiasm for the problem, but they teach you something.

At least in fast-paced software companies, I think these characteristics best determine someone&#039;s likelihood of success.  I think it selects for people that can get things done quickly using small teams.

That being said, interviewing is difficult and full of false positives and negatives.  Companies like Amazon and Google bias their selection criteria to encourage false negatives -- deeming them less risky than false positives -- but that sadly does prevent many good people from getting through the door.</description>
		<content:encoded><![CDATA[<p>Good advice here, Ruben.</p>
<p>I see you mentioned expanding in depth during the interview.  That is closest to my personal style of interviewing.</p>
<p>I usually am looking for enthusiasm for a problem, depth of knowledge on that problem, and a willingness to admit the limits to their knowledge.  My strategy is to keep asking probing questions about an area of their previous work, going deeper and deeper, asking them to express why it is important, what they tried, and what they could also have tried.</p>
<p>Ideally, not only does the candidate infect you with their enthusiasm for the problem, but they teach you something.</p>
<p>At least in fast-paced software companies, I think these characteristics best determine someone&#8217;s likelihood of success.  I think it selects for people that can get things done quickly using small teams.</p>
<p>That being said, interviewing is difficult and full of false positives and negatives.  Companies like Amazon and Google bias their selection criteria to encourage false negatives &#8212; deeming them less risky than false positives &#8212; but that sadly does prevent many good people from getting through the door.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry Bricker</title>
		<link>http://www.earnedlessons.com/2009/03/06/interviewing-what-to-ask-during-an-interview/comment-page-1/#comment-22</link>
		<dc:creator>Jerry Bricker</dc:creator>
		<pubDate>Tue, 28 Apr 2009 17:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.earnedlessons.com/?p=143#comment-22</guid>
		<description>A good explanation about the types of probing questions to ask a candidates who is interviewing for a technical position.</description>
		<content:encoded><![CDATA[<p>A good explanation about the types of probing questions to ask a candidates who is interviewing for a technical position.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
