4 ms·
I've had more than one situation where I was interviewed by someone to see if I was "proficiient in skill #2" where it was obvious to me that they were either
by nirvana 14y ago
I've had more than one situation where I was interviewed by someone to see if I was "proficiient in skill #2" where it was obvious to me that they were either incompetnat or unreasonable.
For example, I listed Win32 programming on my resume back when I would do windows work... and one guy would ask me the parameters for various functions in the API. When I said I always looked those things up while programming he seemed taken aback and said "well, have you used (some specific area of the API)"... and when I said yes, he asked me to list off the parameters.
Needless to say I didn't get an offer from that company, but have had trouble respecting them ever since (and am not surprised that they haven't amounted to much of anything and haven't been innovative.)
Its quite possible that he told the hiring manager I'd lied because I couldn't name a single API he asked.
I just sat and thought about a function I use a lot in my current programming. Cant' quite remember the name of the function itself or its parameters... because I haven't used it today. When I need it, its there, (and its autocompleted by the IDE anyway.)
I think the biggest problem with companies hiring is that they often have people who have no clue how to interview doing the interviews. Seen that a lot.
- rm999 14y agoI'm sorry that happened to you, I've dealt with the same kinds of things. It sucks when bad interviewers block good candidates. In my case I assure you that's not what happened though. When the candidate realized he was faltering on too many questions about skill #2 (really basic questions) he started talking about how he was currently reading an introductory book on it and how he was excited to work somewhere where he can apply it. Oh yeah, and he claimed on his resume that he had been applying it at his current job.