[nscalf]

I think ultimately the problem I haven’t isn’t that I have been assigned a problem to see my code skill. I think that’s pretty fair. The problem is that it’s not a great indicator if your beyond a staff level, it offloads all of the cost of finding and filtering an employee to the applicant, and like you said, it has no indication of their commitment to the code challenge while demanding an open ended commitment from the applicant.

[wildrhythms]

I actually turned down a job, whose hiring manager was very excited (or desperate) to have me, after the recruiter sent me a link to a coding challenge. I felt devalued, that they didn't value my time, and I felt turned off realizing that this coding challenge was the only hurdle for engineers on that team. Note that I wasn't a fresh grad or anything, I had years of experience at this point from, what I assume was at the time, one of their big competitors.

Since the company can't make time for a potential "experienced candidate" (their words) during the hiring process, I wonder what else they can't make time for? Red flag for me.

[busterarm]

You're in the rare camp that realized this. Thanks for doing me and everyone else in this industry a solid.

Companies won't change until this is enough of a negative signal for them.

[tptacek]

The recruiter sent you a coding challenge? How far into the process could you have been?