[collyw]

No.

If you want me for a skillset that I have then interview me on that.

If you think that dumb white board questions are relevant, then there is a 50% chance that I will get it right. Your loss if I get it wrong. You know that job isn't going to be related to some algorithmic crap. (At least it doesn't waste too much of my time - compared to some pretty hefty take home tests I have done).

After 15 years, there is too much stuff to study for its likely a waste of time. I know the stuff that I know well. I won't bullshit any claims about stuff that i don't know.

[csixty4]

Same. Shoot, I've been pulled into the boss's office before and told not to use terms like "big O" on the job because they confuse the junior devs. And I've never needed to balance a tree or reverse a linked list or any of those things since college. It hasn't stopped me from getting projects done.

[ralston]

I once studied for about 48 hours (off and on) for interview at a security-related startup. After 5 rounds of interviews, not a single person asked me a single technical question. Needless to say I got caught up in the modern "study for the interview" hype - a trick I hope to not fall for again.