Here is the 15 sec coding test I used to instantly filter out most applicants
1–10 of 111 posts
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#2That was REALLY weird to read. In reader mode the comparator in the first conditional was >=. But without reader mode it was just >.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#3That was REALLY weird to read. In reader mode the comparator in the first conditional was >=. But without reader mode it was just >.
[deleted]
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#4That was REALLY weird to read. In reader mode the comparator in the first conditional was >=. But without reader mode it was just >.
What did it say? Their website doesn't load.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#5Best test is to listen to 2h meeting without too much details and have to figure out how to ship the feature.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#6That was REALLY weird to read. In reader mode the comparator in the first conditional was >=. But without reader mode it was just >.
Was that the trick? When copying the text, it is also >=, which is why an online search or AI tools probably give the wrong answer as the article asserts. If you correct the code then at least Claude gives the right answer.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#7That was REALLY weird to read. In reader mode the comparator in the first conditional was >=. But without reader mode it was just >.
Apparently they don't want to hire people who don't use reader mode.
But then the question is, how do you reach people who filter out the job ads?
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#8That was REALLY weird to read. In reader mode the comparator in the first conditional was >=. But without reader mode it was just >.
Which is literally the point of the post. They have the = in >= at an opacity of 0 and a font-size of 1, which means it doesn't appear if styles are used properly. And their point is that candidates that copy/paste such trivial code into an AI/interpreter will get -11 because it just sees the >=.
Though a gap in their process is that, as you mentioned, various reading modes also remove styles and likewise might see it. Though a reader should filter out opacity:0 content.
Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#9Re: Here is the 15 sec coding test I used to instantly filter out most applicants
#10I like it, a test so bad, it just might work! I think the trick is not the equal sign, trick is to keep it so simple and small that most qualified people will not try to short circuit it.