Scanning students' rooms during remote tests is unconstitutional, judge rules
npr.org
npr.org
how is a search that is limited not a search, and if it isn't coerced, what would happen if he didn't comply?
My car isn't a car because I only drive it around the block!
> what would happen if he didn't comply?
According to them, they would be unable to take the exam and therefore would not pass. Which means that the time and money spent on the course is wasted. Not coercive at all!
I did not go through with it.
Most of them use a second window to look up answers. This is pretty obvious, from watching them in the webcam, and where they pause. This is also easy to detect, since they'll fail with more abstract questions that don't have an answer you can just look up. For example, tell them to go deep into a project that they have on their resume. Nearly every time, they eventually say, directly or not, that their part was minimal. I don't think anyone has to worry about these people.
But, recently, one person almost made it all the way through, before getting to me. From what I can guess, they had someone in a separate video call, watching the screen and listening to the interview, giving them the answers. I think a language barrier, for the person giving the answers, was the only reason they eventually fell flat. This is a problem that worries me. How do you filter these people, if firing is extremely frowned upon in your org? The only real initial hint that I had was the abysmal typing speed vs claimed experience, which is not a reason that you can write down, for why you failed someone, without looking like some sort of elitist.
I think this will eventually become a real problem, with remote interviews. I think in person, or monitoring, is the only way to catch something like this. But, how do you do an in person interview with a remote team? You either make your requirements even more impossible, or you change the culture of your org to accept that new people may have to be let go, without it being the hiring managers fault (not going to happen).
Most places I've worked for had a 3-6 month probationary period for new employees, where the new hire is evaluated and can be let go with ease. Full benefits of the job don't begin until the end of the probationary period.
Your organization doesn't do that? It should.
This would be incredible, but I'm on the hardware side of things, so maybe the context is a bit different. No company I've worked for did this, with two startups, and two being in the top 5 (at the time). All hardware centric.
I brought this up with my org and was told that it just acts as a filter, since top talent is already well employed, doesn't want the risk, and would never consider a relocation without permanence. Being hardware, physical presence is required, so relocation is necessary more often than it's not. I can agree with this since it matches my own experience. I didn't considered temporary positions any time I was looking, for the same reasons.
I honestly thought this was a universal practice. I learned something new today!
> since top talent is already well employed, doesn't want the risk
I've never seen top talent balk at this. They know that they'll perform well during the probationary period, so there is no risk.