<?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>Sun, 12 Feb 2012 19:54:51 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[php|architect Blog: Confessions of a Hiring Manager: Get my attention, Get a Job]]></title>
      <guid>http://www.phpdeveloper.org/news/12769</guid>
      <link>http://www.phpdeveloper.org/news/12769</link>
      <description><![CDATA[<p>
If you're a developer out there and are looking for that next job (contract or otherwise), you might check out <a href="http://phparch.com/main/news/view/25">this advice</a> from <i>Cal Evans</i> as to what he, a hiring manager in the past, has looked for in a developer's resume.
</p>
<blockquote>
am often asked to take a look at friends resume to give pointers on how that can make it more effective. Invariably, my advice is the same, so I'll share it here. When I was a manager and in charge of hiring, your resume had to get my attention for me to even consider it. If you got my attention, you had a much better chance at getting the job. That's the secret: get my attention, and get the job.
</blockquote>
<p>
He points out that the usual situation is one manager to a large group of applicants. You may see the job post once, but so do 30 other people and you're all trying to grab attention. What's his recommendation? Brevity. Keep the first page short then dive deep behind that. There's more great tips in the rest of <a href="http://phparch.com/main/news/view/25">the post</a>.
</p>]]></description>
      <pubDate>Fri, 26 Jun 2009 17:32:31 -0500</pubDate>
    </item>
  </channel>
</rss>

