No idea if it was a typo for C# or the recruiter thought, we have C and C++, why not add C+ in there to increase our hits.
I found it amusing, but didn't start an argument..
No idea if it was a typo for C# or the recruiter thought, we have C and C++, why not add C+ in there to increase our hits.
I found it amusing, but didn't start an argument..
They also asked me about if I had experience with the EMACS editor, but spelled out the letter E-M-A-C-S. Why that was an important skill I have no idea. Especially since this was for a contact that several companies were competing for and I was hired by the winning company to work on it. No special knowledge of EMACS was required. Any text editor would work.
For instance, when I'm hiring a vSphere admin, and I ask my recruiters to put anybody that wasn't immediately familiar with RVTools (among other things) at the bottom of the resume pile. It's a dead simple and ubiquitous utility for vSphere admins, and is a pretty good shortcut for eliminating people with too little experience or too hands-off experience from contention. Sure, it might end up accidentally selecting against what would otherwise be good candidates, but in general I've found it helps accelerate forced ranking of candidates.
That's probably a bit more directly applicable to the role than your Emacs question, but they might be trying to feel out what 'kind' of a developer you could be. Those that favor Emacs, Vim etc tend to be rather different than those that use Visual Studio, etc.
There's tons of ways to assess this -- interest in upcoming technologies, familiarity with linux/unix history, awareness of other tools, regardless of whether they use them, etc
To me this seems like the OPPOSITE of trivia/whiteboard interviewing. The goal is to probe someone, not mark them down for every random thing they don't know about. Software absolutely seems like one such field where it's both easy and important to find people whose enthusiasm goes home with them.
It's really popular in the startup world to care deeply about enthusiasm about the subject at home, but a lot of these litmus tests won't consistently hit that.
Even though you may generally get better programmers on average through these types of screens and companies are free to hire as they please when it comes to this, it seems rather unfair to a good programmer who simply likes to do other things in their spare time. Requiring programmers that live and breathe CS makes it feel much more exploitative.
I like to use vim whenever possible, but my job requires Visual Studio for many day to day tasks and would not hire someone unfamiliar with Visual Studio.