Take home interview programming tests

Published November 29, 2020

A few times in my career I've been invited to perform a take home programming test as part of an interview process.

So far, every time I've encountered this I've gone through a similar thought process that starts with me being initially open to the prospect and ends with me withdrawing my application before writing any code. My reluctance can be split into a few different points.

How long is this going to take?

It's obviously a bad sign if a company expects you to work for free, but I think most of us would agree that up to two hours of work is not completely unreasonable (assuming that it cuts out two hours of interview time).

So far I haven't been asked to produce a piece of work that would reasonably take less than two hours. They've all been in the 10+ hour range. That's not reasonable at all. It's very easy for someone to design such a test while being already familiar with, and having a development environment set up for, the particular technologies in question and to completely overlook the amount of time required before someone else would be in the position to even begin writing code.

What am I actually being assessed on here?

The implied criteria of assessing the test is that the candidate produces some 'sensible' code that does what it's supposed to. But without clear requirements, 'sensible' is a very subjective word.

Suppose there's an implied need for a data store. Am I going to get criticised if I use SQLite for speed of set-up instead of the full blown SQL Server installation that the employer uses? What if I decide that storage isn't really an important part of a demo application and just serialize to JSON and stick it in a file on disk? What about error handling; robust, production standard error handling can easily make simple blocks of code 3-4x as long as they'd otherwise be; if I skip this will I be opening myself up to criticism? If I implement it, will I be criticised for over-engineering?

Without clear requirements it's difficult to reliably produce a piece of software that does what it's supposed to. This is a basic tenet of professional software development.

So far, I'm yet to see a take home assessment that has clear requirements. If we need to start going back and forward to clarify the requirements, this firstly takes up additional time, and secondly implies the test isn't being administered to a professional standard.

How does this make me feel?

An interview is a two way process, and a mutual investment of time. The company invests its time, as do I. A take home programming test is not mutual. The company expects the candidate to put in time, but the company isn't investing in the process at all. If the company isn't investing its resources into hiring a candidate, why would the candidate feel that pursuing the matter further is an effective use of their time?

Filed under: employment, recruitment

Talk is cheap

Leave a comment:

HTML is not valid. Use:
[url=http://www.google.com]Google[/url] [b]bold[/b] [i]italics[/i] [u]underline[/u] [code]code[/code]
'