In my experience reviewers also look at things other than just how well someone can code. Coding can be learnt but having good attention to detail and a solid problem solving attitude is harder to come by. At Rexlabs we ask the interviewee to make notes and have a few questions around how they plan to complete the test. We also look at; problem solving skills, the reasons behind which problems were solved first and why in a particular order, which external libraries were added and how they decided upon a specific library, how comfortable are they with git and what kind of commits have they made.
The code is a good indication of how comfortable they are with a language or framework, but it doesn't cover if they are a good fit. Also, a senior might be a great programmer but not under a time restriction which will essentially cause them to make more mistakes than usual.
So to recap, I think having extra questioning as apart of the code test is key, the answers should be submitted with the test so that it's fresh in their mind. Answering these questions during an in-person interview can be daunting and they might have forgotten by that point.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In my experience reviewers also look at things other than just how well someone can code. Coding can be learnt but having good attention to detail and a solid problem solving attitude is harder to come by. At Rexlabs we ask the interviewee to make notes and have a few questions around how they plan to complete the test. We also look at; problem solving skills, the reasons behind which problems were solved first and why in a particular order, which external libraries were added and how they decided upon a specific library, how comfortable are they with git and what kind of commits have they made.
The code is a good indication of how comfortable they are with a language or framework, but it doesn't cover if they are a good fit. Also, a senior might be a great programmer but not under a time restriction which will essentially cause them to make more mistakes than usual.
So to recap, I think having extra questioning as apart of the code test is key, the answers should be submitted with the test so that it's fresh in their mind. Answering these questions during an in-person interview can be daunting and they might have forgotten by that point.