+1 on 'Code Archeology'.
I wonder if interviews should consist more of reading a pile of open source and just trying to make sense of it.
There's some crusty open source I've had to deal with whereupon it took quite some intelligence just to get it to compile and work - absolutely nothing to do with 'algorithms'.
I'm half inclined to just say: "Here's a git repo, build it, modify this thing to do that" and if they can, they're gold.