Peeking at the source, it's just a zero-width div, which is not accomodating of people with disabilities. This might open you up to litigation if you disqualify a blind person on the grounds he gave the wrong answer 'using AI', when he might have just been answering the question his screen reader read out.
Here is the 15 sec coding test I used to instantly filter out most applicants
21–30 of 111 posts
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#22Wouldn't the correct answer be 5? result = result + x // 5 0 5
3 comes before. Read it again.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#23Wouldn't the correct answer be 5? result = result + x // 5 0 5
It’s in a loop
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#24What most interviews get wrong is that there are usually just a few "bullet points" that if you see them, you instantly know that the the candidate at least has the technical chops. Instead of creating a test that specifically aims for those bullet points, many technical assessments end up with convoluted scaffolding when actually, only those key bullet points really matter. Like the OP, I can usually tell if a candi…
I’d love for you to elaborate :)
But along that thought, I’ve always held that a human conversation is the best filter. I’ll ask you what do you work on recently, what did you learn, what did you mess up, what did you hate about the tool / language / framework.
I strongly believe your ability to articulate your situation corresponds with your ability to do the job.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#25Wouldn't the correct answer be 5? result = result + x // 5 0 5
The logic results in 3 + 3 - 5 = 1, so it's not 5, sorry. I'd love to know what logic path you followed to get 5 though!
I did it in my head but got 4 (3 * 3 - 5), so I fail, too. Hopefully I'd be paying closer attention if I was actually applying for a job.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#26For anyone who missed the (poorly-explained) trick, the website uses a CSS trick to insert an equals sign, thus showing different code if read or if copied/pasted. That's how the author knows whether you solved it in your head or pasted it somewhere.
This didn’t work for me because Reader Mode popped up and showed the “hidden” equals sign.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#27Wouldn't the correct answer be 5? result = result + x // 5 0 5
Iteration starts from the first element. X is 3, 3, then 5.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#28Why wouldn't a qualified developer just run the code? Takes two seconds instead of ... whatever you're going for here.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#29Peeking at the source, it's just a zero-width div, which is not accomodating of people with disabilities. This might open you up to litigation if you disqualify a blind person on the grounds he gave the wrong answer 'using AI', when he might have just been answering the question his screen reader read out.
This is an excellent point. I did not think of that.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#30I think it’s important to test these systems. Let some % of candidates who get this wrong through to the next stage and see what happens. Does failing this test actually correlate with being a bad fit later? If you want to ineffectivly filter out most candidates just auto-reject everything that doesn’t arrive on a timestamp ending in 1.
> Let some % of candidates who get this wrong through
Really, the better test would be to not discriminate on it before you know it's useful, but store their answer to compare later.