<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Interviewing on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/interviewing/</link>
    <description>Recent content in Interviewing on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 08 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/interviewing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hiring for Values, Abilities, Then Skills</title>
      <link>https://www.secdev.uk/blog/leadership/3.2-hiring-for-values-abilities-then-skills/</link>
      <pubDate>Mon, 08 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/3.2-hiring-for-values-abilities-then-skills/</guid>
      <description>&lt;p&gt;Most engineering interviews are backwards. We spend the majority of our time evaluating technical skills, the thing that&amp;rsquo;s easiest to teach and quickest to develop, and almost no time evaluating values and abilities, which are much harder to change and far more predictive of long-term success.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve made this mistake myself, repeatedly. I&amp;rsquo;ve hired brilliant engineers who turned out to be terrible collaborators. I&amp;rsquo;ve passed on candidates who weren&amp;rsquo;t the strongest technically but would have been exactly what the team needed. The more I&amp;rsquo;ve hired across start-ups and corporates, the more convinced I&amp;rsquo;ve become that we need to flip the order.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
