If a candidate reached out claiming they didn’t have a machine to interview with, I’d gladly find another path forward. But I imagine that’s a small minority in this industry.
It wouldn’t stop them from being hired.
If a candidate reached out claiming they didn’t have a machine to interview with, I’d gladly find another path forward. But I imagine that’s a small minority in this industry.
It wouldn’t stop them from being hired.
Any obstacle whatsoever, especially one you yourself admit is very rare, is much more likely to result in a dropped interview if one is even offered. Why bother?
You’ve got 10,000 candidates applying. Seriously, what would make “doesn’t have a laptop” stand out to you positively? Why not just go with the 9800 applicants who do have one? Surely there’s no reason to think “broken laptop = good dev”. It’s so much easier to simply go with a candidate who has no problems. Beyond that, what’s the deal with making candidates do stuff on their own machines anyways? You don’t know what’s on there. You don’t even know if it’s stable enough for a test, and none of that has any bearing at all on their skill.
I’ve never worked in the Bay Area, but if this is common practice, I think I dodged a bullet.