<?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: Thoughts on Hiring Developers</title>
	<atom:link href="http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/</link>
	<description></description>
	<lastBuildDate>Tue, 02 Apr 2013 20:36:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Some Dude</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-10791</link>
		<dc:creator>Some Dude</dc:creator>
		<pubDate>Tue, 02 Apr 2013 20:36:56 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-10791</guid>
		<description>I&#039;m surprised that everyone expects developers to be &quot;passionate&quot; about their work to the extent that they&#039;ll go home and do it (for free). Nobody demands that a plumber, mechanic, politician, doctor etc do unpaid work. People often have a high number of life demands that preclude much, if any, unpaid work. Important things like kids, community activities and hobbies that round out the individual (and maybe keep the individual from being so round...) . 

as a tid bit: &quot;passion&quot; has original meanings of suffering and pain. I do not want to suffer under any hobby ...</description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised that everyone expects developers to be &#8220;passionate&#8221; about their work to the extent that they&#8217;ll go home and do it (for free). Nobody demands that a plumber, mechanic, politician, doctor etc do unpaid work. People often have a high number of life demands that preclude much, if any, unpaid work. Important things like kids, community activities and hobbies that round out the individual (and maybe keep the individual from being so round&#8230;) . </p>
<p>as a tid bit: &#8220;passion&#8221; has original meanings of suffering and pain. I do not want to suffer under any hobby &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-140</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Thu, 17 Feb 2011 15:40:05 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-140</guid>
		<description>When I was a hiring manager for the development team at my company, we had some criteria we looked for. Experience was one, but we hired many recent graduates without experience, simply because they had the drive and they found the field exciting. One individual brought in his Nintendo DS and showed us some games he developed. Another wowed us with his learning of 4 different languages simultaneously. 

We could have hired a senior individual but did not. He told us at the interview that he doesn&#039;t do the learning on his own time. To us, the field was not a passion or an interest, but simply a job. We wanted people who would push the company and the development team to the next level, challenge their colleagues, and introduce new things to the team.

If that was not there, all we got was a &quot;code monkey&quot; which would be a burden to all - the managers, the colleagues, and the company.</description>
		<content:encoded><![CDATA[<p>When I was a hiring manager for the development team at my company, we had some criteria we looked for. Experience was one, but we hired many recent graduates without experience, simply because they had the drive and they found the field exciting. One individual brought in his Nintendo DS and showed us some games he developed. Another wowed us with his learning of 4 different languages simultaneously. </p>
<p>We could have hired a senior individual but did not. He told us at the interview that he doesn&#8217;t do the learning on his own time. To us, the field was not a passion or an interest, but simply a job. We wanted people who would push the company and the development team to the next level, challenge their colleagues, and introduce new things to the team.</p>
<p>If that was not there, all we got was a &#8220;code monkey&#8221; which would be a burden to all &#8211; the managers, the colleagues, and the company.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Siderite</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-139</link>
		<dc:creator>Siderite</dc:creator>
		<pubDate>Sat, 05 Feb 2011 10:51:27 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-139</guid>
		<description>I was in high school and my friends and colleagues were discussing girls. Some of the girls were just great, but they expected too much. Others were rather easy, but nothing to learn there. But the subtlety was always around the negotiation. One girl wanted a very specific thing from her boy, but not actually specify it; another would test the boy non stop until he would quit; one would say she preffered honesty and love, but she would always choose the guy who falsely advertised himself. Then girls would complain about the poor quality of boys and what jerks we were and enumerated the qualities they all thought were great in a guy, then ended up being best friends with him if ever found.

Reading this series of posts of yours, I realise that I&#039;ve heard this kind of talk before, right then :)</description>
		<content:encoded><![CDATA[<p>I was in high school and my friends and colleagues were discussing girls. Some of the girls were just great, but they expected too much. Others were rather easy, but nothing to learn there. But the subtlety was always around the negotiation. One girl wanted a very specific thing from her boy, but not actually specify it; another would test the boy non stop until he would quit; one would say she preffered honesty and love, but she would always choose the guy who falsely advertised himself. Then girls would complain about the poor quality of boys and what jerks we were and enumerated the qualities they all thought were great in a guy, then ended up being best friends with him if ever found.</p>
<p>Reading this series of posts of yours, I realise that I&#8217;ve heard this kind of talk before, right then <img src='http://lostechies.com/rayhouston/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Houston</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-138</link>
		<dc:creator>Ray Houston</dc:creator>
		<pubDate>Fri, 04 Feb 2011 23:30:55 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-138</guid>
		<description>@Paul (forth comment) - what we did, which I felt worked really well, is that we told them in advance to study up on the SOLID principles. We would tell them that it doesn&#039;t matter if they completely understood them or not, but we&#039;d use them as a talking point during the interview. When the candidate came it, we would have a projector in a small conference room with me typing code into notepad (to reduce distraction). I&#039;d start off with something like:

public interface IWeapon
{
}

public interface ICharacter
{
}

public void HandleAttack(IWeapon weapon, ICharacter character)
{
}

We&#039;d then ask them about interfaces, coupling, etc. We&#039;d ask them to modify HandleAttack (change method parameters if they want) to really orchestrate the attack, which forces them to think about implementation details such whether the Character is the attacker or the target. Does the Attack method go on the Weapon or the Character. How does the Weapon affect the character? What if we add other types of weapons that affect other attributes such as speed? What if Weapons can affect things other than Characters such as Environments. If we add new Weapons to the program, how much code would I have to change?

We&#039;d spend about an hour doing this. Throughout, we would explain how the SOLID principles apply and throw in additional challenges if they did well. There was no right or wrong answer and we would be upfront with the candidates about this. The code would look completely different each time. It helped us see how they think and interacted with others. We could also tell if they were excited by the principles or if they would rather not bother.</description>
		<content:encoded><![CDATA[<p>@Paul (forth comment) &#8211; what we did, which I felt worked really well, is that we told them in advance to study up on the SOLID principles. We would tell them that it doesn&#8217;t matter if they completely understood them or not, but we&#8217;d use them as a talking point during the interview. When the candidate came it, we would have a projector in a small conference room with me typing code into notepad (to reduce distraction). I&#8217;d start off with something like:</p>
<p>public interface IWeapon<br />
{<br />
}</p>
<p>public interface ICharacter<br />
{<br />
}</p>
<p>public void HandleAttack(IWeapon weapon, ICharacter character)<br />
{<br />
}</p>
<p>We&#8217;d then ask them about interfaces, coupling, etc. We&#8217;d ask them to modify HandleAttack (change method parameters if they want) to really orchestrate the attack, which forces them to think about implementation details such whether the Character is the attacker or the target. Does the Attack method go on the Weapon or the Character. How does the Weapon affect the character? What if we add other types of weapons that affect other attributes such as speed? What if Weapons can affect things other than Characters such as Environments. If we add new Weapons to the program, how much code would I have to change?</p>
<p>We&#8217;d spend about an hour doing this. Throughout, we would explain how the SOLID principles apply and throw in additional challenges if they did well. There was no right or wrong answer and we would be upfront with the candidates about this. The code would look completely different each time. It helped us see how they think and interacted with others. We could also tell if they were excited by the principles or if they would rather not bother.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-137</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 04 Feb 2011 23:11:19 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-137</guid>
		<description>Just an note about hiring Jr. Devs. One question I will ALWAYS as a Jr. dev is, &quot;What are the last couple programming related books you read and what did you think of them?&quot; I use this question to gauge the dev&#039;s desire to learn and grow in a more Sr. Dev role. </description>
		<content:encoded><![CDATA[<p>Just an note about hiring Jr. Devs. One question I will ALWAYS as a Jr. dev is, &#8220;What are the last couple programming related books you read and what did you think of them?&#8221; I use this question to gauge the dev&#8217;s desire to learn and grow in a more Sr. Dev role. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Houston</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-136</link>
		<dc:creator>Ray Houston</dc:creator>
		<pubDate>Fri, 04 Feb 2011 22:44:29 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-136</guid>
		<description>@KevDog and @middledd - you may be correct that most companies only want senior developers. Perhaps you should target specific companies that are willing to take a chance on a junior?

@middledd, you have a very good point and I think I will write a blog post about hiring a junior and how it was successful. It&#039;s sounds like you did finally have success and land the job you wanted. That is awesome. I encourage you to blog about your experience. I&#039;d love to read it.

In an interview there are other factors at play that could distroy your chances. How did you dress? Did you show humility or did you come off as aggrogant? Were you confident without being over confident? Did you make any off colored commits? Where you playing with your phone? Did you have body oder? All of these things have been factors with some candidates that I&#039;ve interviewed throughout the years. I remembered a long time ago I interviewed a fellow that was well dress but had a large metal bracelet that kept banging on table as he talked with his hands. I didn&#039;t mind the bracelet but the banging noise destracted me so much that I didn&#039;t listen to anything he had to say.</description>
		<content:encoded><![CDATA[<p>@KevDog and @middledd &#8211; you may be correct that most companies only want senior developers. Perhaps you should target specific companies that are willing to take a chance on a junior?</p>
<p>@middledd, you have a very good point and I think I will write a blog post about hiring a junior and how it was successful. It&#8217;s sounds like you did finally have success and land the job you wanted. That is awesome. I encourage you to blog about your experience. I&#8217;d love to read it.</p>
<p>In an interview there are other factors at play that could distroy your chances. How did you dress? Did you show humility or did you come off as aggrogant? Were you confident without being over confident? Did you make any off colored commits? Where you playing with your phone? Did you have body oder? All of these things have been factors with some candidates that I&#8217;ve interviewed throughout the years. I remembered a long time ago I interviewed a fellow that was well dress but had a large metal bracelet that kept banging on table as he talked with his hands. I didn&#8217;t mind the bracelet but the banging noise destracted me so much that I didn&#8217;t listen to anything he had to say.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: middledd</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-135</link>
		<dc:creator>middledd</dc:creator>
		<pubDate>Fri, 04 Feb 2011 21:24:32 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-135</guid>
		<description>And KevDog&#039;s reply above is a perfect example of what I&#039;m trying to say.  They even did interviews on CNN and other places where companies said flat out, they can&#039;t afford to hire Junior level persons.  The companies they talked to ALL said NOT ONE THING about ambition, drive, motivation, desire to learn - they ALL pointed to experience as the driving factor in their search for employees.  I just feel like, unless you know someone (and i&#039;m starting to place more time and energy into networking), or unless you credentials are A+ material, you aren&#039;t really given a chance unless you start completely at the bottom (ie. the helpdesk) and somehow work your way to being a skilled developer.  That&#039;s even how I got into this game.

So, while your organization (and i&#039;m sure the other organizations that you network with) are most likely the exception and do highly value the more personal aspects of the candidates you interview - from the outside looking in you are the exception.  And it just makes it frustrating to hear companies such as yourself say that you value one thing, and then get &quot;stabbed in the back&quot; so to speak by all these other companies that care nothing about their employees or the personal side of the equation and only care about their bottom line and in bringing on experienced persons.  I&#039;d much rather you try to show these other companies how to develop and cultivate talent, than &quot;rant&quot; about the skill level of the developers. 

Obviously I read your blog, and I will continue to do so.  So I don&#039;t really believe YOU are as arrogant as the rest and I value your opinion, however, I just want to let you all know that from the outside looking in, the picture doesnt appear to be anything close to what you are describing.</description>
		<content:encoded><![CDATA[<p>And KevDog&#8217;s reply above is a perfect example of what I&#8217;m trying to say.  They even did interviews on CNN and other places where companies said flat out, they can&#8217;t afford to hire Junior level persons.  The companies they talked to ALL said NOT ONE THING about ambition, drive, motivation, desire to learn &#8211; they ALL pointed to experience as the driving factor in their search for employees.  I just feel like, unless you know someone (and i&#8217;m starting to place more time and energy into networking), or unless you credentials are A+ material, you aren&#8217;t really given a chance unless you start completely at the bottom (ie. the helpdesk) and somehow work your way to being a skilled developer.  That&#8217;s even how I got into this game.</p>
<p>So, while your organization (and i&#8217;m sure the other organizations that you network with) are most likely the exception and do highly value the more personal aspects of the candidates you interview &#8211; from the outside looking in you are the exception.  And it just makes it frustrating to hear companies such as yourself say that you value one thing, and then get &#8220;stabbed in the back&#8221; so to speak by all these other companies that care nothing about their employees or the personal side of the equation and only care about their bottom line and in bringing on experienced persons.  I&#8217;d much rather you try to show these other companies how to develop and cultivate talent, than &#8220;rant&#8221; about the skill level of the developers. </p>
<p>Obviously I read your blog, and I will continue to do so.  So I don&#8217;t really believe YOU are as arrogant as the rest and I value your opinion, however, I just want to let you all know that from the outside looking in, the picture doesnt appear to be anything close to what you are describing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: middledd</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-134</link>
		<dc:creator>middledd</dc:creator>
		<pubDate>Fri, 04 Feb 2011 21:16:08 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-134</guid>
		<description>For those who noticed my 3 pages of comments (which probably spurred this blog post), the below quote epitomizes my complaints:

&quot;There is some discussion in the comments of Gabriel’s post about “low quality” developers are not able to land “high quality” jobs because those jobs require you to already be highly skilled. I do not think this is true. A lower skilled individual just has to try harder. I am impressed with candidates that I meet who are currently working in a lower skilled development position and have the desire to move to a higher one. First it shows that they acknowledge their skill level. Second it shows that they have enough interest in development to want to become better. If you want a shot at something, show that you deserve it.&quot;

I think that is completely incorrect.  I have ALWAYS been a very motivated individual when it comes to trying to succeed at something that I have set my mind on.  I have also always heard companies offering lip service saying that they really want someone who is junior and eager to learn, before I interview with them.  However, I have also been told, on a few occasions, that the companies love my skills and they absolutely loved the ambition i showed during the interview process.  However, they simply found someone who was &quot;more senior&quot; to fill the position.  In those situations, I do not think there was anything i could have done to get those positions, even though they intially said they were not looking for someone senior.  I have even been in situations where I have gone through the employers&#039; headhunter, made it through 3 sometimes 4 rounds of interviews, passed the tests and everything.  Then have the manager of the company call me personally, expressing regret b/c although I was exactly what they SAID they wanted and sometimes MORE, they eventually found someone that was simply more experienced than I.

Maybe it&#039;s just me.  Maybe I have simply had a lot of back luck finding a truly good place to work in the past (I LOVE my current job).  Maybe, quite frankly, maybe I just wasn&#039;t as motivated in the past as I am now.  HOWEVER, I strongly strongly strongly do not believe that is the case.  And I strongly strongly strongly believe that I am far from alone; in fact, I honestly feel that many devs who have gone through alot of interviews would share my viewpoint.  </description>
		<content:encoded><![CDATA[<p>For those who noticed my 3 pages of comments (which probably spurred this blog post), the below quote epitomizes my complaints:</p>
<p>&#8220;There is some discussion in the comments of Gabriel’s post about “low quality” developers are not able to land “high quality” jobs because those jobs require you to already be highly skilled. I do not think this is true. A lower skilled individual just has to try harder. I am impressed with candidates that I meet who are currently working in a lower skilled development position and have the desire to move to a higher one. First it shows that they acknowledge their skill level. Second it shows that they have enough interest in development to want to become better. If you want a shot at something, show that you deserve it.&#8221;</p>
<p>I think that is completely incorrect.  I have ALWAYS been a very motivated individual when it comes to trying to succeed at something that I have set my mind on.  I have also always heard companies offering lip service saying that they really want someone who is junior and eager to learn, before I interview with them.  However, I have also been told, on a few occasions, that the companies love my skills and they absolutely loved the ambition i showed during the interview process.  However, they simply found someone who was &#8220;more senior&#8221; to fill the position.  In those situations, I do not think there was anything i could have done to get those positions, even though they intially said they were not looking for someone senior.  I have even been in situations where I have gone through the employers&#8217; headhunter, made it through 3 sometimes 4 rounds of interviews, passed the tests and everything.  Then have the manager of the company call me personally, expressing regret b/c although I was exactly what they SAID they wanted and sometimes MORE, they eventually found someone that was simply more experienced than I.</p>
<p>Maybe it&#8217;s just me.  Maybe I have simply had a lot of back luck finding a truly good place to work in the past (I LOVE my current job).  Maybe, quite frankly, maybe I just wasn&#8217;t as motivated in the past as I am now.  HOWEVER, I strongly strongly strongly do not believe that is the case.  And I strongly strongly strongly believe that I am far from alone; in fact, I honestly feel that many devs who have gone through alot of interviews would share my viewpoint.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-133</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 04 Feb 2011 20:05:15 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-133</guid>
		<description>Great read, would like to see some of the questions your ask and a little on how you structure the interview. I am trying to fill a position and feel I must not be asking the right questions enabling the interviewee the chance to shine. </description>
		<content:encoded><![CDATA[<p>Great read, would like to see some of the questions your ask and a little on how you structure the interview. I am trying to fill a position and feel I must not be asking the right questions enabling the interviewee the chance to shine. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KevDog</title>
		<link>http://lostechies.com/rayhouston/2011/02/04/thoughts-on-hiring-developers/#comment-132</link>
		<dc:creator>KevDog</dc:creator>
		<pubDate>Fri, 04 Feb 2011 19:56:30 +0000</pubDate>
		<guid isPermaLink="false">/blogs/rhouston/archive/2011/02/04/thoughts_2D00_on_2D00_hiring_2D00_developers.aspx#comment-132</guid>
		<description>I don&#039;t have the link handy, but in general you are incorrect that lower skilled individuals are being brought on. Unless people match the req exactly, people don&#039;t even pass the resume screen. 

Everyone wants to hire a senior (whatever that means) developer and no one wants to train juniors. Sort of self-defeating, don&#039;t you think?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t have the link handy, but in general you are incorrect that lower skilled individuals are being brought on. Unless people match the req exactly, people don&#8217;t even pass the resume screen. </p>
<p>Everyone wants to hire a senior (whatever that means) developer and no one wants to train juniors. Sort of self-defeating, don&#8217;t you think?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
