{"id":14361,"date":"2021-03-08T22:03:36","date_gmt":"2021-03-08T21:03:36","guid":{"rendered":"https:\/\/www.toomik.net\/helen\/blog\/?p=14361"},"modified":"2021-03-08T22:03:36","modified_gmt":"2021-03-08T21:03:36","slug":"daily_2244_-_interviewing","status":"publish","type":"post","link":"https:\/\/www.toomik.net\/helen\/blog\/2021\/03\/08\/daily_2244_-_interviewing\/","title":{"rendered":"Daily: 2244 &#8211; interviewing"},"content":{"rendered":"<p><img decoding=\"async\" src=\"\/helen\/blog\/images\/daily_3\/2244_interview.jpg\" class=\"x45y6\" \/><br \/>\nPart of my job is doing recruitment interviews. I do them quite regularly &#8211; recently at least once a week. 1337 is growing and we want to hire more developers, and someone needs to interview them from a technical point of view. These days I do roughly one per week, and often get requests for more. It&#8217;s getting to the point where I have to say no because I can&#8217;t take that much time from my &#8220;real&#8221; work. But I enjoy them, so I do try to take the time.<\/p>\n<p>We&#8217;re a large enough firm to have specialists for the early phases &#8211; finding and winnowing out suitable candidates, and having a first interview with them. I&#8217;ve never enjoyed that part of the recruitment process so I&#8217;m glad that&#8217;s already done by the time I get involved.<\/p>\n<p>The second step is a technical interview, and that&#8217;s where I come in. The third and final step is a manager interview.<\/p>\n<p>In a tech interview, we spend one to two hours inventorying and mapping the candidate&#8217;s skills in a wide range of topics. We don&#8217;t usually dig into any one area in great depth, but we probe enough to get a good picture of where the candidate&#8217;s skills lie, and find out where there are gaps in their knowledge.<\/p>\n<p>These days we have a comprehensive template document listing all the areas to cover, each one with a set of keywords to help jog our memories. This is a relatively new &#8220;tool&#8221;. We&#8217;ve invested many laborious person-hours in internal workshops to prepare this interview guide, and then to get used to working with it, and now it&#8217;s really paying off. I&#8217;ve been doing interviews for many years and they&#8217;ve never been as focused and well-organized as what I&#8217;m doing now.<\/p>\n<p>We always do the tech interviews in pairs, which I really like. Not only is it good to always have a second opinion, but it also makes the interview run better. If I can&#8217;t think of a good follow-up question, my colleague is sure to have one.<\/p>\n<p>It&#8217;s easy, relatively speaking, to interview a developer who is supposed to be roughly at my own level of experience. I know what I would expect from another senior colleague. Does this person know enough to be able to deliver production-ready code? Do they have enough experience to make architecture decisions? Are they able to consider the bigger picture, the business needs, the trade-offs?<\/p>\n<p>It is much harder to interview a junior developer. Experience and knowledge can be judged more or less objectively. But judging potential is so much harder. How can I know what this person will be able to do in a few years? How much of their lack of knowledge today is due to lack of exposure, and how much is due to lack of initiative?<\/p>\n<p>I&#8217;m quite glad that the final decision is not mine.<\/p>\n<p>Despite all the digital tools we have, I always take notes with pen and paper. Nothing beats pen and paper when it comes to quick scribbles and unstructured comments.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Part of my job is doing recruitment interviews. I do them quite regularly &#8211; recently at least once a week. 1337 is growing and we want to hire more developers, and someone needs to interview them from a technical point of view. These days I do roughly one per week, and often get requests for [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18,4,768,13],"tags":[],"class_list":["post-14361","post","type-post","status-publish","format-standard","hentry","category-dailies","category-observing_the_self","category-photography-2","category-career"],"_links":{"self":[{"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/posts\/14361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/comments?post=14361"}],"version-history":[{"count":4,"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/posts\/14361\/revisions"}],"predecessor-version":[{"id":14365,"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/posts\/14361\/revisions\/14365"}],"wp:attachment":[{"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/media?parent=14361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/categories?post=14361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.toomik.net\/helen\/blog\/wp-json\/wp\/v2\/tags?post=14361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}