Then you actually get to evaluate someone on how they’d work on your team.
- are their PRs nicely written - do they even know git properly - do they comment code - even for basic code is it structured - does it pass the linter?
Eg. Providing candidates a challenge and the actual pylint command you’ll score it with it’s really easy to see who even bothered to check it passes.
Rather than putting someone on the spot with leetcode see how they behave as a dev. On your real team you’ll have a story with acceptance criteria and a repo to PR into. Give them the same.
It can be a short tiny bit of code but you’ll learn so much about there behavior.
This is also much harder to just google the answer, because you don’t just care about the answer.
Design it so it’s just an hour or two, then offer the choice. Explain you need to evaluate their programming skills for a programming role and they have the choice of interviewer led in-person, or a take home. Both designed to be roughly 1-2 hours.