They don't have to meet everything on the job listing (other than required ones, those they have to, explicitly in their CV and cover letter, or they get removed from the pile) but if they try to address it all as much as possible that's a huge plus.
Also asking a programming question without a compiler and the person actually doing their actual coding thing it like asking a person to do anything without the actual thing. "Can you cycle?" but there's no bike to show you they can, etc.
-
-
But even then you don't code with somebody breathing down your neck. LMAO Or if you do, that's a bad environment!

-
Would you ask somebody to do a literature review or an experiment during an interview?
-
I think this analogy doesn't quite work. There are certain coding questions that are fine and certain lit review questions that are too - e.g. 'where would you start if you were to find out x and y/ solve this coding problem?'. I know several companies do 'coding' questions
-
or tests at interviews that are logic based. But I DO think best way of testing this is to ask to see some code they've written or to ask them what they have written (or to see online repositories if it's that relevant to the role). These are easy questions to 'freeze' while
-
answering and depending on the role you're interviewing for, you might not need someone who interviews well if they code well.
-
I found it helpful to write an interview guideline. Of course I did not ask to code in front of me, but rather asked a simple question that any person should be able to answer who has some coding experience. All I can ask for really ;)
-
I was trying to make the point you made
@hisotalus, so yes, agreed.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.