<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kyle Cordes</title>
    <description>The latest articles on DEV Community by Kyle Cordes (@kylecordes).</description>
    <link>https://dev.to/kylecordes</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F192886%2F1817a6a9-c760-4331-858c-497c47c8ea90.jpeg</url>
      <title>DEV Community: Kyle Cordes</title>
      <link>https://dev.to/kylecordes</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kylecordes"/>
    <language>en</language>
    <item>
      <title>Hiring and interviewing developers</title>
      <dc:creator>Kyle Cordes</dc:creator>
      <pubDate>Sun, 21 Jul 2019 03:36:40 +0000</pubDate>
      <link>https://dev.to/kylecordes/hiring-and-interviewing-developers-3agb</link>
      <guid>https://dev.to/kylecordes/hiring-and-interviewing-developers-3agb</guid>
      <description>&lt;p&gt;I wrote this as a series of tweets, but perhaps here's a better place to capture it for the long term.&lt;/p&gt;

&lt;p&gt;I've been researching and experimenting with hiring+interviewing techniques. Might as well jump on this current “10X” bandwagon, eh? Here is some of what I’ve learned. (Context: I mostly hire software developers, but also other roles.)&lt;/p&gt;

&lt;p&gt;No matter what words are or are not in a job posting, a large number of people who plainly do not match the job at all will apply.&lt;br&gt;
~Every company hires only the best people. Mysteriously, the economy is nonetheless at only a few percent unemployment.&lt;/p&gt;

&lt;p&gt;Many experts advocate spending hours digging into inappropriately internal details of past employers. Mysteriously, all then expect the new hire to keep their confidences.&lt;/p&gt;

&lt;p&gt;Many experts advocate their particular style of interview as the obvious best. But anyone can go on YouTube and learn how to game any popular interview style.&lt;/p&gt;

&lt;p&gt;Many experts’ basic idea is “past performance equals future results”. You can pay a lot of money for that advice. About a hypothetical world in which people do not grow or change.&lt;/p&gt;

&lt;p&gt;Many companies interview software developers with doofus second-year-CS questions. Apparently they do this out of habit, because it seems to reveal little about job performance.&lt;/p&gt;

&lt;p&gt;Time is precious. Have a time budget, and stick to it ruthlessly. Interruption may be necessary.&lt;/p&gt;

&lt;p&gt;For technical work, do you want to hire people good at talking about X or doing X? If the latter, find a way to "audition".&lt;/p&gt;

&lt;p&gt;Lots of applicants want to "hop on a call". Time is precious. Exchange some info first, use that to decide whether to interview. Then meet with an agenda, via a video chat for more complete communication.&lt;/p&gt;

&lt;p&gt;Questions with one right answer aren't that useful. Questions that reveal skill and experience levels are very useful.&lt;/p&gt;

&lt;p&gt;That's it for now. If you liked that and are a software developer with deep Angular or other web platform skills, keep an eye on our careers page. oasisdigital.com/careers&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
