3 ms·

Got rejected after a take home, and the feedback from the recruiter was 1. a reviewer thought I used a library incorrectly (they actually misunderstood how the

Got rejected after a take home, and the feedback from the recruiter was 1. a reviewer thought I used a library incorrectly (they actually misunderstood how the library worked) and 2. I didn’t implement something that the instructions had explicitly said not to implement. I didn’t argue with 1 because I figured it was pointless and it sounded like the recruiter was having a rough day. I politely pointed out 2 as a courtesy and he said “huh, the other guy yelled at me about that”. Although honestly, I left the process thinking “lol” instead of “I’m a dumbass” like I might have absent the feedback.

defrost 2y ago
> and he said “huh, the other guy yelled at me about that”. If this was SASR recruitment that'd be the pysch portion of the test, reject a candidate for a reason that makes no sense and watch their reaction ... The assessment never stops, everything's a meta test, and they push until you quit the recruitment merry go round. In the relatively normal world of software engineering .. that's a recruiter landed with a poor testing pachage and procedures.