<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jim Kirkbride on Medium]]></title>
        <description><![CDATA[Stories by Jim Kirkbride on Medium]]></description>
        <link>https://medium.com/@jim.kirkbride?source=rss-12637916306a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cSpczdlfL-QJ1fbkVdJtog.png</url>
            <title>Stories by Jim Kirkbride on Medium</title>
            <link>https://medium.com/@jim.kirkbride?source=rss-12637916306a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:58:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jim.kirkbride/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Beam Prefers Take-Home Tests]]></title>
            <link>https://medium.com/beambenefits/why-beam-prefers-take-home-tests-60e92d20f0a3?source=rss-12637916306a------2</link>
            <guid isPermaLink="false">https://medium.com/p/60e92d20f0a3</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[interviewing]]></category>
            <dc:creator><![CDATA[Jim Kirkbride]]></dc:creator>
            <pubDate>Fri, 22 Jan 2021 13:03:05 GMT</pubDate>
            <atom:updated>2021-01-22T13:03:05.298Z</atom:updated>
            <content:encoded><![CDATA[<h4>… and Why Algorithmic and Whiteboard Questions Don’t Work for Us</h4><figure><img alt="Why Beam Prefers Take-Home Tests Over Algorithmic Interview Questions" src="https://cdn-images-1.medium.com/max/1024/1*WuoIg0b8mUMoBZVEYI_K7w.png" /></figure><p>How to evaluate a candidate’s technical aptitude is hotly debated from company to company. Every organization has its reasons for including particular evaluation steps in its hiring process. Some opt for algorithmic-based questions or whiteboard sessions while others ask candidates to take an online assessment quiz or complete a take-home project.</p><p>Maybe you’re having the same discussion in your organization. If so, then this article is for you.</p><p>At Beam, we eschew the algorithmic questions and whiteboard sessions in favor of take-home tests for a number of reasons. Let’s talk about why. Who knows, maybe this will prompt you to reconsider your own hiring practices!</p><h3>The case against algorithmic and whiteboard interview questions</h3><h4>Real talk time about algorithms</h4><p>The vast majority of the time you’re not going to need them. Are you creating your own programming language, working with vast amounts of data, or writing code that is close to the hardware? If you’re applying to one of these roles then yes, you probably <strong>do</strong> need to have an understanding of the underpinnings of sorting algorithms, and maybe you do need to write these algorithms from scratch.</p><p>While these roles might require intimate knowledge of algorithms, most roles in the industry do not. You’ll gain more bang for your buck by focusing on solid (and maybe even <a href="https://en.wikipedia.org/wiki/SOLID">S.O.L.I.D.</a>) software development principles, having a working understanding of common data structures, and testing than you will from knowing how to implement a quicksort or A* algorithm.</p><p>Many of our engineers at Beam don’t come from a traditional 4-year Comp Sci program and aren’t able to rattle off implementations from an Algorithms and Data Structures class. However, this does not define the value of their contributions in our organization. Your “standard” software dev role that is primarily focused on feature development and delivering working code doesn’t require deep algorithmic knowledge. In actuality if you were to implement your own sorting algorithms from scratch, you’re likely to see some head-scratching during code reviews, with your fellow devs asking you why you didn’t just use the standard library implementations.</p><h4>They encourage unrealistic evaluation metrics</h4><p>Some advocates of algorithmic and whiteboard questions make the argument that they help to show how candidates perform under stress or how candidates communicate about a problem. Emotional Intelligence (EQ) is important for sure, but there are better ways to evaluate this quality in candidates.</p><p>The problem with this stance is that this is not how modern software development occurs which in turn means you’re evaluating candidates on a false metric. Many candidates aren’t comfortable performing new (or even familiar) skills on-the-spot in a public setting. However, given a realistic time frame and environment, they demonstrate that they are indeed excellent problem-solving programmers.</p><p>To drive this home further, consider also the amount of prep time candidates spend on these questions. Entire cottage industries have sprung up around how to prepare for algorithmic questions, whiteboard sessions and other “out of the box thinking” activities. Candidates have been known to spend hours or even days preparing for these questions. This kind of intensive practice adds another layer of both financial and time management stress for candidates who have other obligations outside work as well as family.</p><p>In my entire 12 year career as a software developer I’ve never once been asked to implement a specific algorithm without looking it up, or to architect a solution to a real-world problem on the spot in front of a group of semi-hostile observers. I <strong>have</strong> on the other hand frequently been asked to come up with a solution to some problem or another which required taking some time to think through the problem, consult with other team members, garner consensus, and come up with a plan of attack.</p><p>Good software takes time to develop, good architecture takes time to emerge, and good organizations avoid high-stress situations when possible. Even roles that require algorithmic thinking have more to do with collaborative problem-solving than memorization of a specific algorithm or on-the-spot whiteboard solution.</p><h4>They encourage bias in the hiring process</h4><p>Algorithmic questions bias towards certain backgrounds on the basis that candidates with these backgrounds are more likely to be able to answer algorithmic questions. Specifically, they tend to focus on candidates with four year degrees in Computer Science from prominent (and expensive) universities while ignoring the shifting demographics of software development as candidates enter the field from bootcamps, certificate programs, or self-instruction.</p><p>These new career paths are opening doors that have <a href="https://codeorg.medium.com/women-computer-science-graduates-finally-surpass-record-set-17-years-ago-20a79a76275">otherwise been closed or difficult to pass through</a> for individuals from diverse and under-represented backgrounds. Candidates on these paths are more focused on the nuts and bolts of creating software in an industry that needs them to be productive immediately and to be able to create working solutions as soon as they enter the workforce. Excluding candidates from different backgrounds means losing out on diversity of thought, skill, and problem solving abilities.</p><h3>The case for the take-home test</h3><figure><img alt="The case for the take-home test" src="https://cdn-images-1.medium.com/max/1024/1*sBYsj4oRyt1JGO3fSOiwZA.png" /></figure><h4>They align more realistically with how most software is created today</h4><p>There are many variations of the take-home test, but most of them involve being given a problem of some manageable complexity and implementing a solution within a given timeline and some guidelines. This most closely mimics software development tasks in real-world organizations and allows developers to demonstrate their technical chops as well as how they problem solve. If the goal is to evaluate how a candidate will perform on a daily basis, then this is exactly what we want.</p><p>Well-designed take-home tests should provide enough of an empty canvas to enable candidates to show what they are capable of while allowing interviewers to evaluate candidates’ technical knowledge and skill with a language or framework.</p><p>As interviewers, we can see how a candidate handles certain aspects of a project. How well do they implement the requirements? Do they write tests? How do they architect solutions? Do they ask questions when they don’t know the answer? These metrics are far more informative and realistic than purely algorithmic-based questions or high-pressure whiteboard sessions.</p><h4>They can remove bias from the hiring process</h4><p>By removing the artificially high bar of algorithmic questions and whiteboard sessions that bias towards candidates from prominent four year colleges, we can open the door to a more diverse set of candidates, including those with economically diverse backgrounds that started their careers on a non-traditional route.</p><p>To be clear, this is not “lowering the bar” or “catering to the lowest common denominator.” Rather, we’re setting realistic expectations and opening up new hiring pipelines for entire pools of talented candidates. By providing a take-home test that is focused on solving the kind of problems we work with on a daily basis, we level the playing field for all of our candidates.</p><p>At Beam, we take removing bias a step further and enable candidates to submit <a href="https://medium.com/beamdental/how-we-anonymized-candidate-code-submissions-and-how-you-can-too-fb5aa2629fb3">anonymized solutions</a> for evaluation, allowing the solution to be evaluated based on its technical merits alone rather than allowing the evaluator’s own biases (conscious or unconscious) to affect hiring decisions. This anonymization takes effort but is well worth the time to make the hiring process more fair and inclusive.</p><h4>They remove stress from the hiring process</h4><p>Beam provides a realistic amount of time for candidates to work on a take-home test at their own pace. This gives candidates the same advantages that we have in our day-to-day jobs and encourages them to put forward their best effort.</p><p>Take-home tests with short turn-around times can encourage candidates to become stressed and rush through solutions which hurts the candidate’s chances at producing a good solution as well as the interviewers’ abilities to evaluate what the candidate is actually capable of.</p><p>While the take-home tests themselves do have the potential to be time-consuming (Beam expects that a test can take between 4 and 12 hours to complete), the prep time is generally negligible. There are no arcane topics to research, no <em>“Top 10 Algorithm Questions (Wait till you see #9!)</em>” blog posts to review, and no rehearsing in front of a mirror (at least for this part of the interview). You simply do what you were trained to do: solve problems in code.</p><p>The take-home test also becomes a point of discussion later in the hiring process which allows interviewers to ask about architecture decisions, the candidate’s experience with the tools, and to clarify any outstanding questions about the candidate’s solution. The candidate can likewise ask questions and provide feedback about the test. By allowing the candidate to work at their own pace and making the end result part of a conversation we reduce the overall stress of the interview process.</p><h3>Conclusion</h3><p>Ultimately, whether or not you use a take-home test as part of your hiring process really depends on your culture and engineering values. At Beam we try to be pragmatic, team-oriented, and inclusive when it comes to solving tech problems. In this regard the take-home test serves our hiring needs better than algorithmic questions and whiteboard sessions. If this resonates with you, consider reassessing your own hiring practices and whether they reflect your organization’s values. Even better, come talk to us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e92d20f0a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beambenefits/why-beam-prefers-take-home-tests-60e92d20f0a3">Why Beam Prefers Take-Home Tests</a> was originally published in <a href="https://medium.com/beambenefits">Beam Benefits</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>