Solving that kind of interview questions is something I always struggle with. I understand they are trying to see if you, as a candidate, can tackle complex problems. The problem is that the way they force you to solve them is not realistic.
I'd say that aside from the context of the interview, a developer should be able to solve algorithm-related problems, because that'll help them face harder problems down the road. It doesn't matter really if you're a front-end or back-end, or data architect or whatever, these types of problems should be something you can tackle.
Solving that kind of interview questions is something I always struggle with. I understand they are trying to see if you, as a candidate, can tackle complex problems. The problem is that the way they force you to solve them is not realistic.
I'd say that aside from the context of the interview, a developer should be able to solve algorithm-related problems, because that'll help them face harder problems down the road. It doesn't matter really if you're a front-end or back-end, or data architect or whatever, these types of problems should be something you can tackle.
That's my take on it anyways.
Yes, learning them and being able to solve them hardens your mind for stronger challenges.
And also, I think (some of) the unrealistic approach of some interviewers is also an issue. Thank you for your insight.