<?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>the interviewer &#8211; Resource Center</title>
	<atom:link href="https://resources.eteki.com/tag/the-interviewer/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:19:15 +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>The Terrible Technical Interview: 6 Examples</title>
		<link>https://resources.eteki.com/terrible-technical-interview-6-examples/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Thu, 10 Nov 2016 14:22:10 +0000</pubDate>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Hiring & Interviewing]]></category>
		<category><![CDATA[Metrics & Processes]]></category>
		<category><![CDATA[Recruiting & Staffing]]></category>
		<category><![CDATA[bad hire]]></category>
		<category><![CDATA[hiring manager]]></category>
		<category><![CDATA[interview practices]]></category>
		<category><![CDATA[the candidate]]></category>
		<category><![CDATA[the interviewer]]></category>
		<guid isPermaLink="false">https://www.eteki.com/?p=1107</guid>

					<description><![CDATA[<p>The post <a rel="nofollow" href="https://resources.eteki.com/terrible-technical-interview-6-examples/" data-wpel-link="internal">The Terrible Technical Interview: 6 Examples</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-64eb942f1eaff"><div class="ld-container container"><div class="row ld-row"><div class="wpb_column vc_column_container vc_col-sm-12 liquid-column-64eb942f2565e"><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;">There are good interview practices and there are bad interview practices. Good interview practices lead to the hiring of the right person for the right job. Bad interview practices lead to terrible hiring decisions.<br />
</span><br />
<span style="font-weight: 400;">In the case of tech, the result of a bad hire is staggering. There are financial reasons. SHRM has estimated that the cost of a bad hire could be as high as five times the amount of the bad hire’s salary. Assuming an average IT salary of $100,000, the cost could be $500,000 per bad hire. <span style="color: #ffffff;">terrible technical interview</span><br />
</span><br />
<span style="font-weight: 400;">There is the loss of morale and productivity that comes with a bad hire. </span><br />
<span style="font-weight: 400;">And missing out on that exceptional candidate who should have been hired in the first place.<br />
</span><br />
<span style="font-weight: 400;">The following six examples illustrate <a style="color: #44c8f5;" href="https://resources.eteki.com/avoiding-technical-interview-pitfalls-practical-tips-technical-interview-experts/" data-wpel-link="internal">pitfalls</a> that can occur during the technical interview process – and some tips to avoid them.  </span></p>
<ol>
<li><b> Overemphasizing the Importance of Certifications and Credentials.</b></li>
</ol>
<p><span style="font-weight: 400;">A recruiting manager hired an IT candidate primarily because of the individual’s Project Management Professional (PMP) certification while ignoring another candidate with ten years more experience but without the PMP certification. Things didn’t work out. <span style="color: #ffffff;">terrible technical interview</span><br />
</span><br />
<i><span style="font-weight: 400;">Lesson learned?  Don’t outright reject applicants, and discount their experience and accomplishments, just because they don’t have the right degree or certification.</span></i></p>
<ol start="2">
<li><b> Not Using Proper Interviewing Technology </b></li>
</ol>
<p><span style="font-weight: 400;">During an interview on Skype, the interviewer wrote some programming code on a whiteboard and asked the engineering candidate to provide feedback.  Problem was, the candidate couldn’t see the whiteboard so the interviewer clumsily tried to reposition their webcam to point at the whiteboard. The technical job candidate was not impressed.<br />
</span><br />
<i><span style="font-weight: 400;">Lesson learned?  This could have easily been avoided by using video interviewing technologies, like collaborative whiteboards, to improve the interview and avoid a candidate experience train wreck.</span></i></p>
<ol start="3">
<li><b> Putting Non Technical Individuals In Charge of Screening Technical Candidates</b></li>
</ol>
<p><span style="font-weight: 400;">Insulted by a recruiter’s ill informed questions, an IT candidate suggested they would prefer being interviewed by someone who understands IT and could ask more challenging questions. A little arrogant? Possibly, but not having the right interviewer can prevent you from hiring the best candidate.<br />
</span><br />
<i><span style="font-weight: 400;">Lesson Learned?  If your recruiters don’t have the technical experience and knowledge to screen candidates for technical positions, consider outsourcing your technical interviews to a company with the technical know-how, like eTeki.  </span></i></p>
<ol start="4">
<li><b> Ignoring Your Gut</b></li>
</ol>
<p><span style="font-weight: 400;">After just one phone interview and no in-person meeting, John was hired. Almost immediately, the team realized a terrible decision had been made. The interviewer, in retrospect, realized he ignored warning signs during the interview process in his haste to fill the job.<br />
</span><br />
<i><span style="font-weight: 400;">Lesson Learned?  Research shows that hiring on ‘gut’ instincts alone results in a high hiring failure rate.  And there is the potential for unfair bias.  But never ignore your instincts.  Be aware and curious of your hunches. It usually means that you need to do more due diligence.</span></i></p>
<ol start="5">
<li><b> Trying to Get More Experience for Less Money</b></li>
</ol>
<p><span style="font-weight: 400;">A hiring manager found a highly qualified candidate for an open software development position but the candidate’s salary expectations were slightly higher that what the hiring manager wanted to pay.  So the hiring manager continued interviewing candidates – and lost the best applicant.<br />
</span><br />
<i><span style="font-weight: 400;">Lesson Learned?  Don’t fall victim to the Fear of Missing Out syndrome (FoMO). Holding out to find a better candidate for a little less money rarely works.  Don’t let a few dollars come between your technical job opening and the best candidate. Pay them.</span></i></p>
<ol start="6">
<li><b> Overwhelming The Candidate</b></li>
</ol>
<p><span style="font-weight: 400;">After a candidate for a highly technical position got past an initial screening by a recruiter, a major bank scheduled a phone interview with the candidate to assess culture fit.  After phoning in for the interview, the candidate was greeted by seven panelists!<br />
</span><br />
<i><span style="font-weight: 400;">Lesson Learned?  Too many meetings, too many interviewers in one meeting, not enough breaks in between meetings. Don’t overwhelm candidates.  The best applicants are likely to walk or won’t be given the opportunity to showcase their skills. <span style="color: #ffffff;">terrible technical interview</span></span></i></p>
<p><b>Conclusion: Don’t Make These Interviewing Mistakes<br />
</b><br />
<span style="font-weight: 400;">To avoid these scary situations and others, consider outsourcing your technical interviews to service providers such as <a style="color: #44c8f5;" href="https://www.eteki.com/" data-wpel-link="internal">eTeki</a>.  They will schedule candidates for interviews within 24 hours with external IT pros who are <a style="color: #44c8f5;" href="https://www.eteki.com/meet-interview-experts/" data-wpel-link="internal">certified in technical interviewing</a>. These interviewers use best practices so candidates’ skills are appropriately compared and compliance is ensured.</span></p>

		</div>
	</div>
</div></div></div></div></div></div></section>
<p>The post <a rel="nofollow" href="https://resources.eteki.com/terrible-technical-interview-6-examples/" data-wpel-link="internal">The Terrible Technical Interview: 6 Examples</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>
