I need to hire an electrician to do some work on my house.
This is going to be my process for finding the BEST candidate to work on my house
10:18 AM - 30 Sep 2019
509
1292
What I dislike the most of the current way of doing recruiting in tech companies(small ones) is the step where the candidate is given a mini project to do in 2-3 days.
I dislike it because I've been in both sides. Giving a take home assignment to a candidate and doing lots of them(in 2018 I think I did 4-6 just in four months)
When and where this kind of recruiting started? Why are we somehow pressured to have side projects to have a GitHub portfolio?
Just until recently, I've been trying to understand why this part of the process is done this way and how to improve it:
Technical interview with a questionnaire(from basic to advanced questions)
Two paid weeks/months doing real work(this would need a pre-selection process to not hire too many false positives)
Any ideas?
How do you feel about Data Structure / Algorithm challenges people have to pass through to prove you know what you're doing?
I think they're OK if the job one is going to do requires them A LOT. If you're building web forms for not life critical web apps, they shouldn't matter in an interview.
Care to share your experience?
The process I've liked more and felt comfortable were the ones where I could speak to current developers of the companies I was applying for. They would ask technical questions and sometimes they would from me and viceversa.
With an interview this way they were able to figure out, up to some degree, how fit I was.
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.
What I dislike the most of the current way of doing recruiting in tech companies(small ones) is the step where the candidate is given a mini project to do in 2-3 days.
I dislike it because I've been in both sides. Giving a take home assignment to a candidate and doing lots of them(in 2018 I think I did 4-6 just in four months)
When and where this kind of recruiting started? Why are we somehow pressured to have side projects to have a GitHub portfolio?
Just until recently, I've been trying to understand why this part of the process is done this way and how to improve it:
Any ideas?
I think they're OK if the job one is going to do requires them A LOT. If you're building web forms for not life critical web apps, they shouldn't matter in an interview.
The process I've liked more and felt comfortable were the ones where I could speak to current developers of the companies I was applying for. They would ask technical questions and sometimes they would from me and viceversa.
With an interview this way they were able to figure out, up to some degree, how fit I was.