<?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: The Case for &#8220;Normal&#8221; Interviews</title>
	<atom:link href="http://www.webgrrls.com/blog/2010/08/16/the-case-for-normal-interviews/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webgrrls.com/blog/2010/08/16/the-case-for-normal-interviews/</link>
	<description>Insight, Information and Inspiration on women's careers, business, technology and the Industry.</description>
	<lastBuildDate>Sat, 09 Mar 2013 18:31:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Elena Strange</title>
		<link>http://www.webgrrls.com/blog/2010/08/16/the-case-for-normal-interviews/#comment-1920</link>
		<dc:creator>Elena Strange</dc:creator>
		<pubDate>Mon, 23 Aug 2010 15:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.webgrrls.com/blog/2010/08/16/the-case-for-normal-interviews/#comment-1920</guid>
		<description>@bwc, great point about microsoft! The whole write-code-on-the-board interview pretty much started with them, I think, many moons ago.</description>
		<content:encoded><![CDATA[<p>@bwc, great point about microsoft! The whole write-code-on-the-board interview pretty much started with them, I think, many moons ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bwc</title>
		<link>http://www.webgrrls.com/blog/2010/08/16/the-case-for-normal-interviews/#comment-1916</link>
		<dc:creator>bwc</dc:creator>
		<pubDate>Sat, 21 Aug 2010 02:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.webgrrls.com/blog/2010/08/16/the-case-for-normal-interviews/#comment-1916</guid>
		<description>I know right!  What is the point of technical interviews and are they as good or better at predicting the interviewee&#039;s success at the job?

In the company I worked in, my VP boss never gave anyone a technical interview because he expect you to be able to learn on the job and not be dumb.  So far in his 30 years in the same company, there was only 1 or 2 hires out of 40 or so that he hired, didn&#039;t work out after 1 year.. that&#039;s a 95% success rate.  He did it by looking at their degree and experience, summing up the person behaviorially AND see if they are a fit. That&#039;s it! 

A 95% success rate without technical interviews and these are programmers who are either majored in Comp Sci, MechE, CivilE, Aerospace Engineers who coded non-trivial software which other professional Engineers use to design the car which you and I use, the airplanes which transport you AND also F1 formula Racecar engineers used it to redesign the chassis to make the air flow efficient.. (not to mention pace maker blood flow and other stuff).

So why other industries which doesn&#039;t have this mission critical software requires stupid technical interviews.  Take Microsoft for example. Their software is not mission critical and their software CONTINTUES TO CRASH AND HOG MEMORY! Yet they still have intense technical interviews.  What&#039;s the point then!  Since they had intensely interviewed these candidates, shouldn&#039;t the software be flawless and not crash nor hog memory?! This just shows that technical interviews are not a good predictor of success. 

Or maybe it&#039;s majority of the people in my company has AT LEAST a MS degree?.</description>
		<content:encoded><![CDATA[<p>I know right!  What is the point of technical interviews and are they as good or better at predicting the interviewee&#8217;s success at the job?</p>
<p>In the company I worked in, my VP boss never gave anyone a technical interview because he expect you to be able to learn on the job and not be dumb.  So far in his 30 years in the same company, there was only 1 or 2 hires out of 40 or so that he hired, didn&#8217;t work out after 1 year.. that&#8217;s a 95% success rate.  He did it by looking at their degree and experience, summing up the person behaviorially AND see if they are a fit. That&#8217;s it! </p>
<p>A 95% success rate without technical interviews and these are programmers who are either majored in Comp Sci, MechE, CivilE, Aerospace Engineers who coded non-trivial software which other professional Engineers use to design the car which you and I use, the airplanes which transport you AND also F1 formula Racecar engineers used it to redesign the chassis to make the air flow efficient.. (not to mention pace maker blood flow and other stuff).</p>
<p>So why other industries which doesn&#8217;t have this mission critical software requires stupid technical interviews.  Take Microsoft for example. Their software is not mission critical and their software CONTINTUES TO CRASH AND HOG MEMORY! Yet they still have intense technical interviews.  What&#8217;s the point then!  Since they had intensely interviewed these candidates, shouldn&#8217;t the software be flawless and not crash nor hog memory?! This just shows that technical interviews are not a good predictor of success. </p>
<p>Or maybe it&#8217;s majority of the people in my company has AT LEAST a MS degree?.</p>
]]></content:encoded>
	</item>
</channel>
</rss>