|
|
|
|
|
by 7Figures2Commas
4654 days ago
|
|
1. Write program that prints prime numbers below 100. 2. ? 3. Profit! Interviews are a two-way street. If you're looking to hire an experienced developer and the best you can do is ask him to do something that he'll probably never have reason to do on the job, you're sending a pretty strong message about your company. If you're going to ask somebody to code (or solve a problem) as part of the interview process, there's nothing worse than being lazy in creating the task. "Print prime numbers below 100" falls under the lazy category. |
|
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!