<?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; knowledge vs experience vs skill	</title>
	<atom:link href="https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/</link>
	<description>Java/J2EE Software Development and Technology Discussion Blog</description>
	<lastBuildDate>Thu, 23 Feb 2012 11:45:25 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: TOP-ALLIANCE		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4933</link>

		<dc:creator><![CDATA[TOP-ALLIANCE]]></dc:creator>
		<pubDate>Thu, 23 Feb 2012 11:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4933</guid>

					<description><![CDATA[interviwing is a very special skill, you need to adopt to situatioins.]]></description>
			<content:encoded><![CDATA[<p>interviwing is a very special skill, you need to adopt to situatioins.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Craig Branch		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4932</link>

		<dc:creator><![CDATA[Craig Branch]]></dc:creator>
		<pubDate>Wed, 22 Feb 2012 14:00:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4932</guid>

					<description><![CDATA[Experience can be hard to beat (although there can be exceptions).   The software industry is unique in that experience can trump education levels.  Give me someone with 10 plus years of experience over a freshly graduated Masters grad anyday.   
As far as those who have learned nothing in 7-10 years...that&#039;s not normal and there is probably  something else going on.  Its just not trying and I would think an interview process and checking with past managers and referrals would flush those type of issues out.]]></description>
			<content:encoded><![CDATA[<p>Experience can be hard to beat (although there can be exceptions).   The software industry is unique in that experience can trump education levels.  Give me someone with 10 plus years of experience over a freshly graduated Masters grad anyday.<br />
As far as those who have learned nothing in 7-10 years&#8230;that&#8217;s not normal and there is probably  something else going on.  Its just not trying and I would think an interview process and checking with past managers and referrals would flush those type of issues out.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Scott Selikoff		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4916</link>

		<dc:creator><![CDATA[Scott Selikoff]]></dc:creator>
		<pubDate>Wed, 01 Feb 2012 08:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4916</guid>

					<description><![CDATA[Unfortunately, Peter is sometimes correct.  People hire unqualified friends/families for jobs all the time, in pretty much every industry.  These days it&#039;s referred to as &quot;networking&quot;, but nepotism has been around for a very long time.]]></description>
			<content:encoded><![CDATA[<p>Unfortunately, Peter is sometimes correct.  People hire unqualified friends/families for jobs all the time, in pretty much every industry.  These days it&#8217;s referred to as &#8220;networking&#8221;, but nepotism has been around for a very long time.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jeanne Boyarsky		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4915</link>

		<dc:creator><![CDATA[Jeanne Boyarsky]]></dc:creator>
		<pubDate>Wed, 01 Feb 2012 02:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4915</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4914&quot;&gt;peter&lt;/a&gt;.

Depends on the recommender I guess.  I won&#039;t recommend someone without skills.  For knowledge and experience it depends on the position.  Some knowledge and experience matter even for an entry level position.  How closely it maps is another story.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4914">peter</a>.</p>
<p>Depends on the recommender I guess.  I won&#8217;t recommend someone without skills.  For knowledge and experience it depends on the position.  Some knowledge and experience matter even for an entry level position.  How closely it maps is another story.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: peter		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4914</link>

		<dc:creator><![CDATA[peter]]></dc:creator>
		<pubDate>Tue, 31 Jan 2012 17:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4914</guid>

					<description><![CDATA[I think the most important question is - &quot;who do you know at this company?&quot;

That seems to trump any skills, knowledge, and experience.]]></description>
			<content:encoded><![CDATA[<p>I think the most important question is &#8211; &#8220;who do you know at this company?&#8221;</p>
<p>That seems to trump any skills, knowledge, and experience.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jeanne Boyarsky		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4912</link>

		<dc:creator><![CDATA[Jeanne Boyarsky]]></dc:creator>
		<pubDate>Mon, 30 Jan 2012 02:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4912</guid>

					<description><![CDATA[Agreed.  And ironically it&#039;s the hardest of the three to measure.]]></description>
			<content:encoded><![CDATA[<p>Agreed.  And ironically it&#8217;s the hardest of the three to measure.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kathy Sierra		</title>
		<link>https://www.selikoff.net/2012/01/29/interviewing-knowledge-vs-experience-vs-skill/comment-page-1/#comment-4911</link>

		<dc:creator><![CDATA[Kathy Sierra]]></dc:creator>
		<pubDate>Mon, 30 Jan 2012 02:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=4158#comment-4911</guid>

					<description><![CDATA[All three are important, but this is one of those areas where (to quote Dan Pink) &quot;there is a gap between what science knows and business does&quot;. Thanks to our education system, we are heavily skewed toward assessing *knowledge* rather than skill (largely because knowledge is so much easier to put in a test). And in studies on expertise, the amount of experience is *not* a good predictor of performance beyond the first two years (the  &quot;ten years of experience vs. one year repeated 10 times&quot; phenomenon). 

So assessing skill -- as their level of expertise -- is potentially more useful than knowledge and experience (beyond some minimum threshold level of knowledge and experience, of course), but it is difficult to do. In the studies on professional performance, ericsson defined expertise as something like, &quot;given a representative task in the domain, an expert will consistently/reliably demonstrate better choices&quot;. One thing that did come out of these studies is that it IS possible to find a smallish subset of tasks that correlate to how someone will perform across most other tasks in the domain, but again, it takes work to figure out what those representative tasks are.

In Chess, for example, they were able to identify just a few positions that accurately predicted how a chess player would perform in tournaments overall. So in 15 minutes or less, they could determine how strong that chess player really was. There are some representative tasks in music and some technical fields, too. I am really interested in this right now :)

Sorry for the long, rambling comment. 
TL;DR: you are right, all three are needed, but skill assessment should be weighted much more heavily than knowledge or experience, especially for anyone with more than 18 months to two years of experience.]]></description>
			<content:encoded><![CDATA[<p>All three are important, but this is one of those areas where (to quote Dan Pink) &#8220;there is a gap between what science knows and business does&#8221;. Thanks to our education system, we are heavily skewed toward assessing *knowledge* rather than skill (largely because knowledge is so much easier to put in a test). And in studies on expertise, the amount of experience is *not* a good predictor of performance beyond the first two years (the  &#8220;ten years of experience vs. one year repeated 10 times&#8221; phenomenon). </p>
<p>So assessing skill &#8212; as their level of expertise &#8212; is potentially more useful than knowledge and experience (beyond some minimum threshold level of knowledge and experience, of course), but it is difficult to do. In the studies on professional performance, ericsson defined expertise as something like, &#8220;given a representative task in the domain, an expert will consistently/reliably demonstrate better choices&#8221;. One thing that did come out of these studies is that it IS possible to find a smallish subset of tasks that correlate to how someone will perform across most other tasks in the domain, but again, it takes work to figure out what those representative tasks are.</p>
<p>In Chess, for example, they were able to identify just a few positions that accurately predicted how a chess player would perform in tournaments overall. So in 15 minutes or less, they could determine how strong that chess player really was. There are some representative tasks in music and some technical fields, too. I am really interested in this right now 🙂</p>
<p>Sorry for the long, rambling comment.<br />
TL;DR: you are right, all three are needed, but skill assessment should be weighted much more heavily than knowledge or experience, especially for anyone with more than 18 months to two years of experience.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
