Developers’ pains when doing technical tests

The day has come, attention! After talking to many of you, devs, you have told us again and again about the same pains you have encountered when doing technical tests in recruitment processes.

And well, apart from working on it, we have nothing left to do but laugh about it . Check out here 10 developers' pains when doing technical test.

1. Tests that have absolutely nothing to do with the position you are applying for, bravo.

2. Tests longer than the Lord of the Rings Saga (but not as good)

3. Tests so specific and limited that they don't let you show your magic, great.

4. The evaluation criteria? They look like a state secret.

5. Blatantly boring tests, not even done on purpose.

6. Will the test creators read the test?

7. Feedback on the test result - what's that? Doesn't ring a bell.

8. Tests that don't allow feedback. Gambling it all on the code is not fair

9. Receiving a test and not knowing anything else about the company (hello darkness my old friend... )

10. 1 different test for each job you apply for. Worse than an escape room