|
If the best you can do is to set a trivial programming problem, then indeed, that is deeply unimpressive. Happily, that is not what the article is suggesting, nor what anyone actually does. The article gives three steps: first, a trivial programming problem, second, a challenging programming problem (here delivered as homework), and thirdly, a face-to-face interview to check cultural fit. The purpose of the trivial problem, as explained in the article, and explained by anyone else who has ever advocated this approach, is simply to weed out people who just cannot code at all, and to do that early and cheaply. My current employer uses a trivial programming problem like this as an early screen (it comes after our recruitment guy has read their CV, but before we put them on the phone with a developer). Therefore, i, and many of my colleagues, are experienced developers who have been given a trivial programming problem to solve. It did not any of us a message which put us off the company. I have not heard of anyone being asked to do this test and losing interest in working for us as a consequence. On the contrary, i was pleased when i was given the problem as an initial screen, because it told me that the company was serious about hiring people who can actually code, which puts them head and shoulders above many employers! |
I see lots of references to "culture" in hiring comments, so I'm not trying to call you specifically out, but what does it mean? It always bristles me, like if your criteria is "white men only need apply" well just outright say it, don't tiptoe around it. As a suggestion to anyone on HN who does hiring, if for example you're not going to hire my wife because of her ethnicity or because she's a woman, just put it in the job ad and save everyone involved a lot of time and tiptoeing around "culture".