<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>interviewing process &#8211; Resource Center</title>
	<atom:link href="https://resources.eteki.com/tag/interviewing-process/feed/" rel="self" type="application/rss+xml" />
	<link>https://resources.eteki.com</link>
	<description>eTeki-Technical Screening for Quality IT Hires</description>
	<lastBuildDate>Mon, 05 Oct 2020 12:34:11 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.2.2</generator>
	<item>
		<title>3 Common Technical Interviewing Mistakes That Can Spoil Your IT Hiring</title>
		<link>https://resources.eteki.com/3-common-technical-interviewing-mistakes-can-spoil-hiring/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Thu, 08 Sep 2016 14:42:05 +0000</pubDate>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Hiring & Interviewing]]></category>
		<category><![CDATA[Metrics & Processes]]></category>
		<category><![CDATA[Recruiting & Staffing]]></category>
		<category><![CDATA[candidates]]></category>
		<category><![CDATA[employers]]></category>
		<category><![CDATA[interviewing process]]></category>
		<category><![CDATA[mistakes]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[Technical Interviewing]]></category>
		<guid isPermaLink="false">https://www.eteki.com/?p=924</guid>

					<description><![CDATA[<p>The post <a rel="nofollow" href="https://resources.eteki.com/3-common-technical-interviewing-mistakes-can-spoil-hiring/" data-wpel-link="internal">3 Common Technical Interviewing Mistakes That Can Spoil Your IT Hiring</a> appeared first on <a rel="nofollow" href="https://resources.eteki.com" data-wpel-link="internal">Resource Center</a>.</p>
]]></description>
										<content:encoded><![CDATA[<section class="vc_row wpb_row vc_row-fluid liquid-row-shadowbox-64e978c95dae0"><div class="ld-container container"><div class="row ld-row"><div class="wpb_column vc_column_container vc_col-sm-12 liquid-column-64e978c9650b9"><div class="vc_column-inner"><div class="wpb_wrapper "   ><div class="wpb_wrapper-inner">
	<div class="wpb_text_column wpb_content_element " >
		<div class="wpb_wrapper">
			<p><span style="font-weight: 400;">Are you unsatisfied with the caliber of your company’s IT hires? Are you losing top IT candidates to other employers?</span><br />
<span style="font-weight: 400;">If you answer “yes” to either of those questions, there’s a good chance your company is making one or more of the three biggest technical interviewing mistakes. Let’s check them out.</span></p>
<p><b>MISTAKE NO. 1: Your Interview Questions Aren’t Behavioral-Based</b><br />
<span style="font-weight: 400;">It’s critical for employers to identify during interviews if candidates will succeed in a given role. Yet, as Google HR Guru Laszlo Bock details in a fascinating article, “</span><a style="color: #44c8f5;" href="http://www.wired.com/2015/04/hire-like-google/" data-wpel-link="external" target="_blank" rel="external noopener noreferrer"><span style="font-weight: 400;">Here’s Google’s Secret to Hiring the Best People,”</span></a><span style="font-weight: 400;"> some employers ask questions that are worthless in determining if candidates are the right fit. Some examples: “What is your greatest strength?” “What is your greatest weakness?” “How many golf balls would fit inside a 747?”</span><br />
<span style="font-weight: 400;">Others make more of an effort to learn about candidates’ skills, but commit the error of focusing on theoretical questions. Quality answers to such questions only show that candidates understand theory, and have limited value in helping determine if candidates can successfully perform the job.<br />
</span><br />
<span style="font-weight: 400;">Instead, ask behavioral questions. The common-sense idea behind this approach is that the best indicator of future job performance is past job performance. What are behavioral questions? They are often introduced with phrases like “Tell me about a time…” Here are two examples Bock provided:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Tell me about a time your behavior had a positive impact on your team.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Tell me about a time you effectively managed your team to achieve a goal. What did your approach look like?</span></li>
</ul>
<p><span style="font-weight: 400;">The behavioral approach is vastly superior to traditional-style interviews, studies have consistently found. For example, a University of Notre Dame study found that behavioral interviews are 55% predictive of future on-the-job behavior, compared to just 10% for traditional interviews.</span></p>
<p><b>MISTAKE NO. 2: Your Interviewing Process Takes Too Long</b><br />
<span style="font-weight: 400;">A </span><a style="color: #44c8f5;" href="https://www.glassdoor.com/research/time-to-hire-in-25-countries/" data-wpel-link="external" target="_blank" rel="external noopener noreferrer"><span style="font-weight: 400;">2017 Glassdoor study</span></a><span style="font-weight: 400;"> found that the average job interview process in the United States takes 23.8 days. Meanwhile, as we noted in a recent post, IT professionals in high demand receive four to six job offers per week, according to </span><a style="color: #44c8f5;" href="http://rht.mediaroom.com/2016-08-11-Are-You-Taking-Too-Long-To-Hire" data-wpel-link="external" target="_blank" rel="external noopener noreferrer"><span style="font-weight: 400;">Robert Half</span></a><span style="font-weight: 400;">.<br />
</span><br />
<span style="font-weight: 400;">Combining the data, if you have an average-length interview process, IT pros in high demand could receive close to 20 other job offers during the process. So clearly, having a long interviewing process can make it harder to land top IT talent.</span><br />
<span style="font-weight: 400;">Here is a list of some of the key consequences of an overly long interviewing process:</span></p>
<ul>
<li style="font-weight: 400;"><b>Lower quality hires</b><span style="font-weight: 400;">—Key talent goes to other employers.</span></li>
<li style="font-weight: 400;"><b>Worse candidate experience</b><span style="font-weight: 400;">—A slow process frustrates candidates. Delayed interviews also can indicate to candidates that they aren’t a priority, especially when other employers schedule interviews quickly.</span></li>
<li style="font-weight: 400;"><b>Lower acceptance rates</b><span style="font-weight: 400;">—Other employers have more time to poach candidates.</span></li>
<li style="font-weight: 400;"><b>Reduced productivity</b><span style="font-weight: 400;">—Longer time to hire means projects don’t get completed.</span></li>
</ul>
<p><span style="font-weight: 400;">A common cause of overly long technical interviewing processes is it can take a week or more to determine when members of internal interviewing panels can fit in an interview.  If you decrease the length of time it takes to schedule, conduct, and score a candidate’s technical skills, your company will gain a competitive edge in the war for the best and brightest technical talent. </span></p>
<p><b>MISTAKE NO. 3: Shortcutting the Process</b><br />
<span style="font-weight: 400;">While you want to have an efficient technical interviewing process, it’s essential not to use shortcuts that spoil the results of the process. Shortcuts include not having standards for your technical interviews (e.g., not having common questions, not having common rating scale) or even not having technical interviews at all.<br />
</span><br />
<span style="font-weight: 400;">The consequences of spoiling the results are severe: you end up hiring the wrong people. With IT hires, that leads to frustrated co-workers, frustrated customers, key projects not getting completed, etc. Eventually it leads to higher turnover, the cost of which alone is estimated at 100-150% of annual salary for technical positions. SHRM has estimated that, factoring in the various consequences, the </span><a style="color: #44c8f5;" href="https://www.shrm.org/ResourcesAndTools/hr-topics/talent-acquisition/Pages/Morale-Productivity-Bad-Hires.aspx" data-wpel-link="external" target="_blank" rel="external noopener noreferrer"><span style="font-weight: 400;">cost of a bad hire</span></a><span style="font-weight: 400;"> could be as high as five times the amount of the bad hire’s salary. Assuming an average IT salary of $100,000, in IT, the cost could be $500,000 for each bad hire. </span></p>
<p><strong>Next in this series &#8211; <a style="color: #44c8f5;" href="http://resources.eteki.com/stop-playing-interviewing-guessing-game/" data-wpel-link="internal">How To Stop Playing the Interviewing Guessing Game</a></strong></p>

		</div>
	</div>
</div></div></div></div></div></div></section>
<p>The post <a rel="nofollow" href="https://resources.eteki.com/3-common-technical-interviewing-mistakes-can-spoil-hiring/" data-wpel-link="internal">3 Common Technical Interviewing Mistakes That Can Spoil Your IT Hiring</a> appeared first on <a rel="nofollow" href="https://resources.eteki.com" data-wpel-link="internal">Resource Center</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
