1) That's irrelevant. I'm speaking to the importance of the ability to reason a linked list which is not really related to 'practical examples of linked lists in a web development context'. To quote silentbicycle above: "It's a linked list, people." We're not talking about 'the latest developments in red-black tree algorithms'.

However... 2) Probably every list of objects you throw around in whatever abstraction providing framework you're using.

Would you hire somebody who can't compute 2+4? For the same reason you wouldn't hire somebody who can't reverse a linked list, even if the actual reversing of the linked list doesn't come up in the job.

Write a webcrawler that doesn't get stuck crawling in circles. You need to maintain history somehow.

Why a linked list? Wouldn't something resembling a hash table or even a tree be a lot better.

I think with web development a lot of the situations where you would want a linked list are abstracted away. Personally I would be testing people on how they take some kind of design outline and map out how they would approach it. Something like dealing with bringing together multiple API's to would be high on the list, this is becoming a much bigger part of web development.

If someone can't understand a linked list, hash tables and trees are well beyond them.

One example,

Given a list of things, implement drag-and-drop way to reorder things.