It seems like you've already identified that the problem is you needing to know 'algorithm problems', so I would work on that. You shouldn't need to memorize h

It seems like you've already identified that the problem is you needing to know 'algorithm problems', so I would work on that. You shouldn't need to memorize hundreds of random problems. I think a few simple (not requiring much time to learn or to maintain) things would go a long way if you really are willing to make yourself put in some effort. Learn how to do basic big oh analysis. Learn how to apply recursion to simple enough problems, like the boggle question. Learn how merge sort and quick sort work and be able to implement them (they're not even that many lines of code). If you're already working on side projects and solving problems at different scale, that should help you naturally stay up on these things. Being able to talk about different libraries you learn and how you worked at different scales should also be valuable during an interview.