4 ms·
I am saving lots of developers hours. I am saving critical developer hours during, say a launch, when you had to keep your candidate search on hold. It has happ
by shail 13y ago
I am saving lots of developers hours. I am saving critical developer hours during, say a launch, when you had to keep your candidate search on hold. It has happened to me multiple times. I was waiting to hear back from companies while they were busy launching a product. In real world it happens a lot. I know I cannot do later rounds and they should be done by the team themselves but initial round can definitely be done by me. And finally, I am reducing their misses which results in saved developer time.
- furyofantares 13y ago> I am saving lots of developers hours I don't see how this is really true. You say an interview can use up 15-20 developer hours and in some percentage of the failure cases you are saving that (and hopefully not failing some percentage of the passing casses, btw.) My point is that if a 1-hour screening by a single developer is effective, I can keep it in-house and save 14-19 developer hours where you'd be saving me 15-20. I guess I am actually assuming you are only spending 1 hour with the candidate, you never say that above. But my point is, unless you are uniquely good at interviewing, the amount of time you are putting into interviewing the candidate is the amount of the you are saving me.