Live data from Hacker News

If companies interviewed tech recruiters the way they interview programmers

medium.com

101–106 of 106 posts

Re: If companies interviewed tech recruiters the way they interview programmers

#101
post #95
post #75

Earlier quoted context omitted.

Not at all. I'm getting at the fact that many frontend devs don't know JavaScript, they just know cut-and-paste jQuery or how to fiddle with/maintain React/Angular components in a large app.

I doubt you can really just cut-n-paste jQuery in any nontrivial web app...

Correct, and that's one way to decisively filter out people who haven't worked on a nontrivial web app.

Re: If companies interviewed tech recruiters the way they interview programmers

#103

When I read articles like this, I tend to assume that they are exaggerations written by people who feel burned because they didn't get the job they want and that the reason was unfair interview questions. In other words, I simply don't believe that interviewers are, as a group, so stupid that they regularly ask obscure Excel questions when they are plainly not relevant. To continue with the recruiting example, I susp…

[deleted]

Re: If companies interviewed tech recruiters the way they interview programmers

#104
post #77

Earlier quoted context omitted.

I think it's at least partly because how averse many shops are to hiring people; even people who clearly lied on their interview/resume. At one point in the past I worked with someone who was incapable of understanding pass-by-reference; something like: int getFoo(foo *out); A colleague spent multiple hours per day for a week trying to explain this to them. After a week they still were unable to successfully make use…

Isn't this passing by pointer and not passing by reference?

Pointers are a specific type reference. As they are the only type of reference built-in to the language, it is common to use the more general term "pass by reference" to mean "pass by pointer" when discussing C.

Re: If companies interviewed tech recruiters the way they interview programmers

#105
post #56
post #51

Earlier quoted context omitted.

Most recently I asked if the recruiter knew the difference between Java and JavaScript, since he had just mentioned both of them. "Uh, they're web technologies... in very high demand." "Yes, but is there a difference between them? What kind of web technologies are they?" Long pause. The background silence changes a little, as though a hand were placed over the telephone's mouthpiece. I can't hear the word in the conv…

Perfect. Next time you should respond, "Hmm...that's not what I have here. The answer is, 'JavaScript uses Electron and Java uses Spring.' I'm sorry, I don't think you're a great fit for us. Best of luck and have a good day." Then hang up, and kill two birds with one stone in the process: the tone-deaf recruiter finally understands how the buzzword bingo interview feels, and you have one less incompetent recruiter to…

I like you.

Re: If companies interviewed tech recruiters the way they interview programmers

#106

This is a picture perfect description of my interview with stitchfix.

I'm sorry to hear that. For which position were you interviewing?

Engineering. First job ive never gotten an offer for. I feel like they werent serious about hiring and maybe they were required to interview a number of non internal candidates and were just checking boxes. Huge waste of my time.

Granted I acknowledge Im not perfect and desirable in every way, but the interview felt really silly

Post reply on HN