Earlier quoted context omitted.
> To play devil's advocate, having a standardized process for all candidates has some benefits. I've witnessed otherwise stellar candidates with amazing open source contributions absolutely bomb coding interviews. Real "write a function that does X" in whatever language you're comfortable with and whatever tools or resources you want. Simple stuff. I'm not sure if you're playing devil's advocate very well here, becau…
> I'm not sure if you're playing devil's advocate very well here, because this suggests to me that the interview process did not work well. Do you want to hire someone who can write a binary tree insertion in 30 minutes, or someone who can make amazing contributions to real software projects? Most companies want malleable, fungible engineers. Most companies are not stable, something is usually in flux -- projects, te…
When I'm acting as a hiring manager for a role, I read through applicant's materials in detail before deciding whether to advance them in the process. It's at least 50% of my work time, and my technical work suffers. I communicate that to the relevant managers and stake holders, and they can help decide whether it's the best use of my time.
I also regularly receive followup emails from rejected candidates saying that they thought the interview was the most fair and thorough of anywhere they applied, they understood why they didn't get the job, and in the process they learned where they need to focus on to be a better fit for the same type of role in the future.