Earlier quoted context omitted.
A lot of places will also do a desgin interview to cover this aspect of the job.
Which raises the question of why do the other kind of interview at all. I mean the leetcode nonsense whose end state is often a theatrical performance: “I’m pretending to invent this clever algorithm on the fly although I’ve practiced it for weeks”. Is there any evidence that candidates who do well on design interviews but fumble on leetcode would be any worse at the actual job?
people who cannot leetcode - a simple data structures & algorithms inteview - cannot understand runtime nuances of what they write.
This is how you end up with N+1 algorithms and exponential runtime.
For example look at all modern front-end in javascript - usually leetcode is more relaxed for front end, and you end up with ungodly gobbles of unnecessary loops inside loops wrapped in loops that traverse DOM for no good reason and freeze the browser.
it is the javascript people who import node libraries that contain 3 lines of code, instead of writing it properly