For those positions I'm trying to get a sense of troubleshooting ability, teamwork capability, ability to admit you were wrong, creativity, how thorough your documentation will be, how descriptive your ticket detail will be, attitude towards projects vs reactive work, and whether you want to be a maker or a doer.
I'd love to see how a pair programming interview works, and I know that I'd be utterly awful as a candidate in such a process. Hopefully I'd learn something ;)
the test is only as awkward as every interview is. interviews are awkward because of how we treat the situation, not because of what we do during the interview.
the key point is to put the candidate at ease as much as i can. i usually get positive feedback from candidates about my interviews, so i must be doing something right.
i have been on the other side of this as well. and i felt that the code task i was given was way to easy to be a skills test, but i also realized that any challenge worth my level of experience would not possibly fit into a one-hour interview session.