If the question you are answering has a "right" answer you are asking the wrong question. E.g. if you search for a web dev, give them a problem and some constraints (e.g. language), ask them to draft a quick solution.
When they are unsure then they will usually ask about the problem or about how the problem should be solved (microservice, shell script, ...)
These are valid questions and you can turn them into more knowledge about the candidate by asking them what pros/cons they see by going each route.
Just like that I have actors that want to know more about the role and actors that need less guidance. In the end their performance counts. I will still try to give them hints inbetween takes (just like I would when we work together on the set) — but in the end it is their work which I will judge.
Unless you are hiring for a position where a dev works in complete isolation and receives no guidance whatsoever I think emulating the real thing is the way to go. And that usually doesn't entail holding a devs hand and neither it does entail not helping them at all.
When they are unsure then they will usually ask about the problem or about how the problem should be solved (microservice, shell script, ...)
These are valid questions and you can turn them into more knowledge about the candidate by asking them what pros/cons they see by going each route.
Just like that I have actors that want to know more about the role and actors that need less guidance. In the end their performance counts. I will still try to give them hints inbetween takes (just like I would when we work together on the set) — but in the end it is their work which I will judge.
Unless you are hiring for a position where a dev works in complete isolation and receives no guidance whatsoever I think emulating the real thing is the way to go. And that usually doesn't entail holding a devs hand and neither it does entail not helping them at all.