Personally I do my best work given time to focus, and not being watched. If there's an option for a slower paced take home, I do quite well as it lets me work in a familiar environment and think carefully not under pressure.
Anyway food for thought, do what you want to do, it's just a suggestion / plea for those of us who are awful at coding interviews (even with lots of practice on leetcode).
At my job, we designed our interview process around the question: “what is the minimum coding exercise that we expect anyone we hire to be able to do?”
This has resulted in an interview where we do ~30 minutes of coding, stuff like: function to reverse a string, function to add an array of numbers, find the largest number in an array of integers.
From there the rest of the interview is conversational. If the candidate is frontend we may dive into X, Y, Z technology. For example, if someone has 5+ years of React experience but doesn’t know what a hook is, that’s a red flag, etc.
You’d be surprised how many people are absolute garbage at those simple coding questions, despite having years of experience. And everyone that cruises those questions has been a great hire thus far, assuming no other red flags like bad culture fit or poor communication etc.
* Take home
* Deep reference checks with former colleagues and managers
* Coding interview questions
* A work trial period
That way people can pick which one will best showcase their skills.