News for hackers. Stuff that matters.
Re:Finding awesome developers in programming interviews by prodigal_erik on Tuesday September 14, 2010 @03:45PM (#1692001)
A colleague once had a candidate who dutifully listed PostScript on his résumé because he had been using a "print to file" feature.
Re:Finding awesome developers in programming interviews by gaius on Tuesday September 14, 2010 @04:12PM (#1692094)
I've seen telnet listed as a skill too.
Re:Finding awesome developers in programming interviews by dkarl on Tuesday September 14, 2010 @09:25PM (#1692966)
People list all the programs they've used. Microsoft Word, Microsoft Powerpoint, Firefox, Internet Explorer, [no, not a web programmer] Windows, Linux, Mac OSX, emacs, Visual Studio, gcc, g++, ssh, Putty, xterm, armed robbery, and emacs. (Typical start to an interview: "You listed emacs twice." "Really? Oops, sorry." "That's... not the reply I was fishing for, but 'oops' is acceptable.")

Frankly, I don't blame them. I looked through a stack of a dozen resumes on my boss's desk and noticed that every single resume listed Scrum. Somebody in HR is screening out candidates that don't list Scrum on their resume. I pointed it out to my boss and he just laughed and said he didn't think he could do anything about it. (I didn't look for other patterns, but I bet it's just as bad with particular software technologies.)

So listing every single piece of software you've ever noticed installed on your computer is a good policy unless you're personally handing your resume to the hiring manager. It makes a bad impression on technical folks, but that's better than getting your resume round-filed before anybody technical sees it.

(Note to self: next time job hunting, prepare different HR-friendly and techie-friendly versions of each resume.)

Re:Finding awesome developers in programming interviews by gaius on Wednesday September 15, 2010 @05:09AM (#1693725)
There must be some jub hunters advice book where they tell people to do this, or maybe schools careers advisers do.

We had a case where we had a stream of candidates giving the same - and wrong - answers to various questions, all had come via the same recruiter, who was debriefing them after and coaching the next one.