i'm more than happy to do take-home assignments or complete reasonable timed assessments, but i have (politely) refused to complete leetcode-style gotcha screens when they have been presented to me as "just another part of the application process".
idk, though. maybe that's a privileged statement based on my position, but from what i can tell grinding leetcode seems to be much less reliable these days & the toll it takes on a lot of folks is pretty significant.
If someone asked my to do a leetcode style problem I'd politely refuse, and likely end the interview. I went through that kind of job hunt at the expense of my mental health and confidence in myself as an engineer once. It was one of the most degrading experiences of my life (so in all not a bad life to be fair). I'll never do it again.
When people started asking these questions, the whole point was to see how people reason about a new problem they haven't solved before. There are almost no work problems that require you to regurgitate something verbatim you saw on leetcode before.
It's seriously making me question the intelligence of these interviewers. Although at the same time I realize it's mainly just to arbitrarily whittle down the applicant pool to a smaller number you can interview in person.
it's really easy to identify code that is not optimal at code review time. it is far more challenging to have a conversation with a algorithm-regurgitating robot that their entire approach was wrong because they misunderstood the abstraction or that their code wasn't needed because Larry is refactoring that part of the system to a separate service already.
But if you're an interviewer or hiring manager who is telling people to "grind leetcode" because you legitimately believe this is a good way to find good talent ... you need your head examined. All you're doing is filtering for people who've grinded leetcode long enough to memorize solutions. This has ZERO correlation to software development ability.
Yes, you can certainly find companies out there that don't interview in this way, but leetcode interviews are extremely common.
After that might be more rounds of coding, system design, and hiring manager interview.
The part where you can be charismatic is once you pass the initial technical bar(s). The talking/behavior is a later point in time and is relatively easy IMO.
Examples of questions I've been asked:
1) https://leetcode.com/problems/non-overlapping-intervals/
2) https://leetcode.com/problems/design-add-and-search-words-da...
3) https://leetcode.com/problems/detect-cycles-in-2d-grid/descr...
4) https://leetcode.com/problems/evaluate-reverse-polish-notati...
So nothing too hard but you have to instantly solve it, and optimally. The hardest one I got was some type of AI search problem, where you have to find a way to navigate obstacles in a 2d grid, and another geometry problem I've not seen before.
Along with this questions like: what pitfalls arise in concurrency? Explain how you would design a pointer type that can be shared between threads, what is epoll? How do you debug a distributed system? etc.