I interview people remotely all the time. We allow people to go through Coderpad or something like that, but in practice, I always suggest screensharing. The r

I interview people remotely all the time. We allow people to go through Coderpad or something like that, but in practice, I always suggest screensharing. The reason I suggest this is not that I am interested in the rest of their computer: I don't want keyboard or mouse control, and our rubrics have absolutely nothing to do with what else is running your box. What I am interested in is letting the candidate work with their favorite tools. It's your computer, with your favorite editor, with whichever bindings you have, and whichever libraries added to your project as you like to use. In our interviews you can also check language docs and stack overflow if you like: In fact, it's pretty common for people that pass the interview to do so. Interviewing is stressful, and other than letting people work on a longer interview project on their own time, the best thing I can do for my candidates is to make them be at ease in every other way possible. In case people worry about privacy, I am happy if they just share a window, especially if it's for an IDE that lets them both see the code and show me test results at the same time. So In my employer's case, a preference for screensharing is not really about treating people like cattle. We discuss all those pros and cons with candidates prior to screening, and accommodate them in almost every case. While I'd agree 100% that the ProctorU plan wound not be something I'd find acceptable, there's a great case for wanting access to your screen that is for the candidate's benefit.