<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 18 Jun 2013 02:34:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Nick Halstead's Blog: Interviewing Programmers 101 - Part 3]]></title>
      <guid>http://www.phpdeveloper.org/news/8459</guid>
      <link>http://www.phpdeveloper.org/news/8459</link>
      <description><![CDATA[<p>
<i>Nick Halstead</i> has <a href="http://blog.assembleron.com/2007/08/13/interviewing-programmers-101-part-3/">posted part three</a> of his series looking at interviewing programmers (here's <a href="http://www.phpdeveloper.org/news/7855">part one</a> and <a href="http://www.phpdeveloper.org/news/7893">part two</a>) with more of a focus on the details of the individual including their knowledge of code and general abilities.
</p>
<blockquote>
In the murky past I wrote two article about interviewing programmers. The <a href="http://blog.assembleron.com/2007/05/15/interviewing-programmers-101-part-1/">first</a> covered the basics of interviewing itself and gave (hopefully) a good grounding for those who have never had to interview before. The <a href="http://blog.assembleron.com/2007/05/21/interviewing-programmers-101-part-2/">second</a> was all about the kind of testing you can do to filter out candidates before you commit to doing a full interview. [...] At the time I then promised to write a third section on what types of tests to use during the interview. Well I finally got round to finishing it off.
</blockquote>
<p>
This time, he <a href="http://blog.assembleron.com/2007/08/13/interviewing-programmers-101-part-3/">suggests things</a> like specific language testing for your company's language of choice, an IQ test, seeing how they "pseudo code" and some psychometric testing. Basically, this boils down to measuring both the individuals potential and how good they will be in the position you're interviewing for.
</p>]]></description>
      <pubDate>Wed, 15 Aug 2007 11:14:00 -0500</pubDate>
    </item>
  </channel>
</rss>
