<?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: Learning From My Hiring Mistakes</title>
	<atom:link href="http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/</link>
	<description></description>
	<lastBuildDate>Sat, 24 Sep 2011 17:20:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Ernest Mueller</title>
		<link>http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/comment-page-1/#comment-686</link>
		<dc:creator>Ernest Mueller</dc:creator>
		<pubDate>Tue, 08 Jun 2010 18:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesimplelogic.com/?p=234#comment-686</guid>
		<description>Great post.  I&#039;ve also had a variety of hires that didn&#039;t work out that I think I could have foreseen better.  

I agree with putting them in front of a bunch of people.  I make sure my peer Infrastructure managers talk to them, dev managers talk to them, and business customer managers.  For the main technical interview I just bring in my entire team, usually, for both tech and fit.  If everyone thinks the guy&#039;s an a-hole, then regardless of how his skills are, it won&#039;t be good for a collaborative environment.

You totally have to be thorough and not compromise.  And that hurts - I&#039;ve had several times where I went through an entire recruiting process - post jobs, get in 80 resumes to sort through, do a dozen phone interviews and four in-person ones...  And then have a &quot;best candidate&quot; that I think is kinda B-.  When you throw them back and start the process again, it&#039;s tough (and can cost you months).  But similar to you, every time I&#039;ve said &quot;Well...  I&#039;m really not feeling this guy&#039;s level of initiative, but I really need some headcount...&quot; it&#039;s come back to burn me.  Insisting on A players is good but hard.</description>
		<content:encoded><![CDATA[<p>Great post.  I&#8217;ve also had a variety of hires that didn&#8217;t work out that I think I could have foreseen better.  </p>
<p>I agree with putting them in front of a bunch of people.  I make sure my peer Infrastructure managers talk to them, dev managers talk to them, and business customer managers.  For the main technical interview I just bring in my entire team, usually, for both tech and fit.  If everyone thinks the guy&#8217;s an a-hole, then regardless of how his skills are, it won&#8217;t be good for a collaborative environment.</p>
<p>You totally have to be thorough and not compromise.  And that hurts &#8211; I&#8217;ve had several times where I went through an entire recruiting process &#8211; post jobs, get in 80 resumes to sort through, do a dozen phone interviews and four in-person ones&#8230;  And then have a &#8220;best candidate&#8221; that I think is kinda B-.  When you throw them back and start the process again, it&#8217;s tough (and can cost you months).  But similar to you, every time I&#8217;ve said &#8220;Well&#8230;  I&#8217;m really not feeling this guy&#8217;s level of initiative, but I really need some headcount&#8230;&#8221; it&#8217;s come back to burn me.  Insisting on A players is good but hard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apolinaras "Apollo" Sinkevicius - The Operations Guy</title>
		<link>http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/comment-page-1/#comment-531</link>
		<dc:creator>Apolinaras "Apollo" Sinkevicius - The Operations Guy</dc:creator>
		<pubDate>Mon, 17 May 2010 18:28:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesimplelogic.com/?p=234#comment-531</guid>
		<description>I think it is very important we stop using the general term &quot;operations&quot; to describe what is just technology operations. TechOps/DevOps is only one organ in the large body called operations. Technology operations is a cost center, operations is a revenue generator.

Especially when we speak about SMBs, it is important to get the lingo right. There are too many so called &quot;operations people&quot; who are merely glorified network admins and would choke at the first sight of a forecast, employee problem, or strategy session with the board.

High-value member of operations team (especially a leader) not only will know his/her way around, but will have a track record with IT systems, HR, project management, service delivery, customer service management, accounting, and even marketing. Operations person is supposed to be ultra-generalist.

Here are two posts on the subject:
&quot;What to Look for in a Chief Right Hand Person (COO, VP of Operations)&quot; http://theoperationsguy.com/what-to-look-for-in-coo-head-of-operations
&quot;Defining the Difference Between (Business) Operations and Technology Operations&quot;
http://theoperationsguy.com/difference-between-business-and-technology-operations

On the subject of hiring technology operations people: 
1. Ability to learn is king! Technologies change now on weekly basis. What was relevant yesterday is no longer relevant today. Just because you puked up every bit of tech jargon you know, that gives me absolutely no guarantee you can do the job. Show me how you think, show me how you learn, and show me you are not stuck in your dinosaur era with related IBM-era entitlement.
2. I no longer pay attention to certifications. With all the mind dumps available out there and rampant cheating, I simply no longer have trust in the certs. To add on top of that, even if you did not cheat, all it says to me is that you take multiple choice tests well.</description>
		<content:encoded><![CDATA[<p>I think it is very important we stop using the general term &#8220;operations&#8221; to describe what is just technology operations. TechOps/DevOps is only one organ in the large body called operations. Technology operations is a cost center, operations is a revenue generator.</p>
<p>Especially when we speak about SMBs, it is important to get the lingo right. There are too many so called &#8220;operations people&#8221; who are merely glorified network admins and would choke at the first sight of a forecast, employee problem, or strategy session with the board.</p>
<p>High-value member of operations team (especially a leader) not only will know his/her way around, but will have a track record with IT systems, HR, project management, service delivery, customer service management, accounting, and even marketing. Operations person is supposed to be ultra-generalist.</p>
<p>Here are two posts on the subject:<br />
&#8220;What to Look for in a Chief Right Hand Person (COO, VP of Operations)&#8221; <a href="http://theoperationsguy.com/what-to-look-for-in-coo-head-of-operations" rel="nofollow">http://theoperationsguy.com/what-to-look-for-in-coo-head-of-operations</a><br />
&#8220;Defining the Difference Between (Business) Operations and Technology Operations&#8221;<br />
<a href="http://theoperationsguy.com/difference-between-business-and-technology-operations" rel="nofollow">http://theoperationsguy.com/difference-between-business-and-technology-operations</a></p>
<p>On the subject of hiring technology operations people:<br />
1. Ability to learn is king! Technologies change now on weekly basis. What was relevant yesterday is no longer relevant today. Just because you puked up every bit of tech jargon you know, that gives me absolutely no guarantee you can do the job. Show me how you think, show me how you learn, and show me you are not stuck in your dinosaur era with related IBM-era entitlement.<br />
2. I no longer pay attention to certifications. With all the mind dumps available out there and rampant cheating, I simply no longer have trust in the certs. To add on top of that, even if you did not cheat, all it says to me is that you take multiple choice tests well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention The Simple Logic » Blog Archive » Learning From My Hiring Mistakes -- Topsy.com</title>
		<link>http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/comment-page-1/#comment-530</link>
		<dc:creator>Tweets that mention The Simple Logic » Blog Archive » Learning From My Hiring Mistakes -- Topsy.com</dc:creator>
		<pubDate>Mon, 17 May 2010 15:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesimplelogic.com/?p=234#comment-530</guid>
		<description>[...] This post was mentioned on Twitter by patrickdebois, Adam Fletcher. Adam Fletcher said: Updated blog post link, Learning From My Hiring Mistakes: http://bit.ly/9UyJDe [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by patrickdebois, Adam Fletcher. Adam Fletcher said: Updated blog post link, Learning From My Hiring Mistakes: <a href="http://bit.ly/9UyJDe" rel="nofollow">http://bit.ly/9UyJDe</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention The Simple Logic » Blog Archive » Learning From My Hiring Mistakes -- Topsy.com</title>
		<link>http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/comment-page-1/#comment-490</link>
		<dc:creator>Tweets that mention The Simple Logic » Blog Archive » Learning From My Hiring Mistakes -- Topsy.com</dc:creator>
		<pubDate>Mon, 17 May 2010 05:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesimplelogic.com/?p=234#comment-490</guid>
		<description>[...] This post was mentioned on Twitter by Skills[inside], Adam Fletcher. Adam Fletcher said: New blog post: Learning From My Hiring Mistakes, http://bit.ly/c5uJ8f [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Skills[inside], Adam Fletcher. Adam Fletcher said: New blog post: Learning From My Hiring Mistakes, <a href="http://bit.ly/c5uJ8f" rel="nofollow">http://bit.ly/c5uJ8f</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Parise</title>
		<link>http://www.thesimplelogic.com/2010/05/16/learning-from-my-hiring-mistakes/comment-page-1/#comment-488</link>
		<dc:creator>Jon Parise</dc:creator>
		<pubDate>Mon, 17 May 2010 05:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesimplelogic.com/?p=234#comment-488</guid>
		<description>I agree with absolutely everyone one of these.  I&#039;m personally guilty of at least two of these mistakes.

Hopefully, new hiring managers will benefit from your experience and advice, but I also suspect that much of this needs to be learned firsthand, unfortunately.</description>
		<content:encoded><![CDATA[<p>I agree with absolutely everyone one of these.  I&#8217;m personally guilty of at least two of these mistakes.</p>
<p>Hopefully, new hiring managers will benefit from your experience and advice, but I also suspect that much of this needs to be learned firsthand, unfortunately.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

