Or they might simply have some ADHD/autistic traits which make these things require additional effort.
I have a list of past projects I'm comfortable talking about. I can go to great lengths talking about any of them in detail if prompted. I'm also comfortable talking about technical topics including those I'm not intimately familiar with - that's part of my job after all. But most importantly, I'm confident enough that I can say "I don't know what that is, can you elaborate?" and "I'd need to look into that and get back to you".
I've you're going to leetcode me, I'm going to underperform. I've never had to do leetcode for a job. I also don't typically apply to the kind of companies that think leetcode is a good filter. Why should I waste their time and mine to apply to a job at a company I'm probably going to hate working for?
Okay, you don't like leetcode, that's fine. It doesn't mean you shouldn't prepare for an interview. In fact I'd say preparing for an interview might include researching their interview process and avoiding them if they use leetcode type questions which you don't like. It might also include learning about their tech stack, brushing up on relevant past experience, or learning a bit about the industry they operate in (for example).
I have a list of past projects I'm comfortable talking about. I can go to great lengths talking about any of them in detail if prompted. I'm also comfortable talking about technical topics including those I'm not intimately familiar with - that's part of my job after all. But most importantly, I'm confident enough that I can say "I don't know what that is, can you elaborate?" and "I'd need to look into that and get back to you".
I've you're going to leetcode me, I'm going to underperform. I've never had to do leetcode for a job. I also don't typically apply to the kind of companies that think leetcode is a good filter. Why should I waste their time and mine to apply to a job at a company I'm probably going to hate working for?