> Personally, I think temp-to-hire or work-for-a-day type models could work I've seen the contract-to-hire stuff come back up recently. There are a couple big

> Personally, I think temp-to-hire or work-for-a-day type models could work I've seen the contract-to-hire stuff come back up recently. There are a couple big flaws with that model, beyond possible abuse, though. 1) You basically are excluding yourself from any candidate that still has a full time job. It would be crazy for them to leave their current gig for a place that might not actually bring them on full time. 2) It doesn't scale, bringing on new team members properly takes time and effort. Not only are you potentially wasting their time, you are also wasting your team's time, and you can only do this kind of evaluation so many times. I do agree though that the standard interview model doesn't make sense. Memorizing leetcode problems doesn't map to good engineering, and take home problems filter out a lot of good engineers that won't bother spending the extra time.