I failed an interview, and the interviewer failed me
unknowndev.pen.io
unknowndev.pen.io
Complaint 1: The recruiter asked you questions you didn't find relevant. I have often asked "curveball" questions just to see how a potential hire thinks on his feet or perhaps to see how he handles a situation in which he doesn't know the answer to something (the correct way being "I don't know that off the top of my head, good thing for Google and Stack Overflow, right?"), so it's not really up to you to determine which questions are relevant. Then again, he could have just been a dick, but not necessarily.
Complaint 2: The company had to be prompted and prodded to respond to you Certainly, this isn't very professional, and it would also leave a bad taste in my mouth, but know this: the company doesn't owe you a damn thing. Silence = rejection, simple as that. If there was anything to follow up with, I would have emailed the company that day, and then promptly put them out of my mind until they replied and kept applying to other jobs.
Complaint 3: The company didn't get back to you in a timely fashion. Unfortunately, this is simple supply and demand. Or, the company is terribly incompetent. But it seems to me that they would prioritize reviewing candidates if they had a small number who were qualified. If there was already a week backlog of candidates, they were probably getting plenty of them already.
I understand the point of your piece, that you believe the recruiter failed the company by not properly interviewing you, and that you believe that the company shot itself in the foot by not giving you a real chance. OK. Then do you really want to work at a place like that?
#1 There were other questions on top of that where the recruiter obviously didn't pay attention. Such as I'd mention that I use the MVC pattern to program and have been using it via a PHP framework. He would follow that up with "Do you have any experience with MVC?" and I'm like, are you serious? I just said that I've been programming this way for years. Right after that he'd ask "Have you used any PHP Frameworks?" and again, I'm bewildered because I've already answered this. He would also, LITERALLY, ask the same question again, five minutes later as if he wasn't paying attention. I'm all for curveballs. I've been interviewed for a front-end job and was asked about SQL but it was approached differently rather than "top 10 questions" from Google. Idk. You might be right though, it could have been a test.
#2 Indeed, the company doesn't. However it's discouraging after you're told, "You'll get a response within 48 hours" and nothing happens. Or when a recruiter ignores half your email by ignoring any questions you have and responding to the last sentence in your email. I don't write lengthy emails either. I like to keep it short and concise so you can quickly scan it on your phone if anything.
In the end, I'm happy to not be there and not deal with them. I might just contact them for the hell of it to see what's up.
My favorite is when you apply somewhere and receive no response. Then several months later, you're contacted by a recruiter from the company at which point you've long past moved on with an offer from somewhere else.