Writing the job around the three problems the hire will own in six months is a much better filter than a list of every technology you might touch. A small paid task also tells you how someone works inside your real codebase, which puzzles never show. Planning the first two weeks before they join is the step most founders skip, and it's often what decides whether the hire speeds things up or slows them down.