Which tells me all I need to know.
Deciding upon which Collection to use is a daily occurence. And if you do choose any hash map derived structure you will frequently need to create your own hashing function for objects.
I've got to say, for the most part, I agree with DJ_Jestar.
Yes, it's important to know when to use a hashmap over a list but for the everyday things where you have a handful of items then using a list and iterating over it is no big deal.
Similarly, I've not had to code a hash function by hand for ages. These days it's a case of selecting an option in the IDE, selecting which fields you want to use in the hash and letting it generate the function for you.
Again, it's useful to know how to construct a function that will minimise collisions, but it's not vital knowledge to get most programming tasks done.
Similarly knowing the relative big-O time and space complexity of various different sorting algorithms is something that for most cases doesn't matter as you will just call the Sort method on the collection you're using, or use a built in library.
There are things that do require deep algorithmic knowledge, but you have to remember that the average developer is knocking up simple CRUD websites and generally doesn't have to do that sort of stuff on a day to day basis.
I personally would put the ability to structure code well and write it in a way that can be understood by others way above algorithmic knowledge for the vast majority of development tasks.