2 ms·
My experience lately has been that yes "full" is expected even though its not specified as such. What I mean is some recruiter will say "we would like you to c
by bogomipz 9y ago
My experience lately has been that yes "full" is expected even though its not specified as such.
What I mean is some recruiter will say "we would like you to complete a coding challenge it shouldn't take any more than 2 hours to complete.' Then the feed back will come back that "the team was disappointed that you didn't implement features x, y and z."
The whole homework/project/coding challenge requirement has really become disrespectful in my opinion. Extremely vague requirements, arbitrary or unrealistic time constraints and then you are judged but not allowed to participate in any discussion about the code you produced.
And perhaps the height of absurdity is recruiters asking via email if you will complete a coding assignment. This is even before speaking to a human being to see if there might even be a fit.
The hiring process just seems to be becoming more broken all the time. Just refuse and say "No."
I think companies might really benefit from smoke testing their own hiring process in some blind fashion.