I'd argue they've been part of the interview process because they're integral to effective programming. Sure, you might not need to implement a doubly-linked list on the job, but you should certainly know how it works under the hood and what the pros and cons of using it are. I don't think any part of that knowledge has become any less relevant.
Whilst I agree with you about the importance of knowing this topic, I'm trying to understand why the implementation of this knowledge during 45-60 minutes interviews is this important. I'm talking about problems as egg drop puzzle or knapsack problem etc. because this kind of situations may (very) rarely occur in real life apps.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'd argue they've been part of the interview process because they're integral to effective programming. Sure, you might not need to implement a doubly-linked list on the job, but you should certainly know how it works under the hood and what the pros and cons of using it are. I don't think any part of that knowledge has become any less relevant.
Hi Ben and thanks for reaching out!
Whilst I agree with you about the importance of knowing this topic, I'm trying to understand why the implementation of this knowledge during 45-60 minutes interviews is this important. I'm talking about problems as egg drop puzzle or knapsack problem etc. because this kind of situations may (very) rarely occur in real life apps.