Answer the question
In order to leave comments, you need to log in
Can you estimate the time in hours for a Ruby test task?
Gentlemen, we have prepared two test tasks for finding a Ruby middl backender for the team. But they did not agree on the assessment of labor costs for the performance of tasks by candidates. Someone thinks that both tasks are 2-3 hours, someone says that the first task will take at least 8 hours, and the second about 4.
Please look at the tasks at the link and write your estimate in hours for each of the two tasks . So we will come to the truth) Ideally, we want the first task to take about 3 hours, and the second - about 1-2 hours.
Answer the question
In order to leave comments, you need to log in
8 hours for the first is an extremely optimistic forecast, if done normally.
Such a task should be paid to candidates, regardless of the success of its implementation.
The first task is unsuccessful for the middle. It is trivial, but at the same time voluminous. At least 8 hours, if you do the norms (with tests, with patterns at least at the level of service objects). For 2-3 hours there will be a govnokod. This is a job for Jun. If it is not paid, then the middle will pass further by this vacancy.
The second task is already normal, and I would suggest it for the middle. It can be directly on social security (speculate about implementation options).
Weird question.
It all depends on the experience and skills of the programmer. One will do it in two hours, the other will sit for a week.
And the third one will raise a copy or an analogue of this task and copy-paste it in a couple of minutes
A self-respecting middle will not do your test tasks at all. Invite to the office and give a real problem that can be solved in 1-2-3 hours. So you will immediately see what tools he uses, where he looks and how he generally works. And it will be better than 100-500 test items.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question