> Take-home projects or a trial period of some kind. This makes the most intuitive sense by far: having candidates do a representative slice of the job gives you a solid idea of whether they'd be any good at it. Combining this with structured interviews was (before AI) considered a gold standard; you'd get a sense of who they are and how they work by talking, have a way to compare them pretty objectively to other candidates because of the structured and consistent nature of the interview process, and then you'd get a sense of how they apply their attributes practically to the job via the work exercise.

Unfortunately a lot of companies have over the last several years been using this to get candidates to do a project for free for them. If it's going to take more than a few hours of my time, I don't take project style interviews seriously unless compensation is added (which some companies do offer and is a big green flag).

Definitely been tricked into working for free a time or two.

Best middle ground I ever had was an interview where they impose a strict 1 hour (maybe it was 90 minutes, idk) time limit between when I got the prompt and when I emailed them back. Then they spent some time looking over it, then I had an interview with an engineer who had read my code and we chatted about it. Why I had made certain decisions, what corners were cut because of the time limit, etc.

Felt very fair. Not enough time to assign a valuable task, enough time and privacy that I wasn't under the gun like you are in a whiteboard interview, and it was pretty applicable to what I would be doing at the company. Solid interview. Didn't get the job, but respected the process.