At my company, we give applicants a week to complete a coding challenge before the final interview. All the interviewers (2-3 at our company) review and score these before the final interview. Yet, as long as the applicant submits code that (a) accomplishes the stated goal and (b) isn't obviously copy/pasted from somewhere else, we will proceed with the final interview.
However, we'll ask for explanations about that code during the final interview. Generally this involves us asking questions about design choices we noted in the review.
We also often have them fix a bug in it (there's always one or two) in front of us. This allows us to see them working on their code, instead of something entirely unfamiliar.
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.
At my company, we give applicants a week to complete a coding challenge before the final interview. All the interviewers (2-3 at our company) review and score these before the final interview. Yet, as long as the applicant submits code that (a) accomplishes the stated goal and (b) isn't obviously copy/pasted from somewhere else, we will proceed with the final interview.
However, we'll ask for explanations about that code during the final interview. Generally this involves us asking questions about design choices we noted in the review.
We also often have them fix a bug in it (there's always one or two) in front of us. This allows us to see them working on their code, instead of something entirely unfamiliar.