When I'm interviewing it's not a guise. I am very clearly interviewing you for:
- cultural fit
- how you approach the problem
- and how well you communicate
For us the actual code we ask to write is very simple. Think fizz buzz. I would never dream to ask to, for example, write code to balance a binary tree. I think those questions are crazy. 90% of our team couldn't do that on a white board and that's completely OK because it's not a skill you need day-to-day. If I based decisions on those kind of algorithms I wouldn't have hired most of our team and it would have been our loss not theirs.
With that said, some people couldn't complete our basic challenge so even though it's not intended as a code competency hurdle, it effectively has weeded out some people who clearly would not be able to function in their daily job.
I'm not sure how I'd react if someone outright refused to do it. I guess I'll deal with that if it happens.