In my experience, there is no such thing as "bad remote tech hire". Either it is a "bad hire" or you need to set the right training and expectations. A bad hir

In my experience, there is no such thing as "bad remote tech hire". Either it is a "bad hire" or you need to set the right training and expectations. A bad hire will perform bad whether in person or remote. I do understand the premise of your question though. The issue with remote hires is not that they are bad, but they are probably not well equipped (training, expectations, process, tools) to do their job remotely. Also, unless someone is senior enough with some remote experience, I am personally hesitant hiring remote because it adds to the complexity. So you don't eliminate bad remote hires. You eliminate the reasons why they are performing bad being remote if they are good otherwise. If they are bad anyway, then being remote probably makes it worse but not sure what you can do about the "remote" part only in such case.