You seem to very much focused on data structures and algorithms, which I do understand is the only way many organizations can quantify prospective programmers (other than knowledge of "technologies" and "languages").
I'm curious what your response would be to the following interview question ...
"How would you model into code the operation of an elevator?"
(I'm wonder whether your viewpoint is solely one of data structures and algorithms that transform them. Or whether you might also have some other perspective of how to go about approaching the design of a software application?)
The elevator question is deceptively difficult and I find there aren't any decent answers to it on the internet. People have devoted phd papers to this topic. And there are sparse Leetcode discussions on this subject.
I suggest it is particularly difficulty if you have no method or approach to apply. That in itself says a lot about an applicants design and programming ability. Given that much of software development is about modeling systems (real or imagined) into code, is it too much to ask that a "programmer" know something about it?
I'm curious what your response would be to the following interview question ...
"How would you model into code the operation of an elevator?"
(I'm wonder whether your viewpoint is solely one of data structures and algorithms that transform them. Or whether you might also have some other perspective of how to go about approaching the design of a software application?)