Should Taki tests (for admission to work) be paid by a potential employer?
In one of the posts this thought recently flashed habrahabr.ru/blogs/arbeit/106832 - whether the test tasks should be paid or not.
My opinion is that test items should NOT be paid (more precisely, such a problem should not arise at all), and for what reason.
Test task must be
- focused on some area (for example, algorithms on graphs, application layer network protocols on top of TCP-IP and their implementation, designing a database scheme for a specific, clearly described task),
- be clearly delineated, and do not include work on such things as documentation, TK, requirements, well-configured environment for the assembly (scripts, etc.). it must be CODE. 50-200-500 lines of code solving a specific task. do THAT and THEN. point.
- and to be aimed at ensuring that a candidate could demonstrate his approach (in practice, not in words a la - “I always write perfectly formatted and commented code, and I run each method through a static codec and profiler before a commit, I just can’t otherwise, even in the most intense conditions! ”)
- it should be INTERESTING enough that no thoughts arise - “what the fuck am I supposed to do this murk, and even free of charge”. The idea should be - “Oh, an interesting task, I haven't come across such a long time ago. And then you can then discuss it in detail with smart people. ”
- Like some resume - test task should be applied on say, 10% of all technical positions. There, where actually nontrivial tasks (first of all algorithmic / other, demanding writing of the nontrivial difficult CODE). At the position of say, in the projects involved in ERP systems, test tasks I think in most cases are superfluous.
')
For what, it must be carefully thought out, and it takes no more than a day and a half to take a candidate’s job. That is, it can be done in a few evenings. In this case, if the candidate refuses, he is the GVHB, and I would not pay him.
WHEREIN.
The test task should not involve the development of a site from scratch, a finished small product, writing project documentation. It takes a lot of time, it's a routine, VERY few people will do this at all, and if you even want to pay for it, this is not a test task, but another part-time hack. With the appropriate attitude towards her.
(Perhaps Google, Facebook and others like them can afford it. When there are 200 strong candidates in your company for 10 positions Signor developers, 50 of them are gurus, 20 of them are passionate people, ready for any conditions, you can also: ))
As an example (I do not work in Yandex, so this is not an advertisement :)) I came across problems that Yandex offers to candidates for some developer positions.
Example: company.yandex.ru/job/vacancies/dev_media_java.xml
This is for me an example of what the test tasks should be. There is far from everywhere you even need to write some kind of code (for example, it is often necessary to set out in detail some subtlety, for example, the Java Memory Model, or to show your approach to the solution - but these are INTERESTING tasks. make them qualitatively, "as it should."
My opinion is that test items should NOT be paid (more precisely, such a problem should not arise at all), and for what reason.
Test task must be
- focused on some area (for example, algorithms on graphs, application layer network protocols on top of TCP-IP and their implementation, designing a database scheme for a specific, clearly described task),
- be clearly delineated, and do not include work on such things as documentation, TK, requirements, well-configured environment for the assembly (scripts, etc.). it must be CODE. 50-200-500 lines of code solving a specific task. do THAT and THEN. point.
- and to be aimed at ensuring that a candidate could demonstrate his approach (in practice, not in words a la - “I always write perfectly formatted and commented code, and I run each method through a static codec and profiler before a commit, I just can’t otherwise, even in the most intense conditions! ”)
- it should be INTERESTING enough that no thoughts arise - “what the fuck am I supposed to do this murk, and even free of charge”. The idea should be - “Oh, an interesting task, I haven't come across such a long time ago. And then you can then discuss it in detail with smart people. ”
- Like some resume - test task should be applied on say, 10% of all technical positions. There, where actually nontrivial tasks (first of all algorithmic / other, demanding writing of the nontrivial difficult CODE). At the position of say, in the projects involved in ERP systems, test tasks I think in most cases are superfluous.
')
For what, it must be carefully thought out, and it takes no more than a day and a half to take a candidate’s job. That is, it can be done in a few evenings. In this case, if the candidate refuses, he is the GVHB, and I would not pay him.
WHEREIN.
The test task should not involve the development of a site from scratch, a finished small product, writing project documentation. It takes a lot of time, it's a routine, VERY few people will do this at all, and if you even want to pay for it, this is not a test task, but another part-time hack. With the appropriate attitude towards her.
(Perhaps Google, Facebook and others like them can afford it. When there are 200 strong candidates in your company for 10 positions Signor developers, 50 of them are gurus, 20 of them are passionate people, ready for any conditions, you can also: ))
As an example (I do not work in Yandex, so this is not an advertisement :)) I came across problems that Yandex offers to candidates for some developer positions.
Example: company.yandex.ru/job/vacancies/dev_media_java.xml
This is for me an example of what the test tasks should be. There is far from everywhere you even need to write some kind of code (for example, it is often necessary to set out in detail some subtlety, for example, the Java Memory Model, or to show your approach to the solution - but these are INTERESTING tasks. make them qualitatively, "as it should."
Source: https://habr.com/ru/post/107641/
All Articles