I agree with you, technical tests do reflect on the company asking for them to be completed; Last year I interviewed with a place that sounded very good but after being given an example of the type of websites they build and being asked to make changes it really put me off wanting to work for them due to the very strange way it was put together and usage of the technologies involved.
As a candidate I prefer if there are no technical tests, as you say they are very time consuming, especially if you have multiple job opportunities in progress. I also feel that being a senior dev who is pretty happy in my current role its up to companies to lure me away from the current place, and expecting me to run through a convoluted recruitment process with lots of interviews and technical tests is a big turn off. Easier to stay where I am.
The best places I have interviewed at did not require technical tests, but instead got me to show and discuss projects worked on in the past while asking me lots of questions about it, and to provide links to repositories on Github so they can have a look and see my coding style is OK. They would of course also ring and talk with the references I provided.
If I have to do a test, I prefer a small practical project I can work on at home and then submit to them. I often have so many questions when interviewing at places that a technical test during the interview does not work so well as the brain is not in the right mindset.
Lastly, that 50min multi-choice test you mention sounded crazy. Does not reflect well on the company at all.
I absolutely agree - I'd prefer there to be no technical tests and a discussion around highlighted projects works a lot better and should give a company a far better view on the applicant's understanding. I should have discussed that in the article.
Generally, I have been amazed that the variety processes some companies have in place to recruit senior developers where they feel they can be confident of the successful applicant's ability at the end of it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree with you, technical tests do reflect on the company asking for them to be completed; Last year I interviewed with a place that sounded very good but after being given an example of the type of websites they build and being asked to make changes it really put me off wanting to work for them due to the very strange way it was put together and usage of the technologies involved.
As a candidate I prefer if there are no technical tests, as you say they are very time consuming, especially if you have multiple job opportunities in progress. I also feel that being a senior dev who is pretty happy in my current role its up to companies to lure me away from the current place, and expecting me to run through a convoluted recruitment process with lots of interviews and technical tests is a big turn off. Easier to stay where I am.
The best places I have interviewed at did not require technical tests, but instead got me to show and discuss projects worked on in the past while asking me lots of questions about it, and to provide links to repositories on Github so they can have a look and see my coding style is OK. They would of course also ring and talk with the references I provided.
If I have to do a test, I prefer a small practical project I can work on at home and then submit to them. I often have so many questions when interviewing at places that a technical test during the interview does not work so well as the brain is not in the right mindset.
Lastly, that 50min multi-choice test you mention sounded crazy. Does not reflect well on the company at all.
I absolutely agree - I'd prefer there to be no technical tests and a discussion around highlighted projects works a lot better and should give a company a far better view on the applicant's understanding. I should have discussed that in the article.
Generally, I have been amazed that the variety processes some companies have in place to recruit senior developers where they feel they can be confident of the successful applicant's ability at the end of it.