One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
It's neither right or wrong, it's an ethical question. I believe that "candidate experience" should not be just a buzzword but a reality. I believe companies should strive to not waste the time of even the candidates that end up not hiring.
Just to clarify, here I'm talking about coding challenge like "create a mobile app that will do xxx respecting all kind of best practices".
The thing is that 4 hours is not the actual time it takes for most candidates to do the coding challenge but the very optimistic very wrong time estimate from the guy who created the challenge. That guy has all the insights in mind so of course it takes even less than 4 hours for him, because programming is all about insights.
I'm glad that you can complete all those kind of challenges finger in the nose in 2 hours, but I know talented developers that would over engineer the shit out of that, going in a deep rabbit hole, and that's why I refuse to do those projects.
I think we're on the same page. We have the parameters. It's a matter of performing the calculation to say if it's worth it, not to take an unwavering stance without context or quantifiable value, even if the value is conditional.
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.
It's neither right or wrong, it's an ethical question. I believe that "candidate experience" should not be just a buzzword but a reality. I believe companies should strive to not waste the time of even the candidates that end up not hiring.
Just to clarify, here I'm talking about coding challenge like "create a mobile app that will do xxx respecting all kind of best practices".
The thing is that 4 hours is not the actual time it takes for most candidates to do the coding challenge but the very optimistic very wrong time estimate from the guy who created the challenge. That guy has all the insights in mind so of course it takes even less than 4 hours for him, because programming is all about insights.
I'm glad that you can complete all those kind of challenges finger in the nose in 2 hours, but I know talented developers that would over engineer the shit out of that, going in a deep rabbit hole, and that's why I refuse to do those projects.
I think we're on the same page. We have the parameters. It's a matter of performing the calculation to say if it's worth it, not to take an unwavering stance without context or quantifiable value, even if the value is conditional.