Earlier quoted context omitted.
"Difficult to work with" is perhaps too harsh a statement. But the candidate is asking for a completely custom treatment at the earliest possible stage of the interview process. The candidate is also assuming that the interviewers aren't aware of the caveats mentioned about standard coding screens/HackerRank exercises. The candidate's proposal also doesn't mirror real-world conditions, because I doubt the job consist…
> just a low-investment screen Low-investment on the part of the employer. They still expect me to spend 90 minutes on proving I have seen a REPL before, which is time I, frankly, don't have. I'm happy to answer/talk about things that relate to my job, but working on puzzles that just happen to be solved more easily by programming has exactly nothing to do with it. > the candidate is asking for a completely custom tr…
We actually take great care in examining resumes and CVs before proceeding with a coding screen. We've had plenty of senior developers fail the most basic questions (think FizzBuzz), which is why we conduct these screens.