3 ms·
> After being told a couple of times how happy <company> are to finally see a real, competent programmer when I enter the room and just answer simple questions
by flukus 9y ago
> After being told a couple of times how happy <company> are to finally see a real, competent programmer when I enter the room and just answer simple questions
One of the more depressing experiences I've had is heading into an interview (on the interviewer side) after seeing someone completely fail a fizzbuzz test. Everyone looks at each other thinking "well maybe if they knock it out of the park during the interview...". It's like dating as an extremely lonely person.
> Well, the problem is that the sum of these methods (clueless(?) recruiters, keyword filtering etc) often filter out me before I even get to an interview.
I've never had a problem with this, except maybe lately with angular. I structure my resume to include the keywords but in a format actual hiring managers want to see, eg, Experience with a number of MVC frameworks including ASP MVC, Monorail, Ruby on Rails (ROR). I don't know if that's the reason it's never been an issue for me, but I hope it helps.
- bogomipz 9y ago>"One of the more depressing experiences I've had is heading into an interview (on the interviewer side) after seeing someone completely fail a fizzbuzz test. Everyone looks at each other thinking "well maybe if they knock it out of the park during the interview...". It's like dating as an extremely lonely person." This is exactly the situation that a recruiter should be preventing. That person shouldn't have made it through door. Your process was broken.. Unqualified people applying for jobs is not unique to the tech industry.
- flukus 9y agoThe interview was immediately after the technical test, it's either that or you have to schedule people to come in again, which wastes the time of the good candidates.