I am also happy to work on a small take-home project for them (within reason) & provided its relevant to the work they do.
The purpose of data structures and algorithms questions is to demonstrate some abstract thinking and coding ability in a short space of time - if you can do that you can probably code in whatever language / framework they use.
Brainteaser questions on the other hand, those are worthless.
Also, having been on the interviewers side of the table - I think as soon as a candidate & I begin discussing his code & technical choices, it becomes obvious if he did the work himself i.e. can he talk in depth about the stack he used, any algorithms, schema decisions etc... or does he just give short "I'm hiding from your question" type answers.
I would be much happier if the interviewer gave me a small app to create from home (which was relevant to the work they actually do) & then discuss my implementation choices in person with them.
What is the point of having me spend most of an interview doing things with dijkstra's algorithm if never, in the history of your company has this been used nor do you plan to use it & then spend the last 5 minutes asking a few vague questions about what I like about Ruby / hate about Rails.
Technical tests, in my experience, are mostly (90%+ of the time) composed of challenges which have no relevancy to the work I would be doing for that company, its pointless ceremony over common sense.